Proof Sets

Three systems. One structural method.

Each case presents a complete artifact family produced independently from public evidence and not commissioned by the organisation named. Most contain four deliverables. Patreon / Apple IAP contains five because the locked diagnosis produces two mutually exclusive restricted redesign specifications.

Three artifacts form the public proof layer: Translation Artifact, Diagnostic Artifact, and Redesign Executive Summary. The Full Redesign Artifact carries the builder-grade transition sequence, invariants, recapture gates, and handoff specification and remains restricted.

The point is repeatability. Each case moves through the same structural sequence: system boundary → workflow trace → functional diagnosis → governing diagnosis → correction dependency order. The domain changes; the proof standard does not.

Proof of structural capability, not contracted outcomes.

3Systems
9Public proof documents
4Restricted specifications
How each proof set is structured
Artifact Status Role
Translation Artifact Public Start here. Shared language entry point into the failure and replacement.
Diagnostic Artifact Public Full evidence base and governing diagnosis.
Redesign Executive Summary Public Board-level replacement logic and proof conditions.
Full Redesign Artifact Restricted Complete transition sequence, invariants, recapture gates, and builder handoff.
Note Most proof sets contain one restricted Full Redesign Artifact. The Patreon / Apple IAP proof set contains two because the locked diagnosis produces two mutually exclusive redesign exits.
Standard proof template — applied to each system 8 fields · same structure · every proof set
Domain
The sector and system type under analysis
Primitive
The smallest unit of real work the system is organised around
Failure class
The taxonomy class and subtype that governs the break
Burden carrier
Who absorbs the work the system fails to carry
Governing diagnosis
The structural truth from which the rest of the failure follows
Artifact set
The four-artifact sequence produced from the locked diagnosis
Replacement direction
What the corrected system must be organised around
Proof standard
What the diagnosis must survive to be valid
Each dedicated proof page carries the completed template and the full artifact sequence.
Choose a proof set. Each dedicated page carries the full case context, governing diagnosis, artifact sequence, public documents, restricted specification, and related proofs.
01 // Proof Set

Outlier AI

Class 7.2 — Ambiguity Absorption Failure

Outlier recruits through the grammar of an expertise market while operating through the mechanics of a reliability pipeline. In plain terms: the platform recruits experts to do compliance work.

4 artifacts · 3 public · 1 restricted

VIEW FULL PROOF →
02 // Proof Set

NHS Primary Care Continuity

Class 9.8 — Care Continuity Failure

NHS primary care is record-rich and continuity-poor. Operational memory is not structurally present at the point of clinical consequence, so the patient becomes the record.

4 artifacts · 3 public · 1 restricted

VIEW FULL PROOF →
03 // Proof Set

Patreon / Apple IAP

Class 1.1 — Host Platform Constraint

Apple IAP forces Patreon’s patronage primitive through subscription grammar at the host payment boundary. The tap is the point of compression.

5 artifacts · 3 public · 2 restricted

VIEW FULL PROOF →
Shared proof structure

The domain changes. The proof standard does not.

Every case moves through the same public sequence: shared-language translation, evidence-tiered diagnosis, then board-level replacement logic. The restricted Full Redesign Artifact carries the implementation-grade specification.

The proof sets demonstrate method transfer across domains. They do not claim commissioning, implementation, or client outcomes.

Restricted layer

Why the Full Redesign Artifacts are restricted

The public layer is sufficient to show the diagnosis, evidence boundary, replacement logic, and proof standard. The Full Redesign Artifact contains the builder-grade transition sequence, invariants, recapture gates, and handoff specification used in a Full Structural Engagement.