Repository navigation
fix(deed): carry the registry's v8 id in identity fields (ruling g) - #76
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZmZjDyQn9ggDLC2sRS
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
|



Changes in
0-AI-MANIFEST.deedandpons-asinorum_chora.deed(identity values only), in each::beholding-chora #u5"estate/chora"->:beholding-chora #u8"chora:estate/github.com/hyperpolymath"Neither deed has a
#u5:repo-uuid(both already carry#u8"gv-clade-index:github.com/hyperpolymath/pons-asinorum"), so that field is unchanged.Birth-path evidence: created=2026-07-08 | root=2026-07-08T17:49:46+01:00 | all_paths=[github.com/hyperpolymath/pons-asinorum ]
The registry (gv-clade-index) does not list this repo yet, and its seed is an A2ML file that may not be extended, so the repo-uuid is written as the computed #u8 form; it moves to #uuid with the registry's id once the repo is registered.
No licence or SPDX edits.
Generated by Claude Code