[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 how identifiers and lifecycle phases behave: moving or renaming an item creates a new UUID, while changing its phase does not.
  • Clarified that changing a prefixed name does not change its phase. The previous name is retained as an alias, and the UUID and phase remain unchanged.

The lifecycle-status comment now states that a move or rename mints a new UUID. It distinguishes this from changing a prefixed name, which leaves the UUID and phase unchanged and adds the old name to aliases[].

Changes: Lifecycle-status wording

Layer / File(s)	Summary
Clarify UUID and prefixed-name wording .machine_readable/CLADE.a2ml	The comment states that UUIDs follow the forge path, so a move or rename mints a new UUID. It clarifies that changing a prefixed name leaves the UUID and phase unchanged and adds the old name to aliases[].

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

Change: Other

Merge Risk: Minimal · up to 31151

The clarification matches the documented lifecycle rules. CodeQL currently fails on an unrelated action pin.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly describes the UUID wording change in the CLADE documentation.
Description check		The description explains the UUID and prefixed-name comment changes, which match 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: 6b9b6435-7006-4038-b432-10f480e92c95

Commits

Reviewing files that changed from the base of the PR and between 98f0ac0 and 3115143.

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: test (nightly, ubuntu-latest)
• GitHub Check: test (1.10, ubuntu-latest)
• GitHub Check: test (nightly, macos-latest)
• GitHub Check: test (1.11, macos-latest)
• GitHub Check: test (1.10, macos-latest)

CI failures not shown inline: 2

GitHub Actions: CodeQL Security Analysis / 0_analyze (actions).txt: docs(clade): uuid follows the forge path, it is not immortal

Conclusion: failure

View job details

##[group]GITHUB_TOKEN Permissions
 Contents: read
 Metadata: read
 SecurityEvents: write
 ##[endgroup]
 Secret source: Actions
 Cache mode: write
 Using locked action versions from the workflow's lockfile
 Prepare workflow directory
 Prepare all required actions
 Getting action download info
 ##[error]Unable to resolve action `actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1`: invalid lockfile pin. Run `gh actions-lock` to update the lockfile. lockfile verification did not produce a result for this action

GitHub Actions: CodeQL Security Analysis / analyze (actions): docs(clade): uuid follows the forge path, it is not immortal

Conclusion: failure

View job details

##[group]GITHUB_TOKEN Permissions
 Contents: read
 Metadata: read
 SecurityEvents: write
 ##[endgroup]
 Secret source: Actions
 Cache mode: write
 Using locked action versions from the workflow's lockfile
 Prepare workflow directory
 Prepare all required actions
 Getting action download info
 ##[error]Unable to resolve action `actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1`: invalid lockfile pin. Run `gh actions-lock` to update the lockfile. lockfile verification did not produce a result for this action

Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!