Skip to content

chore(registry): follow the rename to chora-registry; ids unchanged - #117

Merged
hyperpolymath merged 1 commit into
mainfrom
a1/chora-registry-rename
Nov 14, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
a1/chora-registry-rename

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

On 2026-11-14 GitHub renamed hyperpolymath/gv-clade-index to hyperpolymath/chora-registry. This PR carries out the follow-up that #115 named.

No id changes. The repo keeps #uuid"a65b74d8-351a-89d9-a38d-aea470863b03" (rule U1). That id keeps its gv-clade-index minting domain for good (rule V9).

Changes

  • The repo's own deed. gv-clade-index_chora.deed is renamed chora-registry_chora.deed.
    • :canonical-name, :prefixed-name and (forges :github) take the new name.
    • (lineage) gains :previous-names ("gv-clade-index").
    • :repo-uuid is unchanged, and the file lints OK.
  • The registry's record of itself. In the seed, its entry becomes :name "chora-registry".
    • It gains (former :generation 1 :path "hyperpolymath/gv-clade-index" :until "2026-11-14").
    • uuid and uuid_v8 are unchanged, because the birth path is the same.
    • archive.json gains the move record.
    • repos.json and index.json now serve the new name, github, prefixed and description.
  • Gate fix. Section 7 of scripts/check-registry.sh (never removed) now follows a repo by its id, not by its name.
    • Main's gate fails this rename. It reports "removed from the seed: gv-clade-index", even though the id is still registered. I ran main's gate against this tree to confirm.
    • A real removal still fails, and so does an id change: planted cases 17 and 18.
    • A rename now passes: new planted case 24.
  • Files that name the deed now use the new file name: the AI rule files, 0-AI-MANIFEST.deed, README, QUICKSTART, www/.well-known/ai.txt and docs/practice.
    • The Justfile project and REPO values also take the new name.
    • So do the wrangler.toml DATA_SOURCE_URL and the worker's source link.
  • Docs. REPO-ONBOARDING no longer calls a clade placement an "optional finding aid". A placement is an identity fact (A7 W10).

Deliberately not changed:

  • The gv-clade-index minting domain in sync/ and in the seed's :minted-in (V9).
  • The cache directory names.
  • The served registry: 'gv-clade-index' field in worker/src/index.js. That is an API value; changing it is the owner's call.
  • Historical docs: ADRs, reports, CHANGELOG and docs/history.

Testing

  • bash scripts/check-registry.sh passes. With GV_BASE_REPOS_JSON set to main's repos.json, all 327 base repos are still registered, followed by id, with ids unchanged.
  • bash tests/check-registry-test.sh passes. The 19 planted failures fire, and the rename case passes.
  • shellcheck -S warning is clean.
  • deed_lint reports OK on chora-registry_chora.deed.

This PR stays a draft for the owner. The repo has no stamped proven-lock-gate, so I do not self-merge it.


Generated by Claude Code

GitHub renamed hyperpolymath/gv-clade-index to hyperpolymath/chora-registry
on 2026-11-14. This follows it, as #115 named:

- gv-clade-index_chora.deed becomes chora-registry_chora.deed; its
  :canonical-name, :prefixed-name and (forges :github) follow, and (lineage)
  gains :previous-names ("gv-clade-index"). :repo-uuid is unchanged (U1).
- The seed record becomes :name "chora-registry" with (former :generation 1
  :path "hyperpolymath/gv-clade-index" :until "2026-11-14"). Its uuid and
  uuid_v8 are unchanged and keep the gv-clade-index minting domain (V9);
  archive.json records the birth path.
- scripts/check-registry.sh section 7 follows a repo by its id, not its
  name. Before, a rename read as a removal ("removed from the seed:
  gv-clade-index"); a removal and an id change still fail. Planted case 24
  shows a rename passing; cases 17 and 18 still fire.
- Readers that name the deed (AI rule files, 0-AI-MANIFEST.deed, README,
  docs) and the Justfile project name, wrangler DATA_SOURCE_URL and the
  worker's source link follow the new name. The minting domain, the cache
  directory names and the served `registry` field are left as they are.
- REPO-ONBOARDING no longer calls a clade placement a finding aid (W10).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZoUeC49fDEvSwDNvuS
@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 37 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 454b33af-ee2a-451c-a1cb-eaf18d016029
Commits

Reviewing files that changed from the base of the PR and between ec65e2e and e93d4b7.

Files selected for processing: 21

  • .github/copilot-instructions.md
  • .machine_readable/ai/.clinerules
  • .machine_readable/ai/.cursorrules
  • .machine_readable/ai/.windsurfrules
  • .machine_readable/ai/README.adoc
  • 0-AI-MANIFEST.deed
  • Justfile
  • QUICKSTART-DEV.adoc
  • README.adoc
  • chora-registry_chora.deed
  • docs/developer/REPO-ONBOARDING.adoc
  • docs/practice/AI-CONVENTIONS.adoc
  • scripts/check-registry.sh
  • tests/check-registry-test.sh
  • verisim/seed/chora-registry_praxis.deed
  • worker/data/archive.json
  • worker/data/index.json
  • worker/data/repos.json
  • worker/src/index.js
  • worker/wrangler.toml
  • www/.well-known/ai.txt
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 14, 2026 20:45
@hyperpolymath
hyperpolymath merged commit 57607d3 into main Nov 14, 2026
20 checks passed
@hyperpolymath
hyperpolymath deleted the a1/chora-registry-rename branch November 14, 2026 20:45
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T20:50:21.041946Z e93d4b7 Draft marked ready
🔒 Security Review ✅ Completed 2026-11-14T20:48:56.564004Z e93d4b7 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e93d4b7481

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread 0-AI-MANIFEST.deed
:beholding-chora #uuid"0889b37b-defb-831f-973c-e119500db00e"
(front-doors
:machine "gv-clade-index_chora.deed"
:machine "chora-registry_chora.deed"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the manifest's canonical name too

After the rename, machine consumers entering through this manifest still read :canonical-name "gv-clade-index" on line 12, while the referenced deed and registry now declare chora-registry. This leaves the machine entry point reporting two conflicting current identities for the same UUID; update the manifest's canonical name and its stale header description along with the front-door path.

Useful? React with 👍 / 👎.

Comment thread worker/data/index.json
Comment on lines +954 to +955
"chora-registry": {
"name": "chora-registry",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the old resolver names after the rename

Existing requests to /v1/repo/gv-clade-index now return 404 because route only evaluates index.by_name[name], and existing CLADE-gv-gv-clade-index autolinks likewise fail because /c/:binomial only searches current prefixed values. The repository's lifecycle model explicitly retains former prefixed names as aliases, so export an alias for the old canonical/binomial names and make both resolvers consult it or redirect to chora-registry.

Useful? React with 👍 / 👎.

Comment thread worker/data/repos.json
{"name":"mtpc-template-repo","uuid":"a7feab15-3c46-5173-b3b8-f296409bd738","uuid_v8":"5e787e7b-2f77-8b25-8b32-cd6f621dd97f","clade":"rm","secondary":[],"lineage":"standalone","parent":"","description":"MTPC template repository","prefixed":"rm-mtpc-template-repo","github":"hyperpolymath/mtpc-template-repo"},
{"name":"v3-templater","uuid":"e1db84dc-2090-544d-ab6c-2396096bddf9","uuid_v8":"59e7f13a-d429-872b-8228-f4cb6ce459eb","clade":"rm","secondary":[],"lineage":"standalone","parent":"","description":"V3 template generation tool","prefixed":"rm-v3-templater","github":"hyperpolymath/v3-templater"},
{"name":"gv-clade-index","uuid":"c88e9ff3-9aac-5de8-b891-19b5de64aedd","uuid_v8":"a65b74d8-351a-89d9-a38d-aea470863b03","clade":"gv","secondary":["db"],"lineage":"standalone","parent":"","description":"THIS REPO — clade taxonomy + VeriSimDB portal registry","prefixed":"gv-gv-clade-index","github":"hyperpolymath/gv-clade-index"},
{"name":"chora-registry","uuid":"c88e9ff3-9aac-5de8-b891-19b5de64aedd","uuid_v8":"a65b74d8-351a-89d9-a38d-aea470863b03","clade":"gv","secondary":["db"],"lineage":"standalone","parent":"","description":"THIS REPO — the register of repo identities and their classification schemes (VeriSimDB portal)","prefixed":"gv-chora-registry","github":"hyperpolymath/chora-registry"},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the old VeriSimDB document during the rename

When the hourly refresh runs against a VeriSimDB previously seeded with this repository, seedFromStaticJson PUTs the new record under repo.name but never removes keys absent from the new snapshot, so clade:repos/gv-clade-index remains alongside this new chora-registry document. Both /v1/query/language and /v1/query/tag list the entire VeriSimDB collection and can therefore return the stale old record, or both identities in one result; migrate or delete the old storage key as part of this rename.

Useful? React with 👍 / 👎.

hyperpolymath added a commit that referenced this pull request Nov 14, 2026
## Summary

#115 merged with five Codex P2 findings still open. This PR fixes them.
A1, who owns this repo, asked for it as a PR separate from the rename
(#117). It is cut from main 57607d3, which already includes #117.

## Changes

1. **`.machine_readable/svc/k9/examples/setup-repo.k9.ncl`**
- `checkpoint_files` now defaults to `false`, with a comment pointing to
the root `<repo>_chora.deed` and
`.machine_readable/descriptiles/STATE.deed`.
- The `create-checkpoint-files` recipe no longer writes
STATE/ECOSYSTEM/META `.a2ml` files. It prints a pointer to the deed and
exits 1.
   - No new deed form is invented.
2. **`docs/governance/RELEASE-RUNBOOK.adoc`**: the bookkeeping rule and
the Phase 2/3/4/6 gates now update the phase Status in the root
`ROADMAP.adoc`. The VPS fact cites `docs/SPEC-clade-verisim-portal.adoc`
Layer 3. No `STATE.a2ml` references remain.
3. **`.github/workflows/rhodibot.yml`**
- The workflow now scans the whole repo, `9-archive/` included, and
fails on any `.a2ml` except the three allowlisted files:
`verisim/config.a2ml`, `verisim/seed/clades.a2ml` and
`verisim/seed/forges.a2ml`.
   - No `${{ }}` in `run:`, and the `uses:` lines are unchanged.
4. **`.machine_readable/ai/.clinerules`, line 16 only**: identity is the
root `chora-registry_chora.deed`; descriptive deeds live in
`.machine_readable/descriptiles/`.
5. **`docs/RSR_OUTLINE.adoc:122`**: `just state-touch` is replaced by
the manual `:affirmed` review. The Justfile is not edited.

## Verification

- **Rhodibot scan**, step extracted with yq and run with bash:
  - current tree: clean, rc=0;
  - planted `9-archive/old/STATE.a2ml` plus `docs/stray.a2ml`: rc=1;
  - only the `9-archive/` plant: rc=1;
- planted root `0-AI-MANIFEST.a2ml` plus the near-miss
`verisim/seed/x/clades.a2ml`: both flagged, rc=1;
  - plants removed: clean again.
- `scripts/check-registry.sh`: PASS, 327 repos. Also PASS against main's
`repos.json`: no id changed.
- `tests/check-registry-test.sh`: PASS, all 19 planted failures fire.
- `just fmt-check`, `just lint` and `just validate-state`: OK.
- `nickel typecheck` and `nickel export` on the k9 component: OK.
- A1's guardrail files are untouched, no `.a2ml` is created, and no id
is changed.

## Departures seen, not fixed

- `docs/RSR_OUTLINE.adoc` is still a stale template copy: it recommends
A2ML files, says to use Deno and not Bun, lists ReScript as tier 1, and
carries Palimpsest badges (licence material, flag only).
- `.clinerules` lines 27–30 reverse the current policy ("TypeScript →
ReScript", "bun → Deno"), and line 3 points at a missing `.md`.
- The `add-license` recipe in `setup-repo.k9.ncl` fetches PMPL-1.0. That
is licence drift, flag only.
- `dogfood-gate.yml` interpolates `${{ steps.detect.outputs.* }}` into
`run:`.

---
_Generated by [Claude
Code](https://claude.ai/code/session_0136P7ZoBy5xGnGDLk7wQ8jC)_

Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath pushed a commit that referenced this pull request Nov 14, 2026
…deed and TOPOLOGY

- dogfood-gate.yml: actions/checkout pinned to
  3d3c42e5aac5ba805825da76410c181273ba90b1 (v7.0.1), as every other workflow
  here already is; the lockfile entry is unchanged.
- STATE.deed: :canonical-name "chora-registry" (the chora deed's name since
  #117); :of-chora is unchanged.
- TOPOLOGY.adoc: names chora-registry, says what the seed is, and drops the
  stale .md title.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZoUeC49fDEvSwDNvuS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants