Skip to content

fix(deed): carry the registry's v8 id in identity fields (ruling g) - #76

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/deed-v8-identity-ids
Nov 14, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
fix/deed-v8-identity-ids

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Changes in 0-AI-MANIFEST.deed and pons-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

@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-14T17:02:04.913439Z 49c9746 PR opened
🔒 Security Review ✅ Completed 2026-11-14T17:02:37.257661Z 49c9746 PR opened
ℹ️ 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.

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Chores
    • Updated the project’s Chora reference to use its repository-qualified identifier across the relevant project metadata. This is a metadata-only change; no user-facing functionality or public entities have changed.

The :beholding-chora value changes from #u5"estate/chora" to #u8"chora:estate/github.com/hyperpolymath" in both deed files.

Changes: Beholding-chora value update

Layer / File(s) Summary
Update the declared value
0-AI-MANIFEST.deed, pons-asinorum_chora.deed
Both files change the :beholding-chora value to #u8"chora:estate/github.com/hyperpolymath".

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: Minimal · up to 49c97

This updates the estate chora identity value in two deed metadata files to the v8 form. No in-repo consumer of the field was found, and no concrete break was identified. External registry resolution was not verifiable here, but it is not an established defect.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the change: the deed identity field now carries the registry's v8 id, referenced as ruling g. It matches the raw summary, which states that the :beholding-chora value changes from a #u…
Description check Passed The description lists the exact before and after values of the :beholding-chora field in both deed files. It explains that the :repo-uuid field is unchanged because both deeds already use a #u8 value,…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the change: the deed identity field now carries the registry's v8 id, referenced as ruling g. It matches the raw summary, which states that the :beholding-chora value changes from a #u5 estate/chora value to a #u8 chora:estate/github.com/hyperpolymath value in both deed files. The title is specific to the main change and uses the fix(deed) convention. It does not describe the registry as being updated, which is a minor imprecision, but the title is clearly related to the changeset.

Full details: Description check

Explanation

The description lists the exact before and after values of the :beholding-chora field in both deed files. It explains that the :repo-uuid field is unchanged because both deeds already use a #u8 value, and it gives the reason for using the computed #u8 form until the repository is registered. It also states that no licence or SPDX edits were made. The description is directly related to the changeset and matches the raw summary and objectives.

  • 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

Recent review info

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: 398818ee-d26c-41a1-b540-dd7cdd93e943
Commits

Reviewing files that changed from the base of the PR and between d4adad0 and 49c9746.

Files selected for processing: 2

  • 0-AI-MANIFEST.deed
  • pons-asinorum_chora.deed

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 12

  • GitHub Check: CodeRabbit
  • GitHub Check: scan / rust-secrets
  • GitHub Check: scan / gitleaks
  • GitHub Check: scan / shell-secrets
  • GitHub Check: check
  • GitHub Check: Windows portability
  • GitHub Check: CodeQL Analysis (rust)
  • GitHub Check: I-JSON/JCS and KYAML ratchets
  • GitHub Check: Provenance and coverage
  • GitHub Check: squabble
  • GitHub Check: CodeQL Analysis (actions)
  • GitHub Check: semgrep-cloud-platform/scan
Additional comments: 1

0-AI-MANIFEST.deed: 1

7-7: Data Integrity & Integration

Confirm that #u8"chora:estate/github.com/hyperpolymath" resolves to the estate chora.

The #u8 literal is valid, but the new preimage differs from the previous #u5"estate/chora". Consumers resolve :beholding-chora by UUID. The supplied evidence does not show that the estate chora is registered under this preimage, or that a consumer alias maps the old identifier to the new one.

Before merge, confirm one of the following:

  • The estate chora registry lists the UUID derived from chora:estate/github.com/hyperpolymath.
  • A consumer alias or migration rule maps the previous #u5"estate/chora" identifier to the new value.

If neither exists, consumers that resolve :beholding-chora may fail to find the vocabulary for this repository.

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit b1d1b59 into main Nov 14, 2026
15 checks passed
@hyperpolymath
hyperpolymath deleted the fix/deed-v8-identity-ids branch November 14, 2026 17:23
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