◆ OPERATOR CONTROL ROOM

Fixture contract preview — not a live reducer console. Parameter names mirror the audited server reducer signatures; submitting here is intentionally disabled until a live operator flow is row-backed.

0x84f1a92c77...a803f9dd JUDGE OPERATOR mortal-context CONNECTED
SELECTED HEAT HT-04412 · RUNNING
◆ REDUCER ACTIONS
create_heatCONTRACT PREVIEW
Source: server/src/lib.rs create_heat(task_id: u64, ruleset_version); deadline_at is reducer-owned fixed clock state from start_heat. UI preview only; reducer acceptance is proven by SpacetimeDB rows or explicit errors.
task_id · u64 · required
ruleset_version · string · required
PARAMETER PREVIEW
{
  "task_id": "0",
  "ruleset_version": "[required string]"
}
◆ CURRENT HEAT
HeatHT-04412
StateRUNNING
Deadline15:02:00 UTC
Attempt Aatt-04412-A · 0x84f1...b1d4 · RUNNING
Attempt Batt-04412-B · 0x77b0...faa8 · SUBMITTED
◆ DEMO READINESSOPERATORS
Public URLhttps://mortal-context.pages.dev
Local previewhttp://127.0.0.1:5173
Maincloud modulemortal-context
Copy/paste commands:
pnpm smoke:judge
pnpm holdout:rehearse
Route checklist
https://mortal-context.pages.dev/operator Operator readiness and reducer contract visibility
https://mortal-context.pages.dev/system Runtime proof, smoke checks, and module evidence
https://mortal-context.pages.dev/watch Watch route probe and stream marker posture
https://mortal-context.pages.dev/replay Receipt archive and replay path check
https://mortal-context.pages.dev/watch/demo Fixture stream lane probe
https://mortal-context.pages.dev/watch/HT-04412 Representative live heat deep link
◆ REDUCER LOGLATEST ROWS
join_heat ACCEPTED → att-04412-B fixture transcript from reducer contract preview 14:31:40 UTC
submit_move ACCEPTED → move-006 fixture transcript from reducer contract preview 14:58:12 UTC
submit_result_evidence REJECTED lint summary not parseable fixture rejection; live reducer would return an error string 14:58:21 UTC
settle_heat REJECTED attempt A still running fixture rejection; illegal transition stays disabled 14:59:02 UTC
◆ SAFETY

The UI never computes score, winner, leaderboard, or receipt. There are no direct table-edit controls. Settlement only calls settle_heat; the result appears after the row updates.