rpi

RPI

Run one experiment from the caller's existing intent source through three responsibilities and stop:

anti-ceremony guard -> Plan -> Implement -> fresh Validate -> report

On CONTINUE, the core path remains Plan -> Implement -> fresh Validate -> report. RPI invokes the guard exactly once before Plan. It 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 reference behavior makes the dispatch and stop semantics executable without Git, ao, or a tracker.

Admission and phase lock

RPI activates for any request shaped as plan-execute-verify work — orchestration, worker delegation, "execute this plan", or an explicit Plan -> Implement -> Validate ask — whenever the goal includes changing the subject. The caller does not have to name RPI. Research-, audit-, and review-only delegation is not RPI admission: it produces evidence for a caller, has no implementation candidate, and never earns a verdict.

Once the caller has accepted a plan — including a duel or design synthesis — Plan is closed for that intent. Every subsequent lane must return implementation evidence: diffs, commits, test results, or factual receipts. Dispatching another planning, audit, or review lane over the same intent requires new explicit caller authorization; a review comment is never that authorization by itself.

Contract

1. Invoke anti-ceremony's artifact-free quick guard once with the caller outcome, proposed process work, remaining proof, and stop condition. On STOP, dispatch no core phase, report NOT_PLANNED with the guard's one-sentence reason, and stop. On CONTINUE, proceed without adding an artifact, retry, repair, delivery, tracker, or Git action.
2. 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. Preserve a durable caller-owned source by reference and digest; only when no durable source exists does the runtime snapshot the exact resolved source bytes under their digest before dispatching Implement or a fresh Validate context. If usable intent cannot be established, report NOT_PLANNED and stop.
3. 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.
4. 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.
5. Return the fresh validation result and a short report. Persist and link verdict.v2 only when the caller requests machine-readable evidence or a declared downstream consumer requires it. Stop regardless of PASS, FAIL, or NOT_PROVEN.