Implement

Implement

Implement the accepted outcome. Repair ordinary known defects directly. Use the existing intent; no Plan, Recall or Learn worksheet is owed for a clear edit. Implement owns source changes and factual checks; the runtime derives identity and receipts.

Rules that decide the result

• Fix the cause, not the oracle. Never loosen an assertion, tolerance, golden, fixture or suppression, or substitute a mock or placeholder, to turn a check green. A check that fails against accepted behavior points at a product defect; changing what the check accepts is an acceptance change and needs caller authority.
• Find live consumers before editing. Search the callers, readers, scripts, docs and tests of every edited function, type, path, format or message. For each one, state whether the change affects it and which check covers it. When retiring or renaming, consumers include installations, lookups and old-name invocations; preserve historical provenance.
• Name discriminating checks. A behavioral change preserves RED for the expected missing behavior: name the check that fails before the edit and passes after, plus the check for each affected consumer.
• Report only what ran. Give exact commands and results. List every check you did not or could not run as not run. Never call unrun work verified, fixed or green.

For authorized service operations, load only the relevant procedure from operations methods (reliability, delivery, incident recovery, resilience, toil); ordinary edits owe no operations phase.

Workflow

1. Read intent, acceptance, scope and repository boundaries before the first write; reuse loaded contracts. RPI boundaries apply when that workflow is explicitly selected. Caller-selected episode tracking follows the session association reference; keep unknowns explicit and invent no parentage or second tracker.
2. Carry the accepted behavior examples forward unchanged. Use repository domain names in symbols and tests; check observable outcomes through the relevant interface. Run the smallest applicable check before and after editing. Pure refactors, relocations or docs may have an honest green baseline. Prefer existing tests or small discriminating probes.
3. Make the smallest in-scope change. When repairing discovery or checks, preserve the consumer's existing input selection; fixing an error path does not authorize a wider scan. Use a negative control when exclusion matters. Check a representative change against existing constraints before bulk propagation, and the authored source set before broad regeneration. Repair known failures directly and verify the exact result with a check; a repair does not start another review. A disproved assumption may change the approach within scope; use Plan only for consequential uncertainty.
4. Read the repository's actual check recipe, including instrumentation and environment, rather than reconstructing it from memory. Run targeted tests and lint/static checks before broad integration, and required full checks at integration. Reuse exact-input receipts only while source, tool and relevant environment match. Neither bypass required hooks nor replay a check just to rename its receipt. A required CI job's known failure is actionable before the run ends: repair it within scope, keep the failed subject's evidence and rerun affected checks. Pending jobs do not imply success.
5. Refactor while acceptance remains green. Inspect changed tests, fixtures, goldens, tolerances, suppressions and specification text against original intent before handoff.
6. Have the runtime derive actual changed paths and content identity. A delegated increment awaiting integration returns an exact commit or runtime-derived content digests, author context ID and check facts in the existing handoff. The integrating caller derives subject-manifest.v1 (AgentOps schema schemas/subject-manifest.v1.schema.json) over the complete final subject before judgment; an independently judged increment needs its own manifest. Do not generate both merely because work was delegated.
7. At that boundary, when the repository records AgentOps evidence bindings and changed paths affect bound acceptance evidence, run ao provenance evidence-orphans --root <repo-root> with one --changed <path> per derived path, retain its actual output and refresh affected bindings after repairs. Without ao, list the orphan scan under not run. Never invent or suppress the orphan list.
8. Return the handoff below, then stop.