Skip to content

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

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

hyperpolymath merged 2 commits into
mainfrom
fix/deed-v8-identity-ids

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Changes only anytype_chora.deed:

  • :beholding-chora #u5"estate/chora" -> :beholding-chora #u8"chora:estate/github.com/hyperpolymath"

:repo-uuid already carries #u8"gv-clade-index:github.com/hyperpolymath/anytype", so it is not edited.

Birth-path evidence: created=2026-06-26 | root=2026-06-26T10:03:10+01:00 | all_paths=[github.com/hyperpolymath/anytype ]

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:16.674264Z f4b65d1 PR opened
🔒 Security Review ✅ Completed 2026-11-14T17:02:34.308887Z f4b65d1 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 →

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 50 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: 19154ad4-39e8-458e-a9f6-aeee3d16d550
Commits

Reviewing files that changed from the base of the PR and between f4b65d1 and baddf6e.

Files selected for processing: 2

  • .machine_readable/coaptation/receipts/latest.a2ml
  • CLAUDE.md

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Chores
    • Updated the Chora identifier used by the app.

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

Changes: Beholding Chora value

Layer / File(s) Summary
Update the Chora value
anytype_chora.deed
The :beholding-chora declaration now uses #u8"chora:estate/github.com/hyperpolymath" instead of #u5"estate/chora".

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

Change: Bug fix

Merge Risk: Minimal · previous review f4b65

This updates an identity value in a draft deed file that no repository tooling reads. There is no identified runtime or build impact, so the change is low risk to merge.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the change: it fixes the deed by carrying the registry's v8 identifier in identity fields. The diff changes only the :beholding-chora value from #u5 to #u8 form, so the title matches t…
Description check Passed The description gives a clear summary and lists the single change. It explains why :repo-uuid is unchanged and why the #u8 form is used for now. It includes birth-path evidence and notes that no licen…
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: it fixes the deed by carrying the registry's v8 identifier in identity fields. The diff changes only the :beholding-chora value from #u5 to #u8 form, so the title matches the change. It uses a conventional commit prefix and a specific reference to the ruling. It is somewhat technical, but a teammate scanning history would understand the primary change.

Full details: Description check

Explanation

The description gives a clear summary and lists the single change. It explains why :repo-uuid is unchanged and why the #u8 form is used for now. It includes birth-path evidence and notes that no licence or SPDX edits were made. It does not follow the repository template: the RSR Quality Checklist is missing, the Testing section has no content, and the Changes section lacks the checklist items. Required checks such as tests, formatting and linting are not addressed. The description is mostly complete on purpose, but it omits several template sections.

Resolution

Consider adding a Testing section that states how the change was checked, and completing the RSR Quality Checklist (for example, whether tests, formatting and the linter were run). Mark any items that do not apply. A Closes # link is also useful if a related issue exists.

  • 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: 2e10ed57-313b-4472-b040-be55fbea8ad6
Commits

Reviewing files that changed from the base of the PR and between 8f01813 and f4b65d1.

Files selected for processing: 1

  • anytype_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: 23

  • GitHub Check: CodeRabbit
  • GitHub Check: scan / gitleaks
  • GitHub Check: Runtime Policy
  • GitHub Check: docs
  • GitHub Check: panic-attack assail
  • GitHub Check: check
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Patch Bridge CVE triage
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Groove manifest check
  • GitHub Check: estate-rules
  • GitHub Check: SonarQube
  • GitHub Check: Validate DEED manifests
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: lint
  • GitHub Check: Estate Governance Policy
  • GitHub Check: check
  • GitHub Check: openssf-compliance
  • GitHub Check: Rust standalone tools and workspace gate
  • GitHub Check: Hypatia Neurosymbolic Analysis
  • GitHub Check: analyze (actions, none)
  • GitHub Check: semgrep-cloud-platform/scan
Additional context used

Code guidelines: 1

.github/copilot-instructions.md — auto-discovered
Path-based instructions: 1

Source excerpt: Never use AGPL-3.0.

CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

  • anytype_chora.deed
Additional comments: 1

anytype_chora.deed: 1

41-41: Data Integrity & Integration

The comment asks for external verification without a demonstrated defect. The form is legal, the header marks this key as inert, and no repository consumer reads it. The claimed rejection or misidentification has no inspected binding and no current consequence in this repository.

@sonarqubecloud

Copy link
Copy Markdown

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