You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(clade): uuid follows the forge path, it is not immortal - #141
Comment-only correction. The CLADE status comment said the uuid is immortal. gv-clade-index ADR 0007 (accepted 2026-11-10) makes the uuid follow the forge path: a move or rename mints a new one, and a phase change never does.
A2ML is retired for new content. Correcting a factually wrong comment in an existing file is an edit, not new content.
Changes
.machine_readable/CLADE.a2ml: "uuid is immortal" → "uuid follows the forge path (a move or rename mints a new one, gv-clade-index ADR 0007; a phase change never does)"; "A rename is NOT a phase change" → "A prefixed-name (clade code) change is NOT a phase change". The paragraph is re-wrapped at 80 columns. No data values change. The wording is the same as in the correction PRs already merged across the estate.
RSR Quality Checklist
Required
Tests pass (just test or equivalent): not run locally. Comment-only change, left to CI.
Code is formatted (just fmt or equivalent): n/a, no code
Linter is clean (no new warnings or errors): n/a, no code
No banned language patterns
No unsafe blocks without // SAFETY: comments
No banned functions
SPDX license headers present on all new/modified source files (not touched)
No secrets, credentials, or .env files included
Testing
The diff is one comment paragraph in one file. Every line is ≤80 characters. The commit is signed.
The CLADE status comment said the uuid is immortal. gv-clade-index
ADR 0007 (accepted 2026-11-10) makes the uuid follow the forge path:
a move or rename mints a new one, and a phase change never does. A
prefixed-name (clade code) change still does not remint.
Comment-only correction. No data values change. A2ML is retired for
new content, but correcting a factually wrong comment in an existing
file is an edit, not new content.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZmTcNdC1jL1Vp3qW9H
Clarified that moving or renaming an item mints a new UUID, while changing its phase does not. Prefixed-name changes instead add the previous name to the aliases list without changing the UUID or phase.
The lifecycle comment now states that UUIDs follow the forge path. A move or rename mints a new UUID. It distinguishes prefixed-name changes from phase changes.
The clarification does not change data or runtime behavior. No actionable merge risk remains.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly describes the main change: updating the CLADE documentation to state that UUIDs follow the forge path rather than being immortal.
Description check
The description includes the required Summary, Changes, RSR Quality Checklist and Testing sections. It explains the change and reports that tests were not run locally. The Screenshots section and some…
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Description check
Explanation
The description includes the required Summary, Changes, RSR Quality Checklist and Testing sections. It explains the change and reports that tests were not run locally. The Screenshots section and some applicable checklist items are omitted, but the description is mostly complete.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
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.
The reason will be displayed to describe this comment to others. Learn more.
Additional comments: 1
.machine_readable/CLADE.a2ml: 1
19-19: Major · Data Integrity & Integration · Heavy lift
Unverified finding
Verification ran but could not confirm this finding. It is shown for review, not as a verified issue.
Correct the declared primary forge path.
This record names hyperpolymath/vcl-total, but this repository is hyperpolymath/vcl-ut. The README identifies vcl-total as the crate name. (raw.githubusercontent.com)
The registry uses the GitHub path for repository identity, so this declaration points to the wrong repository. Update the primary path and names, and derive the UUID from the correct path. (github.com)
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: 6d248e28-82dc-4901-b55b-c36b48052e4e
Commits
Reviewing files that changed from the base of the PR and between 5b10cb0 and dc274f8.
Files selected for processing: 1
.machine_readable/CLADE.a2ml
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
On CodeRabbit's Major note (line 19, forge path says vcl-total). I checked it. The finding is real, but it isn't caused by this PR, and the fix is a data change that doesn't belong in this one.
The uuid (581e7dc6-…) is already right for this repo: it equals UUIDv5(URL, github.com/hyperpolymath/vcl-ut).
The fields still on the old name are canonical-name = "vcl-total", prefixed-name = "rm-vcl-total", and all three [forges] paths.
So a rename from vcl-total to vcl-ut was only half applied. Completing it means updating those fields, and, per ADR 0006/0007, deciding whether rm-vcl-total goes to aliases[]. That changes identity data, so this comment-only PR leaves it alone. I've flagged it to the owner for a separate fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Comment-only correction. The CLADE status comment said the uuid is immortal. gv-clade-index ADR 0007 (accepted 2026-11-10) makes the uuid follow the forge path: a move or rename mints a new one, and a phase change never does.
A2ML is retired for new content. Correcting a factually wrong comment in an existing file is an edit, not new content.
Changes
.machine_readable/CLADE.a2ml: "uuid is immortal" → "uuid follows the forge path (a move or rename mints a new one, gv-clade-index ADR 0007; a phase change never does)"; "A rename is NOT a phase change" → "A prefixed-name (clade code) change is NOT a phase change". The paragraph is re-wrapped at 80 columns. No data values change. The wording is the same as in the correction PRs already merged across the estate.RSR Quality Checklist
Required
just testor equivalent): not run locally. Comment-only change, left to CI.just fmtor equivalent): n/a, no codeunsafeblocks without// SAFETY:comments.envfiles includedTesting
The diff is one comment paragraph in one file. Every line is ≤80 characters. The commit is signed.
Generated by Claude Code