Skip to content

[carve-out 6/9] Data out of spec dirs: grade data → archive, PORT-REGISTRY → verisim-data, retire SATELLITES.a2ml #495

Open

Description

@hyperpolymath

Child of #479. Rubrics are specs; grades of specific repos are data — mixing them guarantees spec dirs accrete stale point-in-time reports.

  • adoption-readiness-grades/AUDIT-FINDINGS-2026-05-28.adoc (521-line session report), publication-pre-flight/ESTATE-AUDIT-BASELINE-2026-03-30.adoc, per-dir SELF-ASSESSMENT.adoc snapshots → docs/archive/ (gitbot-fleet convention) or a new estate-audits repo. Framework-gap items inside them → tracked issues against ARG/FRG v1.1 first.
  • PORT-REGISTRY.md assignments → verisim-data, derived from repo configs by a hypatia rule; keep only the uniqueness rule in standards as policy. (Also .md where doc policy says .adoc.)
  • SATELLITES.a2ml → retire: it duplicates the generated registry's role without hash verification, still points at absorbed repos as live satellites, and asserts palimpsest "applied-to = all-repos" contradicting the licence directive (flag-only — retire the file via normal PR, no licence-content edits). Fold its execution-pipeline section into the A2ML family docs first.
  • toolchain-readiness-grades/references/007/ is NOT here — it is licence-flagged, child 8/9, owner-only.

⚠️ CORRECTION 2026-08-25 — the destination name is wrong, and the repo it names is live, not experimental residue

1. verisim-data does not exist. verisimdb-data does — and it is load-bearing.

Measured 2026-08-25:

  • last push 2026-08-25T06:37Z, commit message scan: estate rescan (run 32810961229) (#92) — i.e. it is receiving automated estate scan commits, today
  • referenced by 20+ hypatia modules, including the entire merge brain: merge-orchestrate.yml, estate-rescan.yml, lib/verisim_connector.ex, lib/fleet_dispatcher.ex, lib/dispatch_manifest.ex, lib/pattern_registry.ex, lib/outcome_tracker.ex, lib/recipe_matcher.ex, lib/cross_repo_learning.ex
  • it is one of the four repos in the base ruleset set

This is the estate's canonical scan store. It is not experimental leftover and must not be retired. The question this issue can legitimately ask is only whether PORT-REGISTRY belongs in it — not whether it should exist.

2. estate-audits should not be a repo at all.

Owner ruling 2026-08-25: an audit sitting inside one of the repo directories is in the wrong place. Audits belong in the appropriate directory in developer/ above the repo trees — i.e. developer/dev-notes/ — not in a new repository. hyperpolymath/estate-audits (404) should not be created.

3. Already done: SATELLITES.a2ml is a deprecation stub; PORT-REGISTRY.md no longer exists on origin/main.

Action for this issue, revised: move grade data to developer/dev-notes/ rather than a new estate-audits repo; decide PORT-REGISTRY's placement within the existing, live verisimdb-data; drop the verisim-data name entirely.

Activity

  1. hyperpolymath commented on Jul 28, 2026

    @hyperpolymath
    OwnerAuthor

    ✅ PARTIALLY COMPLETED by commit e061af1

    REMAINING:

    • Full migration of port assignments to verisim-data (requires access to that repo)
    • Complete grade data migration (requires estate-audits repo)
  2. added
    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup
    on Aug 24, 2026
  3. hyperpolymath commented on Aug 27, 2026

    @hyperpolymath
    OwnerAuthor

    Re-verified 2026-08-27 — two bullets done, and the 2026-08-25 correction is itself now stale

    Done:

    ⚠️ The correction in this thread needs correcting

    It states that PORT-REGISTRY.md no longer exists. True as written — but it was renamed to PORT-REGISTRY.adoc by the .md→.adoc migration and is still at the standards root. It was not removed.

    Still present, not mentioned in the correction

    • 5 × SELF-ASSESSMENT.adoc snapshots in spec directories
    • toolchain-readiness-grades/references/007/ — 25 files (the owner-only child, 8/9)

    Recommend: reopen the PORT-REGISTRY bullet against the .adoc path, and treat the two items above as the remaining scope.

  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