Checking the hosted three-runtime mesh…
THE LATE THIRDS // THE LEGACY
Three-Runtime Shadow Mesh
Market producer, Ops producer, and Legacy intake now live as separate hosted machines. Market and Ops may sign and push downstream. Legacy may verify, receipt, diff, and freeze—but it cannot call either source or write back.
V0.7ARMED— CONTROLS
Separate key, runtime, origin, and stateless process.
Stage-only board context; saved boards remain outside.
No producer hostname, credential, pull method, or callback is stored here.
Paste the session code into the separate Market host and push once.
OBSERVE → SIGN → PUSHBoth independent signed receipts must arrive before the 80-control gate can run.
VERIFY → RECEIPT → DIFF → FREEZEPaste the same code into the separate Ops host and push once.
STAGE-ONLY → SIGN → PUSHHOSTED MESH SESSION
Arm the three-machine proof.
Starting creates a short-lived account fence and two source-specific signing grants.
CONTROL LEDGER
—64 inherited laws · 16 hosted mesh laws pending
No authority assumedv0.7 must inherit all 64 controls and add 16 proofs of physical runtime separation, signed delivery, replay safety, and zero return paths.
ARMED