Skip to content

docs(clade): uuid follows the GitHub path; qualify the prefixed-name case - #102

Merged
hyperpolymath merged 1 commit into
mainfrom
docs/clade-uuid-github-path
Nov 10, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
docs/clade-uuid-github-path

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

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.a2ml: "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

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
@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Clarified how GitHub moves, renames, mirror changes and prefixed-name changes affect UUIDs, aliases and lifecycle phases.

The lifecycle comment now ties UUID identity to the GitHub path. It distinguishes GitHub moves or renames from mirror moves and phase changes, and clarifies how prefixed-name changes affect aliases[].

Changes: UUID lifecycle

Layer / File(s) Summary
Clarify UUID lifecycle rules
.machine_readable/CLADE.a2ml
The comment states that a GitHub move or rename mints a new UUID, while a mirror move or phase change does not. When the GitHub path stays unchanged, a prefixed-name change moves the old name to aliases[] without changing the UUID or phase.

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

Change: Other

Possibly related PRs

  • hyperpolymath/aerie#101: Revises the same UUID lifecycle comment and describes UUID identity in terms of the forge path.
Merge Risk: Minimal · up to 162b6

The change clarifies UUID lifecycle wording without changing data. No merge-blocking risk is established.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title clearly identifies the UUID’s relationship to the GitHub path and the prefixed-name clarification.
Description check Passed The description includes a summary, key changes, the required checklist, and testing details. The applicable checklist and screenshots sections are omitted, but the description is otherwise complete.
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.
  • 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: 63046b29-bac1-4321-ba5e-a5d46af5a29b
Commits

Reviewing files that changed from the base of the PR and between d4232bb and 162b666.

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

  • GitHub Check: CodeRabbit
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: check
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Groove manifest check
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: SonarQube
  • GitHub Check: analyze (javascript-typescript, none)
  • GitHub Check: Validate DEED manifests
Additional comments: 1

.machine_readable/CLADE.a2ml: 1

29-35: LGTM!

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

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath merged commit ba3d3bb into main Nov 10, 2026
11 of 12 checks passed
@hyperpolymath
hyperpolymath deleted the docs/clade-uuid-github-path branch November 10, 2026 23:58
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