rpi

# RPI Run one experiment from the caller's existing intent source through three responsibilities and stop: ```text Plan -> Implement -> fresh Validate -> report ``` RPI preserves the original intent and dispatches each core phase at most once. It does not own retries, budgets, queues, claims, leases, Git, delivery, release, closure, or the caller's next decision. The pure [`scripts/run_once.py`](scripts/run_once.py) reference behavior makes the dispatch and stop semantics executable without Git, `ao`, or a tracker. ## Contract 1. Resolve the existing bead or caller intent. Invoke Plan once only if that source needs shaping; Plan updates the same source or proposes an amendment. It creates no AgentOps packet. The runtime snapshots the exact resolved source bytes under their digest, including when the conversation is the only source, before dispatching Implement or a fresh Validate context. If usable intent cannot be established, report `NOT_PLANNED` and stop. 2. Invoke Implement once with the resolved intent. It performs one bounded experiment; the runtime derives subject identity and check receipts. If no subject is built, report `NOT_BUILT` and stop. 3. Invoke Validate once in a context distinct from the author's context. Pass the intent reference and digest, exact subject manifest, factual receipts, validator identity, and freshness attestation. 4. Return the durable `verdict.v2` reference and a short report. Stop regardless of `PASS`, `F...