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

zara-coding: validate and freeze SPECs with trusted assertions #461

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

Advances #1 from normalization into Prolog-RLM's canonical trusted validation/freezing path.

Adds a fixed plugin-owned assertion registry and coding.spec.compile:

  • uses canonical rlm_spec_lang:spec_source_compile/4 (normalize -> registry validation -> freeze);
  • SPEC source is bounded and passed only over stdin;
  • registry is immutable shipped code, never model-generated or dynamically registered;
  • admitted assertions are only repository_head and repository_clean v1;
  • both require current evidence with trust class trusted or observed;
  • both have observer:none, so compiling a SPEC cannot inspect files, run Git, or acquire capabilities;
  • pure evaluators are present for later evidence reconciliation through rlm_verify;
  • coding.spec.catalog now uses the exact same registry, so advertised assertions and admitted assertions cannot drift;
  • rejected Prolog-RLM outcomes remain explicit rejected evidence.

RED-first commit: 48d84cd6. No Core or external todo changes. Planning/execution and cross-plugin calls remain blocked behind Zara Core #400 rather than being duplicated here.

Full compatibility gate, registry/plugin tests and Nix package builds required before merge.

Advances #1 from normalization into Prolog-RLM's canonical trusted validation/freezing path. Adds a fixed plugin-owned assertion registry and `coding.spec.compile`: - uses canonical `rlm_spec_lang:spec_source_compile/4` (normalize -> registry validation -> freeze); - SPEC source is bounded and passed only over stdin; - registry is immutable shipped code, never model-generated or dynamically registered; - admitted assertions are only `repository_head` and `repository_clean` v1; - both require current evidence with trust class `trusted` or `observed`; - both have `observer:none`, so compiling a SPEC cannot inspect files, run Git, or acquire capabilities; - pure evaluators are present for later evidence reconciliation through `rlm_verify`; - `coding.spec.catalog` now uses the exact same registry, so advertised assertions and admitted assertions cannot drift; - rejected Prolog-RLM outcomes remain explicit `rejected` evidence. RED-first commit: `48d84cd6`. No Core or external todo changes. Planning/execution and cross-plugin calls remain blocked behind Zara Core #400 rather than being duplicated here. Full compatibility gate, registry/plugin tests and Nix package builds required before merge.
test(zara-coding): bind compiled assertions to repository root
Some checks failed
CI / test (pull_request) Failing after 17s
Details
7f0495f107
Some checks failed
CI / test (pull_request) Failing after 17s
Details
This pull request has changes conflicting with the target branch.
  • plugins/zara-coding/README.md
  • plugins/zara-coding/lib/zara_coding/plugin.py
  • plugins/zara-coding/prolog/zara_coding_assertions.pl
  • plugins/zara-coding/test/test_plugin.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

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

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-compile
git switch rage/1-zara-coding-spec-compile
git rebase main
git switch main
git merge --ff-only rage/1-zara-coding-spec-compile
git switch rage/1-zara-coding-spec-compile
git rebase main
git switch main
git merge --no-ff rage/1-zara-coding-spec-compile
git switch main
git merge --squash rage/1-zara-coding-spec-compile
git switch main
git merge --ff-only rage/1-zara-coding-spec-compile
git switch main
git merge rage/1-zara-coding-spec-compile
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!461
No description provided.