[hyperpolymath]

What changed

Comment-only follow-up. An earlier PR replaced "uuid is immortal" in the CLADE status comment with "uuid follows the forge path". This one makes it exact. gv-clade-index ADR 0007 (accepted 2026-11-10) derives the uuid from the GitHub path (UUIDv5 over github.com/<owner>/<name>): a move or rename on GitHub mints a new one, and a mirror move or a phase change never does.

A2ML is retired for new content. Correcting a factually wrong comment in an existing file is an edit, not new content.

• .machine_readable/CLADE.a2ml: "uuid follows the forge path" → "uuid follows the GitHub path (a move or rename there mints a new one, gv-clade-index ADR 0007; a mirror move or a phase change never does)"; "A prefixed-name (clade code) change is NOT a phase change" → "A prefixed-name (clade code) change with the GitHub path unchanged is NOT a phase change". The paragraph is re-wrapped at 80 columns. No data values change. The owner approved this wording for the whole estate. It refines the wording merged earlier.

Type of change

• Documentation (docs:)

Local verification

• Tests: not run locally. Comment-only change, left to CI.
• Formatting: n/a, no code
• Linter: n/a, no code

Checklist

• No banned language patterns
• No unsafe blocks without // SAFETY: comments
• No banned functions
• SPDX license headers present on all new/modified source files (not touched)
• No secrets, credentials, or .env files included

Notes for the reviewer

The diff is one comment paragraph in one file. Every line is ≤80 characters. The commit is signed.

---

Generated by Claude Code

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary

Summary by CodeRabbit

• Documentation
  • Clarified how GitHub path changes, mirror moves, phase changes and prefixed-name updates affect UUIDs, aliases and lifecycle status.

The lifecycle-status comments now state that UUID identity follows the GitHub path. They distinguish GitHub moves or renames from mirror moves, and clarify how prefixed-name changes affect aliases, UUIDs, and phases.

Changes: Lifecycle status comments

Layer / File(s)	Summary
UUID identity rules .machine_readable/CLADE.a2ml	The comments state that GitHub moves or renames mint a new UUID, while mirror moves do not. They clarify that a prefixed-name change with an unchanged GitHub path updates aliases[] without changing the UUID or phase.

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

Change: Other

Possibly related PRs

• hyperpolymath/blocky-writer#79: Changes the same lifecycle-status comment; this PR revises its UUID rule and clarifies prefixed-name changes.

Merge Risk: Minimal · up to ba8f6

The change clarifies UUID lifecycle documentation and presents no identified merge-blocking risk.

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[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-10T23:51:15.062992Z We couldn’t complete this review. Comment @codex review to try again.	ba8f616	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.