Provenance & Context Drift
Every derived document under .codearbiter/ traces its claims to source files in the repo. codeArbiter records this mapping as provenance: which files back a given doc, and the git hash-object hash of each file at the time the doc was authored. When a tracked source changes, the stored hash no longer matches. That mismatch is context drift.
Drift is surfaced once, passively, as a single line at SessionStart. It does not interrupt work. .codearbiter/code-map.md provides a coarse orientation map: it names the main source files and the docs that depend on them. /ca:context-check runs the same detection on demand, as a manual audit.
When a commit lands, the commit-gate auto-heal step checks whether any staged source files have drifted their dependent docs. If they have, it re-baselines the provenance in the same commit or proposes a doc update to accompany the work, so a stale claim gets flagged and corrected before it can be read as current. Auto-heal is commit-gate’s Phase 5.5, per the commit-gate skill; on an ordinary commit with an empty worklist, it costs nothing.
Per-document provenance records live under .codearbiter/.provenance/. /ca:context-check runs the same drift detection as a manual, on-demand audit, and offers three dispositions per stale doc: re-scout it from the current source, re-baseline the stored hash without re-scouting, or defer.
