The consistency ingest takes the dirty mark from the issued request alone: validateConsistency (internal/core/intent/consistency.go) reads the dirty and dirty_path lines of the request and never recomputes them, though it re-reads the tree for the receipt check anyway. A request hand-edited to dirty: false over an uncommitted corpus therefore ingests rc=0, and the append-only report pins review_of_commit with no dirty mark while its findings quote text that commit does not hold.

The consistency ingest takes the dirty mark from the issued request alone: validateConsistency (internal/core/intent/consistency.go) reads the dirty and dirty_path lines of the request and never recomputes them, though it re-reads the tree for the receipt check anyway. A request hand-edited to dirty: false over an uncommitted corpus therefore ingests rc=0, and the append-only report pins review_of_commit with no dirty mark while its findings quote text that commit does not hold.

Grounds

• pursued: a forged dirty: false request over an uncommitted corpus ingests to a report carrying dirty: true and the uncommitted path (TestConsistencyIngestRecomputesTheDirtyMark, and a CLI probe on a scratch copy); a report left unmarked, or naming a path other than the edited one, would show it wrong