[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 identity and naming behaviour: moving or renaming an item’s forge path results in a new UUID. Changing only its prefixed name preserves its UUID and phase, while the previous name is retained as an alias. The lifecycle guidance now distinguishes path changes from prefixed-name changes.

The lifecycle comment now states that UUID identity follows the forge path. It distinguishes moves or renames from prefixed-name changes, which preserve the UUID and phase and add the old prefixed name to aliases[].

Changes: Lifecycle identity

Layer / File(s)	Summary
Clarify lifecycle identity .machine_readable/CLADE.a2ml	The lifecycle comment states that a move or rename mints a new UUID. It also states that a prefixed-name change leaves the UUID and phase unchanged and adds the old prefixed name to aliases[].

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

Change: Other

Merge Risk: Minimal · up to a4711

The clarification matches the current identity policy and is ready to merge after normal checks.

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: the UUID follows the GitHub path and is not immortal.
Description check		The description includes the summary, key changes, required checklist, and testing details. It states that tests were not run locally and were left to CI. The omitted screenshots section is not applic…

Full details: Description check

Explanation

The description includes the summary, key changes, required checklist, and testing details. It states that tests were not run locally and were left to CI. The omitted screenshots section is not applicable to 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: 50d13d73-0b73-43ca-8a1e-f7120b4c41a8

Commits

Reviewing files that changed from the base of the PR and between 64ea085 and a4711bd.

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

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

Additional context used

Code guidelines: 1

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

Path-based instructions: 1

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

Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!

[hyperpolymath]

CI note: these failures are not caused by this PR. This PR changes only the comment block in .machine_readable/CLADE.a2ml.

Two Dogfood Gate jobs are red:

• Validate K9 contracts. ./container/deploy.k9.ncl is an unfilled template: the K9! magic line is missing, and so is the pedigree name.
• Validate DEED manifests. ./docs/governance/MAINTENANCE-CHECKLIST.a2ml is missing an identity field (agent-id, name or project).

Neither file is part of this diff. The Dogfood Gate workflow also fails on main at the PR's base, 64ea085. No fix exists on main yet. Fixing these files means filling in real project metadata, so they need a separate change.

---

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