Rpi

RPI

Own the authorized outcome through finish. Use the native coding agent and shell. BD or the caller's tracker owns work and handoffs; Git owns content and delivery. AgentOps supplies a small charter and one fresh judgment where a mistake is costly, not a scheduler.

Operating charter

1. Use the existing accepted outcome, scope and real bounds. A clear change needs no Plan, Recall or Learn worksheet. Resolve uncertainty only when it could change the implementation or acceptance decision.
2. Take the smallest acceptance-advancing action. Plan shapes missing intent or revises a disproved approach. Once an implementer can act and a validator can judge, implement; do not keep improving the plan. Approach revisions preserve acceptance and authorized scope. Acceptance changes need caller authority.
3. Implement and repair ordinary known defects directly. A known test failure needs a fix and a discriminating check, not another planning phase, council or helper.
4. Use focused checks during edits and complete required integration checks before finishing. Reuse valid exact-input receipts; rerun affected checks after changes. Reserve capacity for integration and repair. Keep a subject unchanged while it is being judged.
5. Spend validation where a mistake is costly. For an ordinary change the checks and CI are the gate: finish. Obtain Validate from one fresh author-distinct context only when the caller asks, when a mistake cannot be cheaply undone after it lands (a published release or instructions users will follow, a security boundary, destroying data or tracker state, deleting a check that protects the product), or when no deterministic check covers the changed behavior. Use the author's model family unless the caller selects additional legs; explicitly required reviewers remain required.
6. One round. Give the validator the accepted criteria, the exact subject and one question written before it starts, never the author's confidence or desired verdict; it does not re-run the checks. Repair what fails the accepted behavior or would mislead a user, break install or the CLI, or remove protection for the product; treat the rest as optional notes. Confirm each repair with a check and finish. A repair does not start another review, and NOT_PROVEN is reported with its gaps, not chased. Keep review cost a fraction of the cost of the work; when it approaches that cost, stop and report what is unchecked.
7. Stop at completed acceptance, cancellation, refusal, a spent real bound or an unresolved causal stall after the help below. Adjacent improvements are not permission to expand the goal. Report them briefly only when useful; do not turn them into another work batch.

Delegation and handoffs

When delegation is authorized and useful, select the runtime's task-only dispatch option for independent work; a short prompt in a full-history fork still carries the full history. Supply accepted intent and scope, the exact subject, relevant evidence, remaining bounds, the result's consumer and check ownership. Resume an author for direct repair when useful. Observe actual dispatch settings: prompt wording proves neither isolation nor smaller inherited context. At completion, verify the expected subject and required results; a quiet or partial status is not success.

Return concise findings, check facts and evidence references in the existing handoff, and disclose missing or truncated evidence. Identify the combined subject at the integration or judgment boundary; unjudged worker increments supply content identity and check facts, not duplicate evidence bundles.