Genesis Command Center

Runtime deployment proof.

This page reports the active Command Center runtime, the deployment source markers available to the app, and the homepage and Leadership Deck contracts. Browser, proxy, surrogate, and CDN caching are disabled so this surface reports the origin currently serving the request.

Active runtime evidence

Release marker
command-center-live-build-proof-v2
Runtime marker
command-center-runtime-deployment-proof-v3
Attestation contract
command-center-runtime-attestation-v3
Leadership Deck contract
genesis-leadership-deck-brain-grounded-v1
Route
/release-proof
Machine route
/api/release
Active commit
c896e359142361f610164033ece283f247ed37ee
Active short SHA
c896e35
Expected commit
not configured
Branch
main
Deployment
1b501135-8ce3-4ecd-b118-273147e1b571
Deploy source
Railway
Posture
runtime-active-latest-not-asserted
Cache policy
no-store across browser, CDN, surrogate, and proxy layers
Checked at
2026-07-12T02:03:22.563Z
Homepage contract
switchboard-v2

Deployment Lag Runbook

When runtime is behind, classify the failing origin before acting.

Use the dual-origin attestation when /release-proof shows runtime lag or an old contract marker. The exit condition is matching runtime proof, not GitHub merge status.

Receipt required
Step 1

Read active runtime first

Open /api/release and /release-proof and copy Active commit, Deployment, Branch, Posture, and contract markers before making any production claim.

Step 2

Compare both origins

Compare the Railway service origin and best-leadership.org. If Railway is current while the custom domain is stale, treat the problem as edge cache or domain binding lag.

Step 3

Compare against expected commit

Use EXPECTED_COMMAND_CENTER_COMMIT_SHA or the intended merge commit. If the values do not match, production is behind.

Step 4

Escalate deploy lag

Trigger or inspect the Railway deployment path outside the app. GitHub green gates alone are not runtime proof.

Step 5

Recheck protected surfaces

After the active commit matches, verify /admin redirects to Command Center Entry and authenticated /admin/leadership-deck returns a signed Brain grounding receipt.

Step 6

Write the receipt

Record active commit, expected commit, deployment id, origin comparison, observed posture, and operator who verified the runtime.

Runtime verification contract

Admin entry
/admin

Expected: Protected. Anonymous visitors must land on Command Center Entry.

Proof: Email plus four-digit entry code required.

Release proof
/release-proof

Expected: Public proof page for active runtime commit and homepage contract.

Proof: Edge and browser caching are disabled; the page does not assert latest GitHub main unless expected commit is configured and matched.

Machine attestation
/api/release

Expected: JSON contract command-center-runtime-attestation-v3.

Proof: Dual-origin automation compares Railway and the custom domain with a cache-busting request.

Leadership Deck
/admin/leadership-deck

Expected: Protected Brain-connected contract genesis-leadership-deck-brain-grounded-v1.

Proof: Must be verified after login with one signed synthesis and grounding receipt.

Homepage proof

Expected markers
  • Read posture. Choose command side. Route work. Close with proof.
  • Command routing map
  • Signal → Triage → Route → Receipt
  • Open Work Orders
  • CRM & Discovery
  • Content Control
  • Business Workspaces
  • Launch Board
Retired markers
  • Executive operating cockpit
  • Executive Work Orders