Repository navigation
feat(seed): register affinescript late; add hub and satellite lineage types - #125
Merged
Merged
Conversation
… types Owner rulings of 2026-11-19 (kyX CLADE thread, by selector): - affinescript is registered with the v8 id of chora-registry:github.com/hyperpolymath/affinescript (0858724e-265e-81d0-909b-05cf7e1b4b2d), :minted-in chora-registry. The owner confirmed in the A1 thread the same day that no id is minted in gv-clade-index any more (it was renamed to chora-registry). - lineage satellite, parent nextgen-languages; the registry's LINEAGE set gains the #122 types hub and satellite. - placement clade-12 nl primary, provisional until the chora and CLADE data formats are fully mapped. Prepared by the kyX CLADE thread (session_0136P7ZpYHk11dMRWMDSEyFx), whose push was refused; reapplied here on main 24625ff and re-checked: the id re-derives with sync/uuid-v8.sh, worker/data is regenerated by sync/export-json.sh, and scripts/check-registry.sh passes (328 repos; all 327 of the base still registered, ids unchanged). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZoUeC49fDEvSwDNvuS
hyperpolymath
added a commit
that referenced
this pull request
Nov 19, 2026
## Summary In the A1 thread on 2026-11-19 the owner ruled, by selector, that the registry's `gv` rank-1 placement for `rsr-template-repo` is stale. The template ships governance files but is not a governance project, and its chora deed already dropped `gv`. Under CA1 (standards CHORA-SPEC §11.2) a chora copies its placements from the registry, so the registry is corrected here first. The matching standards fixture change is in metadatastician/standards, branch `chore/a1-rsr-fixture-clade-placements`. ## Changes - `verisim/seed/chora-registry_praxis.deed`: `rsr-template-repo` keeps `(placement :scheme clade-12 :category rm :primary #t)` only. A comment records the ruling. - `worker/data/index.json` and `worker/data/repos.json` are regenerated by `sync/export-json.sh`, so `gv` loses one member. ## RSR Quality Checklist ### Required - [x] Tests pass: `scripts/check-registry.sh` - [x] Code is formatted - [x] Linter is clean - [x] No banned language patterns - [x] No `unsafe` blocks without `// SAFETY:` comments (none) - [x] No banned functions - [x] SPDX license headers present on all new/modified source files (no new files) - [x] No secrets, credentials, or `.env` files included ## Testing `GV_BASE_REPOS_JSON=<main's repos.json> bash scripts/check-registry.sh` passes, with ids unchanged. ## Notes - This PR and #125 both regenerate `worker/data`. Whichever merges second will need a rebase and a fresh `export-json.sh` run, which I will do on request. - The commit is unsigned. The platform signing shim did not sign it, which standards CLAUDE.md treats as non-blocking. This PR is a draft for the owner to merge. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZoUeC49fDEvSwDNvuS)_ Co-authored-by: Claude <noreply@anthropic.com>
Contributor
|
🤖 Completed: Fix CodeRabbit issues in PR #125 — View commit |
<!-- coderabbit-ai-generated:v1 -->
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
This registers
hyperpolymath/affinescriptin the registry seed under the owner's rulings of 2026-11-19. The patch was prepared by the kyX CLADE thread, whose push was refused; this PR reapplies it onmain24625ffand re-checks it. kyx#9 (the translator) and affinescript#800 (its chora) depend on it landing.The rulings, each made by selector:
chora-registry:github.com/hyperpolymath/affinescript, which is0858724e-265e-81d0-909b-05cf7e1b4b2d, with:minted-in chora-registry. The owner also ruled in the A1 thread the same day thatgv-clade-index"should not exist as it was renamed to chora-registry", so no new or late id is minted in the old domain.satellite, parentnextgen-languages.clade-12nl, primary. It is provisional until the chora and CLADE data formats are fully mapped.Changes
verisim/seed/chora-registry_praxis.deed: adds the(repo :name "affinescript" …)record and raises:total-reposfrom 327 to 328.sync/parse-repos.js:LINEAGEgainshubandsatellite, the feat(api)!: reset /v1 to the chora model before its first deploy #122 lineage types named in standardsclade-to-repo-deed.adoc§3.README.adoc,docs/developer/REPO-ONBOARDING.adoc,docs/wikis/Core-Concepts.adocanddocs/wikis/Glossary.adoclist the two new lineage types.worker/data/index.jsonandworker/data/repos.jsonare regenerated bysync/export-json.sh.RSR Quality Checklist
Required
scripts/check-registry.shunsafeblocks without// SAFETY:comments (none).envfiles includedAs Applicable
Testing
printf 'hyperpolymath\taffinescript\tchora-registry\n' | bash sync/uuid-v8.shgives0858724e-265e-81d0-909b-05cf7e1b4b2d.sync/export-json.shregeneratedworker/data. The output matches the kyX thread's patch line for line, apart from thegeneratedtimestamp.GV_BASE_REPOS_JSON=<main's repos.json> bash scripts/check-registry.shpasses. Ids are unique. The archive holds 20 moved repos and 19 retired ids. All 327 repos of the base are still registered, followed by id, and their ids are unchanged.Follow-up (standards, A1)
CHORA-SPEC L1 still says late pre-V9 registrations use
gv-clade-index. The A1 thread reconciles L1 with the 2026-11-19 ruling in standards.The commit is unsigned: the platform's signing shim did not sign it. Per standards CLAUDE.md that does not block anything, and merging through the GitHub UI signs the merge commit.
This PR is a draft for the owner to merge.
Generated by Claude Code