Skip to content

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

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 that a UUID follows the forge path and is minted anew when an item is moved or renamed, while phase changes leave it unchanged.
    • Clarified that changing a prefixed name does not change the phase; the former name is recorded as an alias, with the UUID and phase unchanged.

The lifecycle-status comments now describe UUID behaviour for moves, renames, and phase changes. They also clarify how prefixed-name changes affect aliases[] and phase.

Changes: Lifecycle identity

Layer / File(s) Summary
Document lifecycle identity rules
.machine_readable/CLADE.a2ml
The comments state that moves or renames mint a new UUID. Phase changes leave the UUID unchanged. A prefixed-name change adds the former name to aliases[] without changing the UUID or phase.

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

Change: Other

Merge Risk: Minimal · up to 1145a

The updated comments clarify when UUIDs change. 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: the UUID follows the GitHub path and changes after a move or rename.
Description check Passed The description includes the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. It explains the change and states that tests were not run locally and are left to CI. …
Full details: Description check

Explanation

The description includes the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. It explains the change and states that tests were not run locally and are left to CI. Some checklist items are marked not applicable or remain unchecked, but the description is mostly 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: 652ff365-269c-464f-a6df-647af2c6f96a
Commits

Reviewing files that changed from the base of the PR and between 6739b86 and 1145ac0.

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: semgrep-cloud-platform/scan
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: panic-attack assail
  • GitHub Check: Hypatia neurosymbolic scan
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!

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

Copy link
Copy Markdown
Owner Author

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, 6739b86. 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

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 bbc5c0e into main Nov 11, 2026
13 of 15 checks passed
@hyperpolymath
hyperpolymath deleted the docs/clade-uuid-follows-forge-path branch November 11, 2026 00:28
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