Every public intake lane has a protected review path.
Alliance Ops
Alliance Ops Reviewer Workflow
Public proof for the reviewer path: the intake lanes are live, protected packets exist, and activation gates keep grants, payouts, Discord changes, provider calls, and private EVE data human-reviewed.
Review packets stay behind admin access and private headers.
Reviewer judgment stays required for access, payout, and service changes.
Provider, role-sync, notification, and payout automation remains off.
protected
Review Packet
Protected lane summaries and checklist coverage for access, recruiting, SRP, fleet, buyback, mining, and support.
protected
Intake Launch
Owner launch gates for public intake, protected packet exports, manual decisions, and rollback points.
protected
Reviewer Smoke
Protected route lockouts, no-provider-mutation checks, and reviewer-path smoke evidence.
protected
Reviewer Rehearsal
Human-review rehearsal coverage before grants, payouts, notifications, or role sync are allowed.
protected
Activation Gate
Owner pilot gate for reviewer access, service switches, and no-secret activation evidence.
No-Secret Reviewer Rule
Public Alliance Ops readiness exposes aggregate lane counts, public route counts, submission route counts, protected review route counts, workflow-stage counts, checklist counts, private-data exclusion counts, manual-decision counts, disabled-automation counts, and route labels only; it does not expose raw queue rows, request bodies, applicant or pilot names, contact details, reviewer notes, proof URLs, wallet reads, contract reads, payout actions, role-sync payloads, notification sends, provider secrets, EVE tokens, private EVE data, or separate-project account details.