[hyperpolymath]

Summary

Comment-only correction. The CLADE status comment said the uuid is immortal. 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.a2ml: "uuid is immortal" → "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 rename 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 replaces the earlier "forge path" text, and follow-up PRs bring the repos that merged that text in line.

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 with Claude Code

https://claude.ai/code/session_0136P7ZmTcNdC1jL1Vp3qW9H

[coderabbitai]

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

• Documentation
  • Clarified that moving or renaming an entity along its forge path results in a new UUID.
  • Explained that changing a prefixed name leaves the UUID and phase unchanged, and moves the previous name to the aliases list.
  • Distinguished prefixed-name changes from phase changes.

The lifecycle-status comments now describe UUID behaviour during moves or renames. They also clarify that a prefixed-name change updates aliases[] without changing the UUID or phase.

Changes: Lifecycle status comments

Layer / File(s)	Summary
Clarify lifecycle status comments .machine_readable/CLADE.a2ml	The comments replace the claim that a UUID is immortal with a description of UUID behaviour during moves or renames. They also distinguish prefixed-name changes from phase changes and describe the effect on aliases[], the UUID and the phase.

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

Change: Other

Merge Risk: Minimal · up to 80d56

The comment-only clarification presents no identified merge-blocking risk.

Pre-merge checks: 4

Check name	Status	Explanation
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.
Title check		The title clearly summarises the main change: UUID identity follows the GitHub path and is not permanent.
Description check		The description covers the summary, changes, checklist and testing. It explains why tests were not run locally. The omitted Screenshots section is not critical for this comment-only change.

• 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: d200890f-dfef-48a2-9285-cd8c112526dc

Commits

Reviewing files that changed from the base of the PR and between da7e929 and 80d56f4.

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

• GitHub Check: CodeRabbit
• GitHub Check: analyze (actions, none)
• GitHub Check: Validate eclexiaiser manifest
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: Validate K9 contracts
• GitHub Check: Hypatia neurosymbolic scan
• GitHub Check: semgrep-cloud-platform/scan

Additional context used

Code guidelines: 1

.github/copilot-instructions.md — auto-discovered

Path-based instructions: 2

Source excerpt: State files (.a2ml) live in `.machine_readable/` ONLY, never the root.

CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

• .machine_readable/CLADE.a2ml

Source excerpt: Annotate and document all files.

CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

• .machine_readable/CLADE.a2ml

Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!

[hyperpolymath]

Two checks fail on files this PR does not touch. The PR changes only a comment in .machine_readable/CLADE.a2ml.

• Validate DEED manifests: docs/governance/MAINTENANCE-CHECKLIST.a2ml is missing an identity field.
• Validate K9 contracts: container/deploy.k9.ncl is an unfilled template and has no K9! magic line or pedigree name.

Both are in the scaffold on main, so any PR on this base hits them. No fix exists yet, and each belongs in a separate PR.

---

Generated by Claude Code

[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