Skip to content

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

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

@hyperpolymath hyperpolymath commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Summary

Owner ruling (g), 2026-11-13, extended 2026-11-14: an identity field carries only a v8 id. standards#1553 makes scripts/check-uuid-v8.sh and deed_lint.js reject a #u5 value there, so this repo would go red on its next governance run.

Changes to absolute-zero_chora.deed (identity values only, nothing else):

  • :repo-uuid is now #uuid"1ee6db20-7303-8af9-8540-30a475970fdc", the registry's uuid_v8 for github.com/hyperpolymath/absolute-zero, birth path under the gv-clade-index domain (U1: ids minted before V9 keep that domain; nothing is reminted).
  • :beholding-chora is now #uuid"0889b37b-defb-831f-973c-e119500db00e", the hyperpolymath estate id (chora:estate/github.com/hyperpolymath).

Checks

  • scripts/check-uuid-v8.sh from standards main: pass, on the file and on every tracked file.
  • bun 1-formats/deed/tools/deed_lint.js absolute-zero_chora.deed: OK.
  • I recomputed both ids from their preimages before use.

No licence or SPDX edits.


Generated by Claude Code

Summary by CodeRabbit

  • Chores
    • Updated internal metadata. This change does not alter any user-visible features or behavior. No changes to the app’s workflows, available capabilities, or experience are included in this update.

Replace the #u5 values of :repo-uuid and :beholding-chora with the
registry's uuid_v8 for this repo's birth path and the hyperpolymath
estate v8 id. No other change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZmZjDyQn9ggDLC2sRS
@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-14T15:45:37.062938Z 7b0c823 PR opened
🔒 Security Review ✅ Completed 2026-11-14T15:44:36.917849Z 7b0c823 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.

Walkthrough

The deed changes the values for :beholding-chora and :repo-uuid from #u5 strings to UUID literals.

Changes: Deed Values

Layer / File(s) Summary
UUID literal declarations
absolute-zero_chora.deed
The declarations for :beholding-chora and :repo-uuid now use UUID literals instead of #u5 string values.

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

Change: Bug fix

Merge Risk: Minimal · up to 7b0c8

The change replaces two identity values in the repository deed with registry v8 IDs. No concrete defect was found, and the reported lint and UUID checks passed. Merge risk is minimal.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title names the actual change: the deed's identity fields now carry the registry's v8 IDs, per ruling (g). The raw summary says the deed replaces :beholding-chora and :repo-uuid string values with…
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 actual change: the deed's identity fields now carry the registry's v8 IDs, per ruling (g). The raw summary says the deed replaces :beholding-chora and :repo-uuid string values with UUID literals, and the objectives say the change replaces #u5 values with registry v8 IDs. The title is specific and matches the changeset. It uses a conventional commit prefix and a reference to the ruling, which is acceptable.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • 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

Commits

Reviewing files that changed from the base of the PR and between 37b2ef9 and 7b0c823.

Files selected for processing: 1

  • absolute-zero_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.

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