Public proof sets for structural diagnosis and redesign.
Each case presents a complete artifact family. Most contain four deliverables. The Patreon / Apple IAP proof set contains five because the locked diagnosis produces two mutually exclusive restricted redesign specifications.
In each case, three artifacts form the public proof layer: Translation Artifact, Diagnostic Artifact, and Redesign Executive Summary. The restricted Redesign Artifact contains the builder-grade specification available only through a Full Structural Engagement.
These are professional deliverables, not marketing case studies or slide decks. Produced independently from public evidence. Not commissioned by the organisations named.
The point is not volume. It is repeatability. The same method produces governed artifacts for a private AI platform, a national healthcare continuity failure, and a platform-host payment boundary conflict.
Each Diagnostic Artifact follows the same structural movement: system boundary → workflow trace → functional diagnosis → governing diagnosis → correction dependency order. The Redesign Executive Summary presents the replacement logic publicly. The Full Redesign Artifact converts that logic into corrected primitive, replacement architecture, refusal invariants, transition sequence, recapture gates, and proof conditions.
Proof of structural capability, not contracted outcomes.
Outlier AI
AI task marketplace · private platformReplace the single contributor frame with a dual-stream contributor coordination system: Stream A for constrained reliability execution, Stream B for bounded expert judgment, connected by a portable contributor continuity record.
Produced independently from public evidence. Not commissioned by Outlier or Scale AI.
Plain-language entry point. Creates shared understanding of the failure and the dual-stream redesign.
Entry point: No prior knowledge required. Designed to create a shared structural read across leadership, operations, and contributor teams before moving to the full diagnostic evidence.
Best for leadership, operators, contributors, and first-time readers.
Evidence-tiered diagnosis. Names the primitive mismatch, traces the hidden burden layer, and defines the correction order.
Public-evidence boundary preserved.
Governing diagnosis: Outlier recruits through the grammar of an expertise market while operating through the mechanics of a reliability pipeline.
Primitive mismatch: stated expert judgment; actual variance-controlled instruction adherence at scale. Because the intake architecture and execution architecture select for different inputs, qualification, scoring, routing, and payment all inherit the mismatch.
Best for evidence review, leadership alignment, and understanding the governing diagnosis.
Board-level replacement logic. Shows the corrected primitive, stream contracts, proof standard, and consequence of deferral.
Replacement conditions: minimum viable structure, fake-progress tests, proof standard, and consequence of deferral.
Best for executives, product leaders, board readers, and decision owners.
Complete replacement specification.
Turns the public replacement logic into a governed build sequence: transition sequence, contributor continuity schema, consequence review model, expert signal lifecycle, compensation truthfulness invariant, recapture gates, admissibility conditions, pilot rules, and builder handoff.
The public Redesign Executive Summary shows the replacement logic. The full Redesign Artifact is the restricted specification delivered in a Full Structural Engagement.
Access reviewed by context. The full specification is not a public download.
NHS Primary Care Continuity System
Public healthcare institution · National Health Service (UK)Replace fragmented institutional memory with a patient-held operational continuity system: portable continuity record, symptom event layer, Consultation Packet, outcome append, emergency access, carer access, and recognition pathway.
Produced independently from public evidence. Not commissioned by the NHS, NHS England, or DHSC.
Plain-language entry point. Creates shared understanding of the patient-record failure and the continuity redesign.
Entry point: No prior knowledge required. Designed to create a shared structural read across clinical, policy, and operational teams before moving to the full diagnostic evidence.
Best for leadership, clinicians, patients, carers, policymakers, and first-time readers.
Evidence-tiered diagnosis. Names the continuity-poor failure, locates the collapse node, and separates operational memory from audit trace.
Public-evidence boundary preserved.
Governing diagnosis: NHS primary care is record-rich and continuity-poor. Operational memory is not structurally present at the point of clinical consequence.
Primitive mismatch: promised joined-up care; actual organisation-held records, after-the-fact sharing, and patient memory as the default continuity mechanism. The system generates more data about patients than at any prior point. Less of it arrives, in retrievable form, at the moment a decision must be made.
Best for evidence review, policy framing, clinical leadership, and understanding the governing diagnosis.
Board-level replacement logic. Shows the patient-held continuity architecture, proof standard, and consequence of deferral.
Replacement rule: patient-held ≠ patient-burdened. Includes fake-progress tests, proof standard, and consequence of deferral.
Best for policy leads, executives, clinical leaders, commissioners, and decision owners.
Complete replacement specification.
Turns the public replacement logic into a governed build sequence: seven-move transition sequence, truth-kernel schema, custody / hosting / authority separation, invalid continuity states, source-of-truth hierarchy, emergency and carer access, refusal invariants, admissibility conditions, recapture gates, pilot rules, and builder handoff.
The public Redesign Executive Summary shows the replacement logic. The full Redesign Artifact is the restricted specification delivered in a Full Structural Engagement.
Access reviewed by context. The full specification is not a public download.
Patreon / Apple IAP
Creator patronage platform · iOS monetisation boundary New proof set · April 2026Two mutually exclusive structural exits follow from the same diagnosis.
Path A — The Decoupler (continuity-preserving): Apple becomes the funding rail. Patreon remains the relationship authority. The Credit Event Log is the truth.
Path B — The Allocation Shift (category-transforming): Apple sees one platform subscription. Patreon governs allocation internally. The Patronage Allocation Ledger is the truth.
Both are structurally valid. They are not compatible. Leadership must choose one; attempting both recreates the collapse.
Path A and Path B cannot be combined. The decision is identity, not sequencing.
Produced independently from public evidence. Not commissioned by Patreon or Apple.
Plain-language entry point. Creates shared understanding of the Primitive Switch, the host-constrained mismatch, and the two redesign paths.
Entry point: No prior knowledge required. Designed to create a shared structural read across leadership, creator, product, and policy teams before the full diagnostic evidence is circulated.
Best for leadership, creators, fans, product teams, policy teams, and first-time readers.
Evidence-tiered diagnosis naming the Host-Constrained Primitive Mismatch.
Governing diagnosis: Patreon’s patronage primitive cannot be faithfully expressed inside Apple’s transaction-coded IAP grammar. At the iOS “Join” moment, a Primitive Switch occurs.
Primitive mismatch: stated relationship-coded creator patronage; actual transaction-coded subscription grammar imposed by the host platform at the payment boundary.
Best for evidence review, leadership alignment, platform strategy, policy framing, and understanding the governing diagnosis.
Board-level decision surface covering both structural exits.
Path A preserves Patreon’s existing creator-fan category through a translation layer. Path B transforms Patreon into a platform-level allocation system.
Best for executives, founders, board readers, product leaders, platform strategists, policy teams, and decision owners.
The Decoupler. Continuity-preserving replacement.
Complete builder specification for The Decoupler — the continuity-preserving exit that preserves bilateral creator-fan patronage behind an Apple-compatible payment rail.
Includes the Credit Event Log, Dual Ledger, Fan Agreement Object, Publication Event Handler, refusal gates, Translation Engine, Reconciliation Reserve, fan-facing credit balance, creator-facing per-creation earnings interface, transition sequence, admissibility conditions, recapture gates, drift immune system, and builder handoff.
Apple funds the relationship. Patreon defines it.
The public Redesign Executive Summary shows the replacement logic. The full Path A specification is restricted.
Access reviewed by context. Include organisation and request context. The full specification is not a public download.
The Allocation Shift. Category-transforming replacement.
Complete builder specification for The Allocation Shift — the category-transforming exit that replaces bilateral creator-fan payment with platform-level patronage allocation.
Includes the Platform Subscription Object, Fan Patronage Account, Allocation Rule Object, Patronage Allocation Ledger, Allocation Engine, Publication Event Listener, Creator Payout Engine, Reconciliation Reserve, fan allocation UI, creator payout interface, payor-of-record architecture, relational frame invariants, transition sequence, admissibility conditions, recapture gates, drift immune system, and builder handoff.
Apple sees one platform subscription. Patreon governs allocation internally.
The public Redesign Executive Summary shows the replacement logic. The full Path B specification is restricted.
Access reviewed by context. Include organisation and request context. The full specification is not a public download.
The Patreon / Apple IAP diagnosis produces a strategic fork, not one obvious redesign.
Path A preserves Patreon’s existing creator-fan category by installing a translation layer between Apple’s payment grammar and Patreon’s patronage relationship.
Path B transforms Patreon into a platform-level allocation system where Apple sees one subscription and creator-level economics are governed internally.
Both are structurally valid. They are not compatible. The decision is not which feature to build first. It is what Patreon is going to become.
A serious redesign artifact does not just say what to build. It also names which futures cannot be pursued together.
The domain changes. The structural method does not.
In all three systems, the visible failure is downstream of a missing or mislocated governing function.
In Outlier, contributor continuity and work-class truth are absent at the point of routing, scoring, and consequence.
In NHS primary care, operational memory is absent at the point of clinical decision.
In Patreon / Apple IAP, faithful economic translation is absent at the host payment boundary, so creator-defined patronage is forced into Apple’s subscription grammar.
Hidden human carriers absorb what the architecture cannot hold. Queue Managers, contributors, and external tooling carry platform coherence in Outlier. Patients, carers, known GPs, and informal practice staff carry continuity in NHS primary care. Creators, fans, support teams, and off-platform instruction layers carry the Patreon / Apple IAP mismatch through explanation, routing, and manual workaround.
In all three cases, correction remained inside the inherited frame: more support, more compliance, more digital surface, more communication, more process, more migration tooling, more workaround explanation. The primitive remained untouched.
The artifacts demonstrate the same conversion across domains: recurring failure → structural diagnosis → replacement architecture → proof condition.
Patreon demonstrates that a single locked diagnosis can surface a genuine strategic fork rather than a single replacement path. That is further evidence that the method operates at the level of system identity, not incremental improvement.
This is the redesign law: diagnosis can name the structural failure, but correction loops operating inside the existing frame cannot generate the primitive change the system requires.
Why the Full Redesign Artifacts are restricted
The public proof layer is sufficient to demonstrate the method, evidence boundary, governing diagnosis, and replacement logic. The restricted Redesign Artifacts are restricted because they contain the build-value layer: transition sequence, refusal invariants, admissibility conditions, recapture gates, pilot validity rules, object-level specifications, truth-kernel schemas, and builder handoff.
In some proof sets, there is one restricted specification. In the Patreon / Apple IAP proof set, there are two, because the public diagnosis produces two mutually exclusive replacement paths.
The public documents prove the method. The restricted documents preserve the build value.
Restricted Redesign Artifacts are not published as sample documents. Access can be requested, but the full specification is not a general resource.
If your system has a recurring failure pattern, send the failure pattern first. The five-line brief is a fit screen, not the diagnosis. Do not send a solution. Send the repeated failure.
The Method page explains how these artifacts are produced. The Services page defines how they are commissioned.
These public examples demonstrate the method in action across domains. If your organisation is experiencing recurring structural failure under scale, the next step is simple: send the five-line brief.