[hyperpolymath]

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 uuid follows 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 reads "A prefixed-name (clade code) change is NOT a phase change". That is the rename it means, and the two sentences no longer read as a contradiction.

One file, +6/−4, comment re-wrapped at 80 columns. No data value changes. Signed commit.

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

• Documentation
  • Clarified that moving or renaming an entity creates a new UUID, while changing its prefixed name preserves the UUID and phase and records the previous name as an alias.
  • Clarified that phase changes do not create a new UUID, including transitions from extinct to active.

The lifecycle-status comments now describe when moves or renames mint a new UUID. They distinguish prefixed-name changes from phase changes and specify how the old name is recorded in aliases[].

Changes: Lifecycle-status comments

Layer / File(s)	Summary
UUID and name rules .machine_readable/CLADE.a2ml	Comments state that a move or rename mints a new UUID. A prefixed-name change records the old name in aliases[] and leaves the UUID and phase unchanged.

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

Change: Other

Suggested reviewers: metadatastician

Merge Risk: Minimal · up to d05ae

The comment clarification is ready to merge; no actionable risk remains.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly summarises the UUID lifecycle wording change in the pull request.
Description check		The description explains the comment changes and their rationale, which relate directly to the changeset.
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: af26ab37-723d-4a18-9ad9-bc425b78f1aa

Commits

Reviewing files that changed from the base of the PR and between d05a7f5 and d05ae30.

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

• GitHub Check: CodeRabbit
• GitHub Check: analyze (actions, none)
• GitHub Check: estate-audit
• GitHub Check: Groove manifest check
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: Validate DEED manifests
• GitHub Check: analyze (rust, none)
• GitHub Check: Validate K9 contracts
• GitHub Check: semgrep-cloud-platform/scan

Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!