Activation Control
Activation Owner Decision
This public mirror turns the activation-readiness rollup into owner decision branches: keep live switches gated, record the missing owner/provider evidence, or start a controlled activation pilot later. It publishes only aggregate branch, blocker, lane, and proof counts. Live OAuth, provider actions, account saves, database writes, and private EVE data remain gated.
Live switches stay gated until owner and provider proof is recorded.
0 lane(s) are ready for live activation.
6 buildable item(s) can continue while gated.
Owner-review actions stay visible without evidence values.
10 protected evidence field(s) remain missing.
1 branch is blocked by launch evidence.
No proof target starts OAuth, calls providers, mutates data, or exposes private data.
No protected admin routes or private packet bodies are exposed.
Keep live activation switches gated
Recommended while activation lanes have evidence but no live switch is ready.
- Public Route
- /activation-readiness
- Requirements
- 3
Record owner, EVE, and provider evidence
Available next step for clearing owner, EVE, and provider blockers without enabling live actions.
- Public Route
- /owner-handoff
- Requirements
- 4
Start controlled activation pilot
Blocked until owner-pilot evidence, account-save gate proof, and rollback smoke evidence are recorded.
- Public Route
- /eve-sso-acceptance
- Requirements
- 4
EVE SSO Account Gate
Callback, approved scopes, and owner live test must be recorded before public login turns on.
Evidence ready; live activation gated; blockers 3.
Reports Account Saves
Account saves stay staged until production EVE auth owner-test evidence is recorded.
Evidence ready; live activation gated; blockers 1.
Provider Communications
Discord and email actions stay disabled until provider approval and signed smoke evidence are ready.
Evidence ready; live activation gated; blockers 3.
Revenue Growth
Stripe, AdSense, telemetry, and search lanes stay gated until owner/provider evidence is ready.
Evidence ready; live activation gated; blockers 1.
Ops Monitoring And Recovery
Protected monitoring is covered; recovery drill evidence remains the launch review item.
Evidence ready; live activation gated; blockers 1.
Alliance Ops Intake
Protected intake and reviewer surfaces are ready for owner review before broader activation.
Evidence ready; live activation gated; blockers 0.
Private Corp Command
Private corp dashboards stay gated until EVE SSO, role policy, token health, and audit logging pass.
Evidence ready; live activation gated; blockers 4.
Activation owner decision page
Shows public-safe activation decision branches and launch-switch counts.
- Route
- /activation-owner-decision
Activation owner decision JSON
Returns no-store branch, blocker, proof-target, and safety counts only.
- Route
- /api/activation/owner-decision-readiness
Activation readiness
Keeps seven activation lanes visible with aggregate evidence and blocker counts.
- Route
- /activation-readiness
Activation readiness JSON
Machine-readable feed returns public-safe activation rollup counts.
- Route
- /api/activation/readiness
Next Actions
Shows blocked, staged, buildable, and critical external action counts.
- Route
- /next-actions
Owner Handoff
Keeps owner-review lanes visible without evidence values.
- Route
- /owner-handoff
EVE SSO acceptance
Shows owner-pilot acceptance state without starting OAuth.
- Route
- /eve-sso-acceptance
Launch Evidence Reviewer
Mirrors launch evidence coverage without protected packet bodies.
- Route
- /launch-evidence-reviewer
Health JSON
Lets production smoke prove the activation decision mirror stays safe.
- Route
- /api/health
Public Boundary
Public Activation owner-decision readiness exposes decision branch labels, recommended branch state, activation lane counts, blocked action counts, owner evidence gate counts, EVE owner-pilot labels, provider gate labels, proof target outcomes, public route labels, and no-side-effect booleans only. It does not expose owner evidence values, protected review packets, protected route bodies, provider credentials, EVE tokens, private EVE data, account data, private logs, provider cookies, or separate-project account details, and it does not start OAuth, call EVE or CCP, trigger providers, write database rows, save accounts, or mutate data.