nsaspy/zara-plugins
1
0
Fork 0
Code Issues 10 Pull requests 297 Projects Releases Packages Wiki Activity Actions

zara-coding: reconcile frozen SPECs with repository evidence #459

Open
nsaspy wants to merge 0 commits from rage/1-zara-coding-spec-verify into main
pull from: rage/1-zara-coding-spec-verify
merge into: nsaspy:main
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-08 02:20:01 +00:00
Owner
Copy link

Advances #1 with the first pure VERIFY bridge on top of the repository evidence merged in #104.

This slice:

  • keeps the frozen SPEC compiler outcome and observed repository state off argv and passes both over stdin as bounded data;
  • binds each observation to the exact frozen requirement ID, assertion, verifier, and collector identities;
  • emits only current source_class=repository, trust_class=observed evidence from the already-bounded repository snapshot;
  • calls canonical Prolog-RLM rlm_verify:spec_verify/4 with the immutable zara-coding assertion registry;
  • does not collect filesystem evidence inside Prolog, register callables, execute a plan, or expose another runtime;
  • rejects tampered/non-repository evidence before spawning SWI-Prolog.

TDD: RED 1f3476c1, runner 54ad1bbd, frozen-requirement observation binding 62e0b5fd.

Local isolated verification of the new Python bridge is green. Full repository registry/plugin/Nix gate is required before merge. No Zara Core, Android, dotfiles, or external todo changes.

Advances #1 with the first pure VERIFY bridge on top of the repository evidence merged in #104. This slice: - keeps the frozen SPEC compiler outcome and observed repository state off argv and passes both over stdin as bounded data; - binds each observation to the exact frozen requirement ID, assertion, verifier, and collector identities; - emits only current `source_class=repository`, `trust_class=observed` evidence from the already-bounded repository snapshot; - calls canonical Prolog-RLM `rlm_verify:spec_verify/4` with the immutable zara-coding assertion registry; - does not collect filesystem evidence inside Prolog, register callables, execute a plan, or expose another runtime; - rejects tampered/non-repository evidence before spawning SWI-Prolog. TDD: RED `1f3476c1`, runner `54ad1bbd`, frozen-requirement observation binding `62e0b5fd`. Local isolated verification of the new Python bridge is green. Full repository registry/plugin/Nix gate is required before merge. No Zara Core, Android, dotfiles, or external todo changes.
Some checks failed
CI / test (pull_request) Failing after 17s
Details
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-spec-verify:rage/1-zara-coding-spec-verify
git switch rage/1-zara-coding-spec-verify

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-spec-verify
git switch rage/1-zara-coding-spec-verify
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-spec-verify
git switch rage/1-zara-coding-spec-verify
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-spec-verify
git switch main
git merge --squash rage/1-zara-coding-spec-verify
git switch main
git merge --ff-only rage/1-zara-coding-spec-verify
git switch main
git merge rage/1-zara-coding-spec-verify
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
security

   
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara-plugins!459
No description provided.