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 - #175
Comment-only correction in .machine_readable/CLADE.a2ml. The 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 rename is NOT a phase change" now reads "A prefixed-name (clade code) change is NOT a phase change". The comment paragraph is re-wrapped at 80 columns; no data values change.
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 how UUIDs behave when items move or are renamed, and distinguished changes to prefixed names from phase changes.
The lifecycle comment now states that UUIDs follow the forge path and that a move or rename mints a new UUID. It also distinguishes prefixed-name changes from phase changes.
Changes: UUID lifecycle
Layer / File(s)
Summary
Lifecycle comment .machine_readable/CLADE.a2ml
The comment describes UUID changes when a forge path moves or is renamed. It specifies that prefixed-name changes are not phase changes.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: f2072066-efaf-440e-9b90-bc9dea6226e7
Commits
Reviewing files that changed from the base of the PR and between f682637 and 37eab6c.
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.
Recent review details
Context from checks skipped due to timeout: 6
GitHub Check: CodeRabbit
GitHub Check: Validate K9 contracts
GitHub Check: Groove manifest check
GitHub Check: Language registry consistency
GitHub Check: analyze (actions, none)
GitHub Check: semgrep-cloud-platform/scan
CI failures not shown inline: 2
GitHub Actions: Workflow Security Linter / 0_lint-workflows.txt: docs(clade): uuid follows the forge path, it is not immortal
##[group]Run gh actions-lock --verify-local
�[36;1mgh actions-lock --verify-local�[0m
shell: /usr/bin/bash -e {0}
##[endgroup]
opening lockfile: reading .github/workflows/actions.lock: line 4, column 10: lockfile version v0.0.3 is newer than this binary supports (v0.0.2); upgrade the tool that reads this lockfile to a build that supports v0.0.3; run `gh extension upgrade gh-actions-lock` to update
##[error]Process completed with exit code 2.
GitHub Actions: Workflow Security Linter / lint-workflows: docs(clade): uuid follows the forge path, it is not immortal
##[group]Run gh actions-lock --verify-local
�[36;1mgh actions-lock --verify-local�[0m
shell: /usr/bin/bash -e {0}
##[endgroup]
opening lockfile: reading .github/workflows/actions.lock: line 4, column 10: lockfile version v0.0.3 is newer than this binary supports (v0.0.2); upgrade the tool that reads this lockfile to a build that supports v0.0.3; run `gh extension upgrade gh-actions-lock` to update
##[error]Process completed with exit code 2.
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}
Comment-only correction in
.machine_readable/CLADE.a2ml. The 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 rename is NOT a phase change" now reads "A prefixed-name (clade code) change is NOT a phase change". The comment paragraph is re-wrapped at 80 columns; no data values change.Generated by Claude Code