RACECONTROL · CONTROL PLANE · TIER-1

Deployment dashboard

Read-only view over per-venue Server + Bono-edge state. Mutation is forbidden here per tier-boundary rule (vii) in replit.md.

NEW · provision & subscriptionProvision an installerMint an installer and read the subscription panel for Racing Point eSports — no need to walk the tenant page.
Provision →

Launch critical path · B1..B9

Tenant heartbeats (1)

Heartbeats are stubbed in the Replit sandbox (LAN-isolated). On Bono deploy they wire to /internal/health over WireGuard (COORD-MEMO-1 Axis 8).

Captain owes (B1..B5)

  • B1CD-20 OTP-bridge sync-ratify✅ RATIFIED 2026-05-24 (was: CRITICAL)
  • B2Session bundle 5-item disposition✅ RATIFIED 2026-05-27
  • B3CD-22 Bono recon path pick✅ DONE 2026-05-24
  • B4V1-F / V1-H existence confirmation✅ CLOSED-AS-N/A 2026-05-28
  • B5Phase J CD-17 / CD-18 / CD-19 / CD-21 status confirmation✅ RATIFIED 2026-05-24
  • B6Provision `comms-link` CI secrets + flip required status check⏳ pending Captain physical action (Task #920, 2026-05-29)
  • B7Ratify Task #921 doctrine-name gate draft + James installs in `racingpoint/comms-link/`⏳ pending Captain ratify + Server-side install (Task #922, 2026-05-29)

Operators owe (B6..B9)

    Latest Captain ratify trail

    CAPTAIN-RATIFY-2026-05-28.md
    # CAPTAIN-RATIFY-2026-05-28 — Ratify-all-pending pass
    
    **Date:** 2026-05-28 (Replit sandbox; +1 day vs IST) · **Authority:** Captain (this session)
    **Source packet:** `coordinator/CAPTAIN-RATIFY-ALL-PENDING-2026-05-28.md`
    **Recorded by:** Replit (sandbox) per Captain instruction "RATIFY rp-v2-apps/coordinator/CAPTAIN-RATIFY-ALL-PENDING-2026-05-28.md" with sub-decision policy "RATIFY everything that has a clean default; DEFER the four items needing sub-decisions."
    **Routing:** Server-side maintainer (legacy git identity `james-racingpoint`) appends each §S-N candidate below to `racingpoint/comms-link/V2-MASTER-STATE.md`. Replit cannot push there.
    
    ---
    
    ## Dispositions
    
    ### A. B3 — Bono SSH paste
    **Status:** UNCHANGED (already RATIFIED 2026-05-24 as Option 2; physical paste pending Captain action). No new ratify in this pass.
    
    ### B. B4 — V1-F / V1-H existence confirmation
    **Disposition:** ⏸ **DEFERRED — needs Captain ground-truth.** Carried forward as the sole remaining `CAPTAIN-OWES.md` open ratify item.
    
    ### C. AUTH-MEMO-1 rule #5 — Binary + license signing custody
    
    | Class | Disposition | §S-N candidate |
    |---|---|---|
    | C.1 `security` | ✅ **RATIFIED** single-custody (clean default per packet §3). | §S-410 candidate |
    | C.2 `critical-security` | ⏸ **DEFERRED** — Captain must name the two-of-two deputy before key generation. | — |
    | C.3 `feature` | ✅ **RATIFIED** single-custody. | §S-411 candidate |
    | C.4 `schema` | ⏸ **DEFERRED** — Captain must name the two-of-two deputy before key generation. | — |
    | C.5 `license` | ✅ **RATIFIED** custody, with binding invariant: **license signing key MUST NEVER co-reside with any binary signing key host** (per `PHASE-L-PRODUCTIZATION-CLOSURE-2026-05-21.md` §3 + Item D.5 below). | §S-412 candidate |
    
    **Post-ratify gate:** the three ratified classes can proceed to key generation per `BINARY-SIGNING-CEREMONY-CHECKLIST.md`. The two deferred classes block their respective release paths until deputies are named.
    
    ### D. Phase L productization closure — 9-clause multi-anchor