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.
What is compared
Section titled “What is compared”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.tipis the spec’s surviving branch, or the second parent of the merge that brought it in. If neither is found,tipishead(how: head-only) and drift is zero by construction. - Drift:
addedis observed but not claimed.removedis claimed but not observed (reverted or never landed). - Invariants: three checks over the spec’s own records:
records-parse(frontmatter parses and## Recordedis last),anchors-resolve(everymm-verify://anchor resolves to a run file), andno-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.
Where it runs
Section titled “Where it runs”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.jsonand 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, writesreconcile.json, and appends acontradictsdecision.
Neither action launches a session or changes git state.
The record: verification/reconcile.json
Section titled “The record: verification/reconcile.json”The latest decision only; it is overwritten by the next one.
| Field | Meaning |
|---|---|
schema_version, at, actor | Record version, time, and who decided |
decision | accepted or sent-back |
base, head | The claimed range |
tip | branch, sha, and how (branch, merge-parent or head-only) |
claimed_count, observed_count | File counts for each side |
drift | added and removed file lists |
invariants | The three results with id, label, pass, detail |
issue | Filename of the issue filed by Send drift back |
recheck | pending after Send drift back |
From the terminal
Section titled “From the terminal”/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.