Technical whitepaper 1.2 · Binder-Integrated Foundational Revision · September 2026

    Proof-Horizon Sharding

    Correction-Surviving, Proof-Carrying Canonical Computation

    Breyden E. Taylor — Founder, Inventor and Architect, Prompted LLC

    Core claim

    Proof topology should follow epistemic dependency, not workspace topology. Many humans, agents, machines, clones, repositories, and organizations may inspect and prove an evolving system in parallel, while one serial authority advances what the system accepts as canonical.

    Read the full paper Evidence ledger

    Standing

    A peer paper in the flat papers register. It originates the temporal evidence protocol; it does not sit above FORKED, Fractal Quivers of Quivers, Computing Around the Open Center, or the Frontier apparatus, and none of them sits above it.

    The governed-horizon primitive is inherited from the Ubiquity architecture and its FORKED estate. PHS does not claim to originate horizon geometry. Its distinct contribution is the temporal-evidentiary specialization of horizon noncollapse.

    Technical Whitepaper 1.2 — publication candidate. A from-the-top rewrite of the foundational protocol paper. v1.1 and v1.0 remain lineage, not current authority. This is a technical disclosure and architecture paper, not a patent opinion or claim-construction document.

    Words
    25,031
    Rendered pages
    69
    Sections
    21 + 6
    References
    38

    Revision 1.2 — eight material corrections

    1. 01

      Retains the intellectual lineage from Prompted LLC and Ubiquity through Fractal Quivers of Quivers, Computing Around the Open Center, and FORKED to PHS.

    2. 02

      Distinguishes the upstream invention of governed horizon geometry from the PHS-native use of lawful knowability as an evidence partition key.

    3. 03

      Reconstructs the operational prehistory through the covenant, strike, cable, board, winch, basin, and anchor machinery documented by THE BINDER.

    4. 04

      Makes explicit that those mechanisms are one recurrent current-to-target loop with different roles, not a loose vocabulary and not synonyms for PHS.

    5. 05

      Identifies the tic-768-to-770 horizon-quiver build as a decisive self-falsifying construction event.

    6. 06

      Expands the protocol invariants with anchor preservation, residue visibility, anti-vacuity, observer-artifact non-occlusion, currentness-at-the-act, and honest-negative carriage.

    7. 07

      Integrates a fuller lived falsification history without converting operational evidence into universal proof.

    8. 08

      Preserves the binder's negative findings as load-bearing results rather than editorial caveats.

    The reference epoch

    Seven horizons. Each one names the earliest point at which a claim can lawfully be known. No observer may claim a rung it did not reach.

    1. H0Candidate or covenant dispositionA proposal is bound to a target before any execution is admitted.
    2. H1Source-bearing subjectAn exact immutable subject is selected and frozen.
    3. H2aDistribution proofThe subject is published through governed synchronization and read back directly.
    4. H2bIndependent reproduction proofA separate observer acquires and reproduces the exact subject. No local probe may claim this rung.
    5. H3Receipt / state carrierA descendant carrier is created from the resulting receipts. It cannot yet prove its own subsequent remote state.
    6. H4Carrier checkpointThe carrier's own distribution becomes provable in its turn.
    7. H5Terminal reconciliationConvergence, with evidence classes still distinct.

    Honest negatives

    These are results, not disclaimers. A protocol that discards its own negative findings has already broken its evidence law.

    • Fixture-green is not live-fired.

      A green fixture proves the harness ran, not that the governed path executed against a live subject.

    • The economy remains SimOnly.

      The 202-tic GUNSLINGER run exercised tempo and anchor exclusion in simulation. No live money and no external economic effect. [BND-11]

    • basin_drained has not fired live.

      One deep basin exercise does not establish broad drain liveness. [BND-19]

    • The rollback refusal path is armed but never needed.

      Five armings, zero refusals across 213 rows. Armed-but-not-fired is a valid evidence class, not a proven refusal. [BND-22]

    • Winch vocabulary does not prove WinchDial traversal.

      Campaign language is not a code path. Not every wave is shown to have crossed the implementation. [BND-15]

    • Row-level totals remain binder-indexed.

      The two lane-complete extracts were not in the drafting attachment set, so 161 cable receipts, 68 drain receipts, 51 campaign files, 213 ledger rows, and 202 economy artifacts are indexed, not independently verified.

    Section map

    Plates

    • Figure 1. Intellectual and architectural lineage. PHS inherits Ubiquity's constitutional substrate and specializes FORKED's horizon-noncollapse doctrine along the temporal-evidentiary axis.
      Figure 1 — Intellectual and architectural lineage. PHS inherits Ubiquity's constitutional substrate and specializes FORKED's horizon-noncollapse doctrine along the temporal-evidentiary axis.
    • Figure 2. The operating loop reconstructed from THE BINDER. Covenant, strike, cables, board, winch, basin, anchor, and receipts are distinct roles inside one recurrent current-to-target motion.
      Figure 2 — The operating loop reconstructed from THE BINDER. Covenant, strike, cables, board, winch, basin, anchor, and receipts are distinct roles inside one recurrent current-to-target motion.
    • Figure 3. The tic-768-to-770 horizon-quiver construction event. The instrument's own name was subordinated to the evidence it actually obtained.
      Figure 3 — The tic-768-to-770 horizon-quiver construction event. The instrument's own name was subordinated to the evidence it actually obtained.
    • Figure 4. Governed checkpoint history overlays immutable succession, independent proof, and explicit authority.
      Figure 4 — Governed checkpoint history overlays immutable succession, independent proof, and explicit authority.
    • Figure 5. Proof-Horizon Sharding reference epoch.
      Figure 5 — Proof-Horizon Sharding reference epoch.
    • Figure 6. GUNSLINGER and HIDALGO alter execution tempo without changing PHS evidence law or canonical authority.
      Figure 6 — GUNSLINGER and HIDALGO alter execution tempo without changing PHS evidence law or canonical authority.
    • Figure 7. A governed proof swarm scales observers while retaining one convergence path.
      Figure 7 — A governed proof swarm scales observers while retaining one convergence path.
    • Figure 8. Operational emergence of the winching machinery and horizon-quiver build, reconstructed from THE BINDER's dated landmarks.
      Figure 8 — Operational emergence of the winching machinery and horizon-quiver build, reconstructed from THE BINDER's dated landmarks.
    • Figure 9. Nested August 2026 GitHub Pulse windows supplied by the author. Values are gross tracked additions and deletions, not quality, deployment, or outcome measures.
      Figure 9 — Nested August 2026 GitHub Pulse windows supplied by the author. Values are gross tracked additions and deletions, not quality, deployment, or outcome measures.

    Downstream implementation

    The Forge Implementation of Proof-Horizon Sharding — Downstream implementation paper (v1.0), citing PHS v1.1. It does not originate the protocol, and no authorship or Prompted LLC lineage transfers to the implementation organization.

    The implementation dispatch

    Sealed artifacts

    Rows marked held are cited but not published here. Write breyden@prompted.community to request access to a cited private artifact.

    Recommended citation

    Taylor, B. E. (2026). Proof-Horizon Sharding: Correction-Surviving, Proof-Carrying Canonical Computation (Technical Whitepaper 1.2, Binder-Integrated Foundational Revision). Prompted LLC.

    Copyright (c) 2026 Prompted LLC. All rights reserved.

    Cross-citations in the authored corpus

    Declared relations to papers already in this record, each with the reason it is load-bearing. Companion apparatus citing peer papers. Nothing here places Frontier above any sibling paper, and nothing here places a sibling paper above Frontier; the papers register stays flat.