Alliance Ops

SRP Request

Submit Loss

Review Policy

SRP requests require a killmail link or pasted killmail text, ship/purpose context, FC or doctrine note when applicable, and human approval before payout.

Default stateSubmittedReview ownerSRP Reviewer / AdminAutomationNonePayoutHuman-approved only

eligibleFleet Doctrine Loss

Killmail / fleet or doctrine name / FC/objective note

eligibleTackle / EWAR Loss

Killmail / fleet role note / FC or scout context

conditionalLogistics / Support Loss

Killmail / fleet/support role / FC or logistics anchor note

conditionalCapital / Structure Timer Loss

Killmail / operation ping or timer reference / leadership/FC approval

Readiness Boundary

Manual IntakeLive

Loss requests can be submitted without private EVE data.

Admin ReviewProtected

Queue review and decision notes stay behind admin access.

Reserve PlannerAdmin-only

Reserve exports use aggregate guidance and exclude raw queue details.

Future Proof5 scopes

Private SRP proof context waits for feature-specific EVE consent.

Public SRP readiness exposes public route counts, protected route counts, workflow-stage counts, consent-preview links, and safety booleans only; it does not expose pilot names, killmail URLs, raw SRP queue notes, wallet balances, contract data, EVE tokens, provider secrets, private EVE data, or payout actions.

Open SRP Readiness JSON Preview Future SRP Consent