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 - #101
Comment-only correction. The [status] comment in .machine_readable/CLADE.a2ml, written by clade-status-backfill (gv-clade-index ADR 0006), said "uuid is immortal". gv-clade-index ADR 0007, accepted 2026-11-10, says the opposite: the uuid follows the forge path, so a move or rename mints a new one, and a phase change never does.
Changes
.machine_readable/CLADE.a2ml: that claim replaced. "A rename is NOT a phase change" now reads "A prefixed-name (clade code) change is NOT a phase change", the rename it means. Comment re-wrapped at 80 columns. No data value changes.
RSR Quality Checklist
Required
Tests pass: no code changed
Code is formatted
Linter is clean
No banned language patterns
No unsafe blocks without // SAFETY: comments
No banned functions
SPDX license headers present on all new/modified source files
Comment-only correction. The CLADE status comment written by
clade-status-backfill (gv-clade-index ADR 0006) 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. The same comment's "A rename is NOT a phase change"
now says "A prefixed-name (clade code) change", the rename it means, so
the two sentences no longer read as a contradiction. No data value
changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZmtCj9Doze7s38qbz5
No actionable comments were generated in the recent review.
Summary
Summary by CodeRabbit
Documentation
Clarified that a UUID follows the forge path and that moving or renaming it results in a new UUID.
Documented that changing a phase does not create a new UUID, and distinguished prefixed-name changes from phase changes.
The lifecycle-status comment now describes when a UUID changes and clarifies the distinction between prefixed-name changes and phase changes.
Changes: Lifecycle status
Layer / File(s)
Summary
Clarify lifecycle status comment .machine_readable/CLADE.a2ml
The comment states that a forge-path move or rename mints a new UUID, while a phase change does not. It also states that a prefixed-name change does not change the phase.
The change clarifies lifecycle documentation. No concrete merge-blocking issue was identified.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title clearly identifies the documentation change and its main point: the UUID follows the forge path and is not immortal.
Description check
The description includes a summary, key changes, the required checklist and testing information. The missing applicable-checklist and screenshots sections are not critical for this comment-only change…
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 a summary, key changes, the required checklist and testing information. The missing applicable-checklist and screenshots sections are not critical for this comment-only change.
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.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: a24849e2-e53f-4300-81fd-22f5c9e7490b
Commits
Reviewing files that changed from the base of the PR and between 96cfa4f and 418777e.
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.
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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary
Comment-only correction. The
[status]comment in.machine_readable/CLADE.a2ml, written byclade-status-backfill(gv-clade-index ADR 0006), said "uuid is immortal". gv-clade-index ADR 0007, accepted 2026-11-10, says the opposite: the uuid follows the forge path, so a move or rename mints a new one, and a phase change never does.Changes
.machine_readable/CLADE.a2ml: that claim replaced. "A rename is NOT a phase change" now reads "A prefixed-name (clade code) change is NOT a phase change", the rename it means. Comment re-wrapped at 80 columns. No data value changes.RSR Quality Checklist
Required
unsafeblocks without// SAFETY:comments.envfiles includedTesting
Comment-only; one file, +6/−4. Signed commit.
Generated by Claude Code