Skip to content

docs(clade): uuid follows the GitHub path, it is not immortal - #93

Merged
hyperpolymath merged 2 commits into
mainfrom
docs/clade-uuid-follows-forge-path
Nov 11, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
docs/clade-uuid-follows-forge-path

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

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

The CLADE status comment said the uuid is immortal. gv-clade-index
ADR 0007 (accepted 2026-11-10) makes the uuid follow the forge path:
a move or rename mints a new one, and a phase change never does. A
prefixed-name (clade code) change still does not remint.

Comment-only correction. No data values change. A2ML is retired for
new content, but correcting a factually wrong comment in an existing
file is an edit, not new content.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZmTcNdC1jL1Vp3qW9H
@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Clarified lifecycle information: identifiers are newly generated when an item is moved or renamed, and remain unchanged when its phase changes. The documentation also distinguishes changes to an item’s prefixed name from phase changes, making the stated behavior around identifiers and lifecycle updates more precise.

The lifecycle-status comments now state when a UUID changes and distinguish phase changes from clade-code changes.

Changes: Lifecycle status comments

Layer / File(s) Summary
Clarify UUID and phase comments
.machine_readable/CLADE.a2ml
The comments state that UUIDs follow the forge path and that a move or rename mints a new UUID. They also state that phase changes leave the UUID unchanged and that a clade-code change is not a phase change.

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

Change: Other

Merge Risk: Minimal · up to e2884

The clarified guidance does not appear to change behavior. No merge-blocking risk was identified.

Pre-merge checks: Passed 4

Check name Status Explanation
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Title check Passed The title clearly describes the main change: correcting the UUID lifecycle comment to state that the UUID follows the GitHub path and is not immortal.
Description check Passed The description covers the summary, changes, checklist, and testing. It explains that tests were not run locally and were left to CI. The optional Screenshots section is omitted, and several required …
Full details: Description check

Explanation

The description covers the summary, changes, checklist, and testing. It explains that tests were not run locally and were left to CI. The optional Screenshots section is omitted, and several required checklist items are unchecked or marked not applicable, but the description is otherwise complete.

  • 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

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: d6555565-3102-4b53-ae19-d0eabd63ee4c
Commits

Reviewing files that changed from the base of the PR and between 54bb38f and e28840d.

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

  • GitHub Check: CodeRabbit
  • GitHub Check: Validate K9 contracts
  • GitHub Check: semgrep-cloud-platform/scan
Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-34: LGTM!

@linear-code
linear-code Bot marked this pull request as ready for review November 10, 2026 23:13

Copy link
Copy Markdown
Owner Author

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

The uuid is UUIDv5 over github.com/<owner>/<name> (gv-clade-index ADR
0007), so say "GitHub path" rather than "forge path": a move or rename on
GitHub mints a new uuid, a mirror move does not. Scope the "not a phase
change" sentence to a prefixed-name change with the GitHub path unchanged.

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

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZmTcNdC1jL1Vp3qW9H
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath hyperpolymath changed the title docs(clade): uuid follows the forge path, it is not immortal docs(clade): uuid follows the GitHub path, it is not immortal Nov 10, 2026
@hyperpolymath
hyperpolymath merged commit f6383c2 into main Nov 11, 2026
12 of 14 checks passed
@hyperpolymath
hyperpolymath deleted the docs/clade-uuid-follows-forge-path branch November 11, 2026 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants