Skip to content

fix(identity): correct wokelangiser identity + WokeLang relationship#26

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

fix(identity): correct wokelangiser identity + WokeLang relationship#26
hyperpolymath merged 1 commit into
mainfrom
claude/wizardly-archimedes-9pnqed

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Why

Part of the same effort to stop work being misrouted into the nextgen-languages coordination repo and to encode the wokelang ↔ wokelangiser relationship correctly.

Per iseriser (the -iser meta-framework): an -iser is an adapter that bridges a specialist language into the code you already write. So wokelangiser emits WokeLang — it injects WokeLang's consent/accessibility patterns into other code. You never "wokelangise WokeLang" (it already has those patterns natively). wokelangiser's Cargo.toml has no wokelang dependency; the relationship is one-way (wokelangiser → WokeLang).

Changes

  1. docs/architecture/TOPOLOGY.md — the Integration Points row described WokeLang as "Source language in nextgen-languages monorepo", which was wrong twice: (a) WokeLang is standalone, not in a nextgen-languages monorepo; (b) it cast WokeLang as a wokelangise target. Recharacterised as the specialist language wokelangiser bridges other code to (standalone repo hyperpolymath/wokelang).
  2. .machine_readable/CLADE.a2ml — the file was still the unedited RSR scaffold, declaring the repo's canonical identity as rsr-template-repo. canonical-name + the three forge URLs now point at hyperpolymath/wokelangiser.

Assumption flagged: I kept the scaffold's clade prefix (rmprefixed-name = "rm-wokelangiser") and left [clade] primary, secondary, and uuid untouched, because the correct -iser clade isn't derivable from the codebase. If wokelangiser should have a different clade, say so and I'll update it.

Intentionally retained: legitimate references to the RSR template (CHANGELOG "scaffolded from", the ADR, quickstart clone command, citation) — those are accurate history/external references, not identity claims.

Verification (actually run)

  • Repo-wide rg after the edits: zero nextgen-languages monorepo claims; the only rsr-template-repo hits remaining are the intentional historical/external references above.
  • CLADE.a2ml edit is a pure value swap on identity fields (see diff); uuid, clade, and lineage keys unchanged.

Metadata/docs only — no proofs or code logic changed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Y2MWTAqX2x7goVJzjFB4j5


Generated by Claude Code

Two fixes that stop work being misrouted:

1. docs/architecture/TOPOLOGY.md: the Integration Points row cast WokeLang as a
   "source language in nextgen-languages monorepo" - wrong twice. WokeLang is a
   standalone repo, and wokelangiser EMITS WokeLang (it bridges OTHER code to
   WokeLang's consent/accessibility patterns); you don't "wokelangise" WokeLang.
   Row recharacterised accordingly.

2. .machine_readable/CLADE.a2ml: file was still the unedited RSR scaffold,
   declaring the repo's canonical identity as "rsr-template-repo". canonical-name
   and forge URLs set to wokelangiser (clade prefix kept as rm-; uuid untouched).

Legitimate historical/external references to the RSR template (CHANGELOG, ADR,
quickstart, citation) are intentionally retained.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y2MWTAqX2x7goVJzjFB4j5
@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 marked this pull request as ready for review June 19, 2026 22:28
@hyperpolymath
hyperpolymath merged commit 5e6da83 into main Jun 19, 2026
20 checks passed
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