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

zara-coding: expose canonical Prolog-RLM SPEC catalog #469

Open
nsaspy wants to merge 5 commits from rage/1-spec-language-catalog into main
pull from: rage/1-spec-language-catalog
merge into: nsaspy:main
Conversation 0 Commits 5 Files changed 5 +96 -29
nsaspy commented 2026-09-08 02:20:04 +00:00
Owner
Copy link

Advances #1.

Slice

  • RED-first bridge contract for Prolog-RLM spec_language_catalog/2
  • coding.spec.catalog exposes the canonical closed SPEC structural vocabulary
  • the bridge deliberately passes an empty trusted assertion registry, so no Zara/plugin-owned semantic callables are fabricated
  • shared bounded SWI-Prolog execution path keeps fixed goals, timeout, argv-only execution, and honest runtime failures
  • docs make provider-backed validation/freezing the next explicit integration seam

This does not create a second SPEC IR, install model-selected validators/evaluators, execute model Prolog, or claim provider-backed validation exists.

Upstream compatibility evidence

Current Prolog-RLM documents SPEC source -> canonical Spec -> validate -> freeze, exports spec_language_catalog/2 and spec_source_compile/4, and keeps assertion registration trusted/non-model-facing.

Gate

Merge only after exact-head CI passes compatibility contract tests, full registry/plugin tests, package builds, and Nix checks.

Advances #1. ## Slice - RED-first bridge contract for Prolog-RLM `spec_language_catalog/2` - `coding.spec.catalog` exposes the canonical closed SPEC structural vocabulary - the bridge deliberately passes an empty trusted assertion registry, so no Zara/plugin-owned semantic callables are fabricated - shared bounded SWI-Prolog execution path keeps fixed goals, timeout, argv-only execution, and honest runtime failures - docs make provider-backed validation/freezing the next explicit integration seam This does not create a second SPEC IR, install model-selected validators/evaluators, execute model Prolog, or claim provider-backed validation exists. ## Upstream compatibility evidence Current Prolog-RLM documents `SPEC source -> canonical Spec -> validate -> freeze`, exports `spec_language_catalog/2` and `spec_source_compile/4`, and keeps assertion registration trusted/non-model-facing. ## Gate Merge only after exact-head CI passes compatibility contract tests, full registry/plugin tests, package builds, and Nix checks.
docs(zara-coding): document canonical SPEC catalog boundary
Some checks failed
CI / test (pull_request) Failing after 21s
Details
428ccb6ca4
Some checks failed
CI / test (pull_request) Failing after 21s
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/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-spec-language-catalog:rage/1-spec-language-catalog
git switch rage/1-spec-language-catalog

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-spec-language-catalog
git switch rage/1-spec-language-catalog
git rebase main
git switch main
git merge --ff-only rage/1-spec-language-catalog
git switch rage/1-spec-language-catalog
git rebase main
git switch main
git merge --no-ff rage/1-spec-language-catalog
git switch main
git merge --squash rage/1-spec-language-catalog
git switch main
git merge --ff-only rage/1-spec-language-catalog
git switch main
git merge rage/1-spec-language-catalog
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!469
No description provided.