Skip to content

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

Merged
hyperpolymath merged 1 commit into
mainfrom
docs/clade-uuid-github-path
Nov 11, 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 that a GitHub path move or rename results in a new UUID, while moving a mirror or changing phase does not.
    • Clarified that changing the prefixed name without changing the GitHub path leaves the UUID and phase unchanged, and records the previous name as an alias.

The lifecycle comment now defines GitHub path as the source of UUID identity. It distinguishes GitHub moves from mirror moves and clarifies how prefixed-name changes affect aliases, UUID, and phase.

Changes: Lifecycle guidance

Layer / File(s) Summary
UUID and name-change rules
.machine_readable/CLADE.a2ml
The comment states that GitHub moves or renames mint a new UUID, while mirror moves and phase changes do not. If the GitHub path is unchanged, a prefixed-name change adds the former name to aliases[] without changing UUID or phase.

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

Change: Other

Possibly related PRs

  • hyperpolymath/Axiom.jl#126: Changes the same lifecycle comment and describes UUID behaviour on forge moves, renames, and phase changes.
  • hyperpolymath/Axiom.jl#127: Clarifies that a prefixed-name change is not a phase change and puts the old name in aliases[].
Merge Risk: Minimal · up to 4aaf1

No merge-blocking risk is established for the documentation change.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title clearly describes the GitHub-path UUID change and the prefixed-name qualification.
Description check Passed The description explains the comment changes to UUID identity and prefixed-name handling.
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: 82552f6f-3ea0-46dc-8dbc-06ecd518f5d2
Commits

Reviewing files that changed from the base of the PR and between 3b7f9ab and 4aaf1af.

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

  • GitHub Check: CodeRabbit
  • GitHub Check: Roadmap could-baselines (packaging + optimization + telemetry)
  • GitHub Check: Julia 1.11 - windows-latest
  • GitHub Check: Documentation sanity
  • GitHub Check: Proof assistant bundle checks
  • GitHub Check: Runtime smoke (CPU)
  • GitHub Check: Idris2 ABI typecheck
  • GitHub Check: Julia 1.11 - ubuntu-latest
  • GitHub Check: GPU fallback tests - macos-latest
  • GitHub Check: Julia 1.10 - ubuntu-latest
  • GitHub Check: CPU vs Zig parity + accelerated smoke
  • GitHub Check: Julia 1.10 - windows-latest
  • GitHub Check: Zig Backend
  • GitHub Check: Julia 1.10 - macos-latest
  • GitHub Check: Certificate integrity checks
  • GitHub Check: SMT proofs (Z3)
  • GitHub Check: Julia 1.11 - macos-latest
  • GitHub Check: Coprocessor strategy, resilience, and TPU/NPU/DSP/MATH strict tests
  • GitHub Check: Interop smoke (PyTorch import + ONNX export)
  • GitHub Check: GPU fallback tests - ubuntu-latest
  • GitHub Check: Julia nightly - ubuntu
  • GitHub Check: Julia nightly (crypto-enabled) - ubuntu-latest
  • GitHub Check: Julia 1.10 (crypto-enabled) - ubuntu-latest
  • GitHub Check: Detect relevant changes
  • GitHub Check: estate-rules
  • GitHub Check: Julia 1 (crypto-enabled) - ubuntu-latest
  • GitHub Check: Build docs (Documenter, with doctests)
  • GitHub Check: Groove manifest check
  • GitHub Check: Validate DEED manifests
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Creusot contracts (crypto/)
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Analyze (actions)
  • GitHub Check: semgrep-cloud-platform/scan
Additional comments: 1

.machine_readable/CLADE.a2ml: 1

32-38: LGTM!

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

Copy link
Copy Markdown
Owner Author

CI note: Julia 1 (crypto-enabled) - ubuntu-latest is failing on this PR. It also fails on the latest main commit (3b7f9ab), so this PR did not cause it. This PR only changes a comment in .machine_readable/CLADE.a2ml. I don't have a fix to port in, and I can't re-run the check from here.


Generated by Claude Code

Copy link
Copy Markdown
Owner Author

Follow-up: Julia nightly (crypto-enabled) - ubuntu-latest has also failed on this PR. It fails on main (3b7f9ab) as well, so this PR did not cause it either.


Generated by Claude Code

@hyperpolymath
hyperpolymath merged commit 479e6d7 into main Nov 11, 2026
41 of 44 checks passed
@hyperpolymath
hyperpolymath deleted the docs/clade-uuid-github-path branch November 11, 2026 00:12
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