Audience
For agents and operators
This page is for the person or agent running IMPLEMENTAUDIT inside an actual repo.
Operator contract
- Pick the invocation shape honestly.
- Bind or synthesize the work record before mutation.
- Inspect real files.
- Write run artifacts.
- Run before/after checks (Smoke A/B).
- Close only through final audit or handoff.
Invocation shapes
| Shape | Plain meaning | Mutation condition |
|---|---|---|
| Direct governance | The user supplied a concrete audit, handoff, checklist, review, task, or bounded plan. | Bind the work record first, then mutate under it. |
| Embedded governance | An outer goal/task already owns the work. | Do not emit a nested goal; govern the active object in place. |
| Goal synthesis | The input is too incomplete to execute safely. | Write a bounded plan and handoff before execution. |
| Governed casual-build intake | The user gives natural-language repo-build intent. | Synthesize a bounded audit object before any mutation. |
Operator checklist
- Record owner/source before editing.
- Use before/after checks instead of trusting the final sentence.
- Classify failure before retrying.
- Escalate only with new evidence.
- Keep commit, push, tag, release, publication, provenance, and sidecar setup behind separate gates.
Source surfaces
Canonical behavior lives in skills/implementaudit/SKILL.md, skills/implementaudit/templates/PROTOCOL.md, skills/implementaudit/references/planning-depth.md, and skills/implementaudit/references/routing.md.