Skip to content
⌘K

Claim Audit

A verdict is declared over a range of commits. Claim audit re-checks that range against git after the fact, and records what a person decided about any difference. No model is involved in the comparison.

For a verified spec whose verification/summary.json carries diff.base and diff.head:

  • Claimed: files changed in base..head, the range the verdict was computed over.
  • Observed: files changed in base..tip. tip is the spec’s surviving branch, or the second parent of the merge that brought it in. If neither is found, tip is head (how: head-only) and drift is zero by construction.
  • Drift: added is observed but not claimed. removed is claimed but not observed (reverted or never landed).
  • Invariants: three checks over the spec’s own records: records-parse (frontmatter parses and ## Recorded is last), anchors-resolve (every mm-verify:// anchor resolves to a run file), and no-unreviewed-merge (a merged spec has a verifying entry in its status history).

A spec is clean when both drift lists are empty and no invariant fails; otherwise it is drifted. A merged spec with a head-only tip is shown as unknown rather than clean.

The derivation runs only in the desktop app (the reconcile_candidates and reconcile_spec commands), and only reads git. The board card shows claimed, landed, drift and the invariants, with these actions:

  • Accept: observed becomes the recorded truth. Writes verification/reconcile.json and appends a [decision] line to the spec’s ## Recorded.
  • Send drift back: files an issue in .mm/issues/ listing the drift and any failed invariants, writes reconcile.json, and appends a contradicts decision.

Neither action launches a session or changes git state.

The latest decision only; it is overwritten by the next one.

FieldMeaning
schema_version, at, actorRecord version, time, and who decided
decisionaccepted or sent-back
base, headThe claimed range
tipbranch, sha, and how (branch, merge-parent or head-only)
claimed_count, observed_countFile counts for each side
driftadded and removed file lists
invariantsThe three results with id, label, pass, detail
issueFilename of the issue filed by Send drift back
recheckpending after Send drift back

/mm:drift-audit [spec] reads reconcile.json and summary.json and explains them. It is read-only and never derives or decides. It is not /mm:triage-drift, which triages stale context docs.