harness-update

Agent governance updates require a scoped harness update proposal that captures rationale and evidence before patching AGENTS.md, docs, or run templates. Proposals must undergo stakeholder review and approval before modifying shared artifacts.

Propose changes to AGENTS.md or agent specs after completing a non-trivial workflow run to separate product implementation from durable harness evolution. This ensures lessons learned are reviewed before promoting into shared governance practices.

Run templates cannot be modified directly during Codex or Claude workflows. A controlled patch workflow requires generating an evidence-backed proposal and securing reviewer approval before applying any changes to shared templates.

Capturing lessons learned involves generating a scoped harness update proposal that documents the rationale, evidence, and required patches from the run. Stakeholders then review this proposal before applying changes to skills or agent specs.

The harness update process applies to both Codex and Claude workflows, governing changes to AGENTS.md, docs, skills, agent specs, and run templates. It enforces evidence review and reviewer approval across both platforms.

Reviewer approval before patching shared documentation prevents uncontrolled modifications to governance artifacts like AGENTS.md and run templates. The controlled patch workflow ensures all changes are evidence-backed and stakeholder-validated.