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 fresh judgment, 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](../plan/SKILL.md) 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](../implement/SKILL.md) 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 final judgment. Reuse valid exact-input receipts; rerun affected checks after changes. Reserve capacity for integration, review and repair. Keep the final subject unchanged while it is being judged. 5. Obtain [Validate](../validate/SKILL.md) from one fresh author-distinct context in the author's model family unless the caller selects required additional legs. There is no fixed ten-m...