Skip to content

[umbrella] Estate audit & optimization — make the enforcement real (Waves 0–6) #460

Open

Description

@hyperpolymath

Program tracker for the estate-wide audit-and-uplift anchored in standards. Ordered by estate doctrine (RSR-PHILOSOPHY.adoc): holes before goals, solutions at source, always fail loudly.

The diagnosis (7-agent recon): the estate's declarations were rich but enforcement was largely theatre — validators passed vacuously, mandatory checks were declared-but-never-run, and there was no post-action check on an agent's claims. Each wave converts a layer of theatre into a check that genuinely can fail.

Landed

Remaining charters (hand-off to other sessions / bots)

Cross-links to existing issues

Relates: #381 (registry drift), #399 (CI-red on main), #426 (estate CI-red master cause), #437 (hypatia stale cache), #446 (honest badge framework), #451 (reusable-workflow permissions), #387 (rsr-audit bugs, fixed), #124 (proof-debt epic), #348 (gitbot fan-out).

Licence/SPDX is flag-only throughout every wave — no header edits.

Activity

  1. added
    meta:umbrellaParent issue aggregating child issues
    meta:recurringRecurs on a schedule or by trigger; never finally closed
    on Jul 3, 2026
  2. hyperpolymath commented on Aug 24, 2026

    @hyperpolymath
    OwnerAuthor

    Wave 6 continuation update (2026-08-24):

    Canonical metadata naming:

    Reproducible HYP-S009 inventory:

    Recommended extraction order remains #492 AXEL pilot, then #491. #490 and #494 are destination-blocked from the authenticated horizon (hyperpolymath/a2ml and /lol not visible); do not create/delete destinations without owner direction. #493 must remain licence-neutral.

    Licence boundary: no licence/SPDX content was edited. The 32 tracked #497 paths remain owner-only; this includes 25 (not the stale issue-body count of 24) under toolchain-readiness-grades/references/007/.

  3. 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
  4. hyperpolymath commented on Aug 27, 2026

    @hyperpolymath
    OwnerAuthor

    Re-verified 2026-08-27 — three "remaining charters" are in fact done

    charter state
    Mustfile PR gate ✅ registry-verify.yml runs scripts/run-mustfile.sh on pull_request, with an explicit "Wave-8 gate promotion" comment
    RSR v2.0 machine-half ✅ spec.scm/ has 0 tracked files; .machine_readable/ has 95
    6a2 → descriptiles ✅ 6 residual 6a2 paths vs 180 descriptile paths

    Genuinely still open

    Recommend: tick the three completed charters, and let this umbrella close once #635 and the guides land.

  5. added
    governancePolicy, rulesets, standards, compliance, and their enforcement
    scope:estateAffects many or all repos across the estate
    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

    governancePolicy, rulesets, standards, compliance, and their enforcementmeta:recurringRecurs on a schedule or by trigger; never finally closedmeta:umbrellaParent issue aggregating child issuespriority:p3Low - nice to havescope:estateAffects many or all repos across the estate

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions