zara-coding: reject contradictory dirty/path evidence #448

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-dirty-path-coherence into main
Owner

Advances #1 by making repository verification fail closed on internally contradictory observed state.

RAGE transaction

  • RED-first 96738f2: require both evidence construction and the verify bridge to reject dirty=false with changed paths and dirty=true with no changed paths; tampered evidence must be rejected before SWI-Prolog is invoked.
  • implementation b752282 + 663aec5: enforce the invariant at canonical evidence construction and re-check it at the trust boundary before serializing repository evidence to Prolog-RLM.

This prevents a hand-constructed/tampered evidence mapping from satisfying one repository assertion while contradicting another. No new authority, collector, shell, or execution path is introduced.

Exact-head CI must pass compatibility, full generated registry/plugin Nix checks, and package builds before merge.

Advances #1 by making repository verification fail closed on internally contradictory observed state. ## RAGE transaction - RED-first `96738f2`: require both evidence construction and the verify bridge to reject `dirty=false` with changed paths and `dirty=true` with no changed paths; tampered evidence must be rejected before SWI-Prolog is invoked. - implementation `b752282` + `663aec5`: enforce the invariant at canonical evidence construction and re-check it at the trust boundary before serializing repository evidence to Prolog-RLM. This prevents a hand-constructed/tampered evidence mapping from satisfying one repository assertion while contradicting another. No new authority, collector, shell, or execution path is introduced. Exact-head CI must pass compatibility, full generated registry/plugin Nix checks, and package builds before merge.
Some checks failed
CI / test (pull_request) Failing after 16s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/1-zara-coding-dirty-path-coherence:rage/1-zara-coding-dirty-path-coherence
git switch rage/1-zara-coding-dirty-path-coherence

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/1-zara-coding-dirty-path-coherence
git switch rage/1-zara-coding-dirty-path-coherence
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-dirty-path-coherence
git switch rage/1-zara-coding-dirty-path-coherence
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-dirty-path-coherence
git switch main
git merge --squash rage/1-zara-coding-dirty-path-coherence
git switch main
git merge --ff-only rage/1-zara-coding-dirty-path-coherence
git switch main
git merge rage/1-zara-coding-dirty-path-coherence
git push origin main
Sign in to join this conversation.
No description provided.