IMPLEMENTAUDIT
On this page
  1. Continuity
  2. Preload priority
  3. Decision records
  4. Optional sidecar context
  5. Intra-run vs inter-run continuity
  6. Continuity writeback options
  7. Source surfaces
  8. Resume contract
  9. Sidecar priority
  10. What belongs in AGENTS.md
Closure

Continuity and resume

How the run resumes from files without trusting chat memory.

Resume from disk, not from chat memory.

The work record, live repository files, and AGENTS.md are the first continuity surfaces.
For phased work, the run folder carries the cursor and phase evidence.
Sidecars can add terrain or custody context, but they must not outrank the files the run actually edits and audits.

Continuity

Resume from the bound work record and live repo files, not chat memory.
For phased work, STATE.md and PROTOCOL.md inside the run folder carry the run cursor and rules.

Preload priority

On resume:

  1. Read live files and applicable AGENTS.md first.
  2. Then read the run folder.
  3. Then read notes.
  4. Then read optional Graphify terrain.
  5. Then read optional ActiveGraph checkpoint or mirror context.

If these disagree, the run must record the conflict instead of silently choosing the convenient source.

PriorityContinuity sourceBoundary
1Live repo files and applicable AGENTS.mdAuthoritative. Never overridden by memory, sidecars, or prior run notes.
2Run-root applied context: applied-context.md, applied-memories.md, STATE.md, and active phase filesPrior state for this task; must be checked against live files.
3Optional personal or project notesHuman-curated guidance; used only when available and authorized.
4Graphify terrainQualified first-contact orientation only after scope-local catalogue/fingerprint validation, or the legacy commit-SHA check. Dogfood-only, structural llm: false, not proof; absence is not a failure.
5ActiveGraph checkpoint or mirrorAuthorized fork/diff checkpoint assistance or an optional non-authoritative event mirror. The run root remains authoritative; absence is not a failure.

Decision records

AGENTS_UPDATE_DECISION records whether durable repo instructions changed.
CONTINUITY_DECISION records whether continuity material should be persisted, skipped, or handed off.
Both are audit decisions, not decorative notes.

Optional sidecar context

Optional sourceUseBoundary
Graphify terrain--graph-scope selects the smallest scope covering the named paths; revalidate the child before parent broadening or relation fallback.Canonical scan root, Graphify-manifest and graph-source population, content/config hashes, graph-bound scope contract, and graph digest must match; unsupported nested config, any stale-sidecar, or an absent relation routes to live files. Legacy built_at_commit still compares with git rev-parse HEAD.
ActiveGraph checkpoint or mirrorUse authorized fork/diff or optionally mirror already-recorded run-root events.Not lifecycle authority, correctness proof, or authorization to mutate.
Optional tooling pageSetup, conventions, and historical-backfill labels.Read the boundary before relying on sidecars.

Intra-run vs inter-run continuity

Intra-run continuity resumes the current run cursor and active phase from the run root.
Inter-run continuity carries durable lessons through AGENTS.md or another authorized record; an ActiveGraph mirror remains secondary.

Continuity writeback options

Per-phase writeback is explicit.
CONTINUITY_DECISION records one of five bounded options:

  • No writeback.
  • Repo-local AGENTS.md rule.
  • Run-local applied context.
  • Optional personal/project note.
  • Optional ActiveGraph mirror event, after separate authorization.

IMPLEMENTAUDIT_CONTINUITY_SAVED appears only after a real writeback and must name the writeback boundary.

Source surfaces

AGENTS.md, skills/implementaudit/templates/sidecars.md, and skills/implementaudit/references/lean-operating-discipline.md.

Resume contract

On resume, reread STATE.md, the active phase spec, and planning evidence from disk.
Validate the run root and phase spec before continuing.
Do not restart from phase one unless the owner asks.

After IMPLEMENTAUDIT_PAUSE, offer the interruption menu: Resume, Revise spec, Skip phase, or Stop.
Continue from the disk-backed paused step without re-printing phase start unless a new phase actually begins.

Sidecar priority

Optional sidecars can support maintainers, but live files, AGENTS.md, Smoke A/B evidence, and final audit remain higher-priority proof surfaces.
For the broader optional-tooling contract, see Optional tooling.

What belongs in AGENTS.md

AGENTS.md is for durable repo-local operating rules and anti-repeat lessons.
It is not for raw terminal output, transient run state, unresolved brainstorm notes, or evidence that belongs in a run folder.

Put in AGENTS.mdKeep in the run folder
A repeated failure mode that future agents must avoid.The one-time command output that proved the failure.
A stable authorization, package, generated-file, or release boundary.Phase-local notes, temporary blockers, and smoke logs.
A concise rule with scope and rationale.Raw screenshots, local paths, or chat-only context.