Skip to content

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

Merged
hyperpolymath merged 2 commits into
mainfrom
docs/clade-uuid-follows-forge-path
Nov 10, 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
Contributor

Explain Change →

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 35 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

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: 4966c567-da2e-4018-b14f-716e96be1e6c
Commits

Reviewing files that changed from the base of the PR and between 98d930a and 74aac89.

Files selected for processing: 1

  • .machine_readable/CLADE.a2ml

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Clarified how moves, renames, prefixed-name changes and phase changes affect UUIDs, aliases and lifecycle status.

The lifecycle-status comments now describe how moves, renames, prefixed-name changes, and phase changes affect UUIDs, aliases, and phase values. The status values are unchanged.

Changes: Lifecycle status comments

Layer / File(s) Summary
Document UUID and alias rules
.machine_readable/CLADE.a2ml
Comments state that moves or renames mint a UUID based on the forge path. Prefixed-name changes record the old name in aliases[] without changing the UUID or phase. Phase changes preserve the UUID.

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

Change: Other

Merge Risk: Minimal · previous review 98d93

No merge-blocking risk is established; the lifecycle wording has not been directly checked against ADR 0007.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title clearly summarises the main change: the UUID follows the forge path rather than remaining unchanged after a move or rename.
Description check Passed The description explains the correction and its rationale, lists the file-level changes, completes the required checklist, and describes testing. The applicable checklist and screenshots sections are …
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.
Full details: Description check

Explanation

The description explains the correction and its rationale, lists the file-level changes, completes the required checklist, and describes testing. The applicable checklist and screenshots sections are omitted, but these omissions do not make the description incomplete 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

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: 75628659-e76e-4f93-a9f7-ee56127f051d
Commits

Reviewing files that changed from the base of the PR and between 8a66634 and 98d930a.

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

  • GitHub Check: CodeRabbit
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: analyze (actions, none)
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Groove manifest check
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Zig FFI builds + tests (Zig 0.14.0)
  • GitHub Check: Validate DEED manifests
  • GitHub Check: panic-attack assail
  • GitHub Check: ABI ↔ FFI structural conformance
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:21
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 merged commit d3a9a9e into main Nov 10, 2026
15 checks passed
@hyperpolymath
hyperpolymath deleted the docs/clade-uuid-follows-forge-path branch November 10, 2026 23:45
@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
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