Skip to content

fix(identity): give wokelangiser its own deterministic uuid - #27

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/wizardly-archimedes-9pnqed-uuid
Jun 20, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
claude/wizardly-archimedes-9pnqed-uuid

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Why

Follow-up to #26. That PR corrected wokelangiser's canonical-name + forge URLs but deliberately left uuid as a flagged placeholder. The scaffold uuid a5ea1382-a34c-5334-8a46-a2ebe904c810 is byte-identical to iseriser's CLADE.a2ml uuid (iseriser is also an unedited RSR scaffold) — a cross-repo identity collision. uuids in this estate are meant to be unique per repo.

Change

.machine_readable/CLADE.a2ml — uuid → 1c233dc2-7b7e-5856-9606-22f119ed68ad.

This is the registry's deterministic UUIDv5, exactly per gv-clade-index's documented scheme (sync/deploy-clade-a2ml.sh, sync/export-json.sh, README):

uuidgen --sha1 --namespace @url --name "github.com/hyperpolymath/wokelangiser"

Verified, not guessed: there is no uuidgen in the build env, so I implemented UUIDv5 with sha1sum (URL namespace 6ba7b811-9dad-11d1-80b4-00c04fd430c8) and reproduced wokelang's known uuid e460af5f-1cfb-58bf-9c5a-70bf458ea2af exactly before applying the identical method to wokelangiser.

Clade — intentionally NOT changed (flagged)

[clade] primary = "rm" / prefixed-name = "rm-wokelangiser" remain the RSR scaffold defaults. I did not touch them: wokelangiser is not registered in gv-clade-index (worker/data/repos.json has no wokelangiser entry and no -iser family at all), and the clade definitions are VeriSimDB-backed, so the correct -iser clade isn't derivable from the registry. Assigning it is a registry decision. If you have the authoritative -iser clade, tell me and I'll set [clade] primary + prefixed-name here before merge.

Out of scope

  • iseriser's identical placeholder uuid — iseriser is not in this session's write scope (only wokelang + wokelangiser are). Noted as an upstream follow-up.

Verification (actually run)

  • UUIDv5 method reproduced wokelang's known uuid (e460af5f-…) → confirms the derivation is correct; wokelangiser then computes deterministically to 1c233dc2-….
  • Working-tree diff is exactly one line (the uuid value): 1 file changed, 1 insertion(+), 1 deletion(-); SPDX header and every other key untouched.

Metadata only — no proofs or code logic changed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Y2MWTAqX2x7goVJzjFB4j5


Generated by Claude Code

…iser's scaffold placeholder)

The uuid was the unedited RSR-scaffold value, byte-identical to iseriser's CLADE.a2ml uuid — a cross-repo identity collision (uuids are meant to be unique per repo). Replaced with the registry's deterministic UUIDv5 derived from "github.com/hyperpolymath/wokelangiser" (URL namespace), per gv-clade-index's documented scheme (sync/deploy-clade-a2ml.sh); verified by reproducing wokelang's known uuid with the same sha1sum method.

Clade (rm) and prefixed-name left unchanged: wokelangiser is not yet registered in gv-clade-index and the -iser family has no clade assigned there, so the correct value isn't derivable from the registry — flagged rather than guessed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y2MWTAqX2x7goVJzjFB4j5
@hyperpolymath
hyperpolymath marked this pull request as ready for review June 20, 2026 02:27
@github-actions

Copy link
Copy Markdown

🔍 Hypatia Security Scan

Findings: 54 issues detected

Severity Count
🔴 Critical 1
🟠 High 10
🟡 Medium 43

⚠️ Action Required: Critical security issues found!

View findings
[
  {
    "reason": "Issue in boj-build.yml",
    "type": "missing_timeout_minutes",
    "file": "boj-build.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in casket-pages.yml",
    "type": "missing_timeout_minutes",
    "file": "casket-pages.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in casket-pages.yml",
    "type": "missing_timeout_minutes",
    "file": "casket-pages.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in codeql.yml",
    "type": "missing_timeout_minutes",
    "file": "codeql.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in dogfood-gate.yml",
    "type": "missing_timeout_minutes",
    "file": "dogfood-gate.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in dogfood-gate.yml",
    "type": "missing_timeout_minutes",
    "file": "dogfood-gate.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in dogfood-gate.yml",
    "type": "missing_timeout_minutes",
    "file": "dogfood-gate.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in dogfood-gate.yml",
    "type": "missing_timeout_minutes",
    "file": "dogfood-gate.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in dogfood-gate.yml",
    "type": "missing_timeout_minutes",
    "file": "dogfood-gate.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  },
  {
    "reason": "Issue in instant-sync.yml",
    "type": "missing_timeout_minutes",
    "file": "instant-sync.yml",
    "action": "flag",
    "rule_module": "workflow_audit",
    "severity": "medium"
  }
]

Powered by Hypatia Neurosymbolic CI/CD Intelligence

@hyperpolymath
hyperpolymath merged commit 13ceef1 into main Jun 20, 2026
20 checks passed
@github-actions
github-actions Bot deleted the claude/wizardly-archimedes-9pnqed-uuid branch June 21, 2026 02:15
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.

2 participants