[hyperpolymath]

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. The comment's "A rename is NOT a phase change" now says "A prefixed-name (clade code) change", the rename it means. Paragraph re-wrapped at 80 columns; no data value changes.

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

• Documentation
  • Clarified that moving or renaming a forge creates a new UUID, while changing its phase does not.
  • Documented that changing a prefixed name preserves the UUID and phase, and adds the previous name to the aliases list.

The lifecycle comments now state that a forge move or rename mints a new UUID, while a phase change does not. They also clarify that a prefixed-name change adds the old name to aliases[] without changing the UUID or phase.

Changes: UUID lifecycle clarification

Layer / File(s)	Summary
Clarify lifecycle rules .machine_readable/CLADE.a2ml	The comments distinguish UUID changes caused by a forge move or rename from phase changes. They state that a prefixed-name change adds the old name to aliases[] and leaves the UUID and phase unchanged.

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

Change: Other

Merge Risk: Minimal · up to 66855

The change clarifies UUID and alias lifecycle comments; no merge-blocking issue was identified.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly describes the UUID lifecycle correction, which is the main change.
Description check		The description explains the comment correction and states that no data values changed.
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.

• 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

• X
• Mastodon
• Reddit
• LinkedIn

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: 59a1fb2f-8143-454a-b47f-1adbac2fae46

Commits

Reviewing files that changed from the base of the PR and between 093a4e8 and 6685529.

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: 3

• GitHub Check: CodeRabbit
• GitHub Check: analyze (actions, none)
• GitHub Check: semgrep-cloud-platform/scan

Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!