[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.

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

---

Generated by Claude Code

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary

Summary by CodeRabbit

• Documentation
  • Clarified how an item’s identifier changes when it is moved or renamed, and that changing its lifecycle phase does not affect the identifier.
  • Clarified that renaming does not change the lifecycle phase and that the previous name is retained as an alias.
  • Added a reference to the relevant architecture decision record.

The lifecycle-status comments now state that a UUID follows the forge path and changes on a move or rename. They cite ADR 0007 and retain the statements about phase changes and aliases.

Changes: Lifecycle status comments

Layer / File(s)	Summary
Lifecycle identity rules .machine_readable/CLADE.a2ml	The comments replace the claim that a UUID is immortal with the rule that a move or rename mints a new UUID. They retain the statements that phase changes do not change the UUID, and that a rename leaves phase unchanged and adds the old prefixed name to aliases[].

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

Change: Other

Merge Risk: Low · up to 575a3

Rename guidance remains ambiguous; correct the retained sentence before relying on it.

- [ ] 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

[chatgpt-codex-connector]

Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	❌ Failed 2026-11-10T20:23:56.035506Z We couldn’t complete this review. Comment @codex review to try again.	575a3ca	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.