Day 11: my AI-code trust gate now sees what actually happened — two-phase, signed

Description and use

LOOM implements a two‑phase, signed approval process that closes the gap between approval and execution. The gate now records the actual outcome and rejects replay or forgery attempts.

Problem

A single approval step cannot guarantee that the executed code matches the approved behavior; gaps such as crashes or replay attacks can occur between approval and completion.

Outcome

LOOM’s two‑phase signed approval eliminates the approval‑to‑completion gap, ensuring that the gate records the true execution outcome and rejects replay or forgery attempts. All 388 checks succeeded.

Workflow

• 1. Operator signs a claim_operator_approval to reserve approval before execution.
• 2. The code executes under the gate’s supervision.
• 3. Upon completion or failure, finish_claimed_receipt is called to close the claim with a receipt.
• 4. The gate verifies that the claim was not replayed, duplicated, forged, or double‑finalized.
• 5. The system records the actual outcome, proving what happened.

Evidence

Day 11 makes approval two-phase and signed — 385 → 388 checks, all green

Source

The gate that refuses lies and proves what it allowed now also proves what actually happened

Source