[hyperpolymath]

Summary

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.

Changes

• .machine_readable/CLADE.deed: "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.

RSR Quality Checklist

Required

• Tests pass (just test or equivalent): not run locally. Comment-only change, left to CI.
• Code is formatted (just fmt or equivalent): n/a, no code
• Linter is clean (no new warnings or errors): n/a, no code
• 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

Testing

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 project identity behaves when its GitHub path or name changes. Moving a mirror or changing project phase does not create a new identity. Changing a prefixed name while keeping the GitHub path unchanged updates the recorded alias, without changing the identity or phase.

The CLADE lifecycle comment now ties UUID identity to the GitHub path. It also clarifies the stated effects of mirror moves, phase changes and prefixed-name changes on UUIDs and aliases.

Changes: UUID lifecycle wording

Layer / File(s)	Summary
Clarify UUID and alias rules .machine_readable/CLADE.deed	The comment states that mirror moves and phase changes do not mint a UUID. It limits the alias rule to prefixed-name changes where the GitHub path remains unchanged.

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

Change: Other

Possibly related PRs

• hyperpolymath/affinescript#789: Revises the same CLADE lifecycle comment and describes UUID, phase and alias rules.

Suggested reviewers: metadatastician

Merge Risk: Low · up to e6a5a

The lifecycle guidance now points readers to a GitHub path that does not match AffineScript’s UUID. Reconcile the declaration before relying on it for identity, though this comment-only change does not itself alter stored data.

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

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