IMPLEMENTAUDIT
On this page
  1. The 20-second version
  2. First command
  3. What gets written
  4. Loop map
  5. Terms without the insider tax
Overview

Plain English

Start here if the product vocabulary is new. This page explains the first run in ordinary terms first, with IMPLEMENTAUDIT terms kept beside the plain meaning.

The 20-second version

You give a repo requestUse Claude Code or Codex in the repository you want changed.
It creates or binds the work recordPhased or larger runs use a run folder (run root) such as .IMPLEMENTAUDIT/runs/<task-slug>-<id>/.
It writes state and checklistsSTATE.md, a roadmap, phase checklists, decisions, and evidence live on disk.
It checks before and after editsBefore/after checks (Smoke A/B) make the result comparable instead of conversational.
It stops on failed evidenceStop-the-line failure handling (Andon) records the cause, countermeasure, rerun, escalation, or handoff.
It closes only after auditAUDIT_COMPLETE must precede IMPLEMENTAUDIT_RUN_COMPLETE.

First command

No special audit file is required for a first try. Paste one concrete repo request into Claude Code or Codex:

Concrete taskstart
/implementaudit add tests for the login timeout bug

If you already have findings, point at them directly:

Findings fileaudit
/implementaudit close the findings in AUDIT.md

What gets written

Run folderFor phased or larger work, .IMPLEMENTAUDIT/runs/<task-slug>-<id>/ keeps state outside chat.
State fileSTATE.md records status, phase, decisions, and failure rows.
Phase checklistPhase checklist (phase spec) defines bounded work before mutation.
EvidenceBefore/after checks, failure log, and final audit ledger show what happened.

Loop map

Read these as different kinds of control, not five pipeline steps.

  • The planner frames the work.
  • Run-state control keeps the work record, run folder when present, and phase cursor coherent.
  • Phase execution loops through bounded work.
  • Failure handling can interrupt any layer.
  • Final audit repeats until closure or handoff is honest.
planner loopL1 - Plan the workframes the request, writes the roadmap, and critiques before dispatchphase checklists (phase specs)
run-state controlL2 - Track the runowns the work record, run folder when present, state cursor, and continuity across the jobSTATE.md
execution loopL3 - Change safelyruns each execute / verify / update cycle against the real repobefore/after checks (Smoke A/B)
interrupt loopL4 - Stop on failurecan interrupt any layer to classify, probe, fix, rerun, escalate, or hand offfailure log (Andon log)
closure loopL5 - Verify closureloops after phases until final checkable evidence proves completion or handofffinal fix-and-verify loop (audit-fix)

Terms without the insider tax

GembaReal filesLook at the repository, generated source, and current state before deciding what is true.proof starts in the actual workspace
AndonStop-the-line failure handlingWhen evidence fails, pause to classify the gap, record the cause, choose a countermeasure, rerun, escalate, or hand off honestly.no failed check gets waved through
Smoke A/BBefore/after checksRun a focused check before changing things and a comparable check after, so the result is measured against a real baseline.same slice, clearer evidence
run rootRun folderThe on-disk work record for larger or phased work, usually under .IMPLEMENTAUDIT/runs/<task-slug>-<id>/.state survives outside chat
owner/sourceWhere the change belongsPatch the file or contract that actually owns the behavior, not the nearest symptom or generated copy.source first, generated output later
DMAIC/DMADVRepair/new-build routingExisting behavior is improved through a repair route; new or replacement work gets a design-and-verify route.brownfield and greenfield stay distinct
trust-priorAccepted earlier evidenceEvidence from an earlier verified step can be reused only with the boundary named, not treated as fresh proof.reuse is explicit
audit-fixFinal fix-and-verify loopFinal audit gaps loop back into narrow fixes and reruns until closure is proven or the handoff says what remains.closure stays checkable
referenceTerminologyOpen the term map when a phrase needs its owning reference instead of the short plain-English version.the deeper vocabulary map