Skip to content

🎯 ONE SHOT β€” L-T27-PROOFSYNC β€” eliminate 32 stale Admitted in t27 forkΒ #559

@gHashTag

Description

@gHashTag

🎯 ONE SHOT β€” L-T27-PROOFSYNC β€” eliminate 32 stale Admitted in t27 fork

Anchor: φ² + φ⁻² = 3 Β· DOI 10.5281/zenodo.19227877
Audit: coq_audit_2026-05-08 Β§3 (Drift between t27 and trios).
Repos: gHashTag/t27 (fork), gHashTag/trios (canonical).

Problem

gHashTag/t27/proofs/trinity/*.v (5 files, 32 Admitted) are a stale 1-way mirror of gHashTag/trios/docs/phd/theorems/trinity/*.v. Specifically:

File t27 Admitted trios Admitted Drift
ExactIdentities.v 11 3 🚨 8 unmerged sweep-1 fixes (PR #550)
Bounds_LeptonMasses.v 8 8 identical
ConsistencyChecks.v 7 7 identical
Bounds_QuarkMasses.v 4 4 identical
Unitarity.v 2 2 identical

This causes false positives in cross-repo audits: the empire shows 60 Admitted total instead of canonical 28.

Two strategies (lane chooses one)

Strategy A β€” DELETE & SUBMODULE

Replace t27/proofs/trinity/ with a git submodule pointer to gHashTag/trios (or a sparse-checkout git subtree of docs/phd/theorems/trinity/). Single source of truth.

Pros: zero ongoing sync work; t27 always sees the latest trios proofs.
Cons: changes t27 build; need to update t27 CI to fetch submodule.

Strategy B β€” AUTOMATED SYNC WORKFLOW

Add .github/workflows/proof-sync.yml to t27 that runs daily and opens PRs to mirror trios/docs/phd/theorems/trinity/*.v β†’ t27/proofs/trinity/*.v whenever they drift.

Pros: keeps t27 self-contained; no submodule complexity.
Cons: ongoing CI cost; race-condition window.

Lanes (4 lanes β€” claim by commenting claim L-T27-PROOFSYNC-Lx)

Lane Action
L-T27-SYNC-L1/main (decide) Open RFC issue in gHashTag/t27, propose A vs B, wait for queen ruling
L-T27-SYNC-L2/main (cherry-pick) Cherry-pick trios PR #550 (sweep-1) into t27 immediately to remove 8 stale Admitted, regardless of long-term strategy
L-T27-SYNC-L3/main (implement) Execute the chosen strategy A or B
L-T27-SYNC-L4/main (verify) Update dashboard inventory (PR to phd-dashboard) when t27 stale = 0; update audit memo

DoD aggregate

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationone-shotONE SHOT mission issue

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions