Skip to content

[campaign] standards carve-out: evict products/impls, keep the canon (spec + policy + registry + template) #479

Open
6 of 9 issues completed

Description

@hyperpolymath

Umbrella tracker for restoring standards to a canon repo — normative specs, policies, generated registries, and templates-as-spec — by evicting the products, implementations, and vendored copies that the 2026-02-08 monorepo absorption pulled in. Derived from a fresh architecture audit (2026-07). The mechanism already exists: the registry's kind = "external" pointer + HYP-S006 drift check, so each eviction flips a LOCAL entry to a hash-verified EXTERNAL pointer — nothing downstream breaks.

Guardrails: licence-adjacent items are flag-only / owner-decision per the Manual-Only licence policy — never swept here. No deletion by access-recency: "delete" below means move-to-docs/archive/ unless noted.

Charter — what STAYS when done

Normative spec text (RFC-2119) + grammars/schemas + conformance vectors · profiles & templates-as-spec · the generated REGISTRY.a2ml/TOPOLOGY.md · policies (licence, CODEOWNERS, remote-url, tooling-integrity, template-applicability) · the readiness-grade rubrics (CRG/TRG/ARG/FRG) · the HYP-S rule definitions.

Evict — product/implementation → home (each via a hash-pinned EXTERNAL registry pointer)

  • a2ml/ (2,018 files: compiler, LSP, 5 bindings, website w/ CNAME+ads.txt) → hyperpolymath/a2ml. Keep the record/markup spec + profiles/ + templates in standards. (Its nested CI has been dead since absorption — GitHub only runs root workflows.)
  • k9-svc/ (1,915 files: bindings, editors, LSP, pandoc, site, benchmarks) → hyperpolymath/k9-ecosystem (its own site copy already says this is the architecture). Keep SPEC.adoc + invariants + conformance vectors.
  • k9-svc/actions/validate/ → hyperpolymath/k9-validate-action (exists) — duplicate of an executable CI action.
  • avow-protocol/, axel-protocol/, consent-aware-http/ implementations (websites, DNS zones, compiled .res.js) → their existing same-name repos. Keep only PROTOCOL/THREAT-MODEL/charter spec text (or an external pointer).
  • 0-ai-gatekeeper-protocol/mcp-repo-guardian/ → hyperpolymath/mcp-repo-guardian (exists); repo-guardian-fs/ → its own repo.
  • rhodium-standard-repositories/satellites/ (964 vendored files, 11 repos) → their canonical repos (named in the stale .gitmodules); then delete the lying .gitmodules.
  • rhodium-standard-repositories/{templates,contractiles,examples}/ → hyperpolymath/rsr-template-repo (doctrine names it THE operationalisation; two template sources = guaranteed drift).
  • rhodium-pipeline/, ux-test-harness/, batch-rollout scripts → own repo / gitbot-fleet (estate-ops tooling, not spec).
  • lol/ (corpus crawler) → its own repo.

Data out of spec dirs → registry/data store

  • Grade data (AUDIT-FINDINGS-2026-05-28, ESTATE-AUDIT-BASELINE, per-dir session reports) → docs/archive/ or a new estate-audits repo; live grades → verisim-data. (Rubrics stay; grades-of-specific-repos are data.)
  • PORT-REGISTRY.md assignments → verisim-data (derive from repo configs); keep only the uniqueness rule as policy.
  • SATELLITES.a2ml → retire; it duplicates the generated registry without hash verification.

Delete / archive (scaffold junk & point-in-time reports at the canon root)

  • stapeln.toml, contractile.just (stale generated output), audit-contractiles.sh, SECURITY_TRAINING_SUMMARY.md, the confusingly-nested standards/ subdir, session detritus (*-COMPLETE*.md, *SESSION_SUMMARY*, DEPLOYMENT-SUCCESS.md), RSR's stale root CLAUDE.md.

⚠️ Licence-flag items — OWNER decision, flag-only (do NOT sweep)

  • toolchain-readiness-grades/references/007/ — 24 verbatim audits of the All-Rights-Reserved 007 repo sitting in a public canon repo → back to hyperpolymath/007. Licence exposure — surface to owner.
  • PALIMPSEST.adoc full narrative → palimpsest-license repo, leave a one-paragraph pointer (only the three carve-out repos should "talk about" Palimpsest).

After-eviction hygiene (prevents recurrence)

  • Add the review-tier "implementation-inside-canon" detector (fires when a registry LOCAL home contains Cargo.toml/deno.json/Containerfile/CNAME).
  • Session-detritus auto-archiver fix-script.

Ordering: evict via external pointer + regenerate REGISTRY.a2ml in the same PR each time (so registry-verify proves nothing dangles). Sequence the biggest wins first (a2ml/, k9-svc/, satellites/). Child issues can be split per bullet.

Filed from the architecture audit; happy to split into per-eviction child issues on request.

Activity

  1. added
    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup
    on Aug 24, 2026
  2. hyperpolymath commented on Aug 25, 2026

    @hyperpolymath
    OwnerAuthor

    2026-08-25 — full triage of all 65 open issues; four new umbrellas filed

    A complete pass over this repo's open issues was done on 2026-08-25. Results: 3 closed (#407, #303, #313), 4 issue bodies corrected for false premises, 1 canon conflict ruled, and the outstanding work regrouped under four new umbrellas:

    Work already shipped from that pass:

    PR What
    hyperpolymath/.git-private-farm#127 wires observe.sh — the merge sense organ, written 2026-07-13 and called by no workflow since
    hyperpolymath/hypatia#721 points the merge brain at a populated store
    hyperpolymath/hypatia#720 fixes a dispatch to dot-git-private-farm, a repo that does not exist
    hyperpolymath/gitbot-fleet#490 same defect, other end of the hop
    #632 rules the TypeScript/AffineScript canon conflict — AffineScript governs
  3. hyperpolymath commented on Aug 27, 2026

    @hyperpolymath
    OwnerAuthor

    Re-measured 2026-08-27 — nothing evicted yet, and 6 of 9 destinations do not exist

    Current sizes in standards@origin/main:

    directory files
    a2ml/ 2,024
    k9-svc/ 1,898 → 41 ✅ (evicted today, #650)
    rhodium-standard-repositories/ 1,138
    lol/ 339
    0-ai-gatekeeper-protocol/ 170
    axel-protocol/ 110

    ⚠️ The correction that should drive sequencing

    This issue asserts two destination repos "(exists)" and both 404.

    destination state
    hyperpolymath/k9-validate-action ❌ 404 — asserted as existing
    hyperpolymath/mcp-repo-guardian ❌ 404 — asserted as existing
    hyperpolymath/a2ml ❌ 404
    hyperpolymath/repo-guardian-fs ❌ 404
    hyperpolymath/lol ❌ 404
    hyperpolymath/consent-aware-http ❌ 404
    hyperpolymath/estate-audits ❌ 404
    k9-ecosystem, rsr-template-repo, avow-protocol, axel-protocol, verisimdb-data ✅ exist

    So 6 of the 9 evictions have nowhere to go. Minting the destinations is the first blocking step — not a2ml/'s size. That is owner-gated (agents cannot create repos), so it should be lifted to the top of the sequence.

    All three .gitmodules this issue calls "lying" are still present. Children: #490/#492/#493/#495/#497 open; #491 CLOSED today; #496 closed.

  4. added
    scope:estateAffects many or all repos across the estate
    status:readyFully specified and ready to be picked up
    on Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:p2Normal - queue itscope:estateAffects many or all repos across the estatestatus:readyFully specified and ready to be picked uptech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions