I produce fixed-scope diagnostic and redesign artifacts that name the hidden structural break, locate the governing mismatch, and give builders a governed replacement sequence.
Written artifacts · Fixed scope · No hourly rates
The same failure costs more the second time than the first. At some point, the structure has to be named.
Three systems. Thirteen complete deliverables. Nine public proof documents. Four restricted specifications. Each proof set demonstrates the same structural movement: shared language → structural diagnosis → public replacement logic → restricted full specification.
Recruited as an expertise market. Operated as a reliability pipeline. Every downstream mechanism — qualification, scoring, routing, pay — inherits the mismatch.
Three public proof documents and one restricted full redesign specification.
Patreon’s founding patronage primitive cannot be faithfully expressed inside Apple’s transaction-coded IAP grammar. At the iOS “Join” moment, a Primitive Switch forces relationship-coded support into an Apple-governed subscription event. The proof set surfaces two mutually exclusive exits, not one linear fix.
Three public proof documents and two restricted full redesign specifications.
It does not add another opinion layer. It gives decision owners and builders a shared structural read of the failure, the rule that is breaking, and the order in which change must happen.
The repeated symptom stops being discussed as a moving target. The structural failure is named once and located precisely.
The artifact becomes the design source. Builders execute against a written structure instead of inventing interpretation midstream.
The artifact defines what the system must enforce, what it must not absorb, and where the boundary sits. It identifies the Ghost Structure: manual workarounds, off-platform instructions, informal memory, and compensating human labour that exist because the structure does not carry the function itself.
This is the only way to engage. Two fixed-scope engagement paths. Not consulting, not workshops, not open-ended advisory. Diagnostic only when a structural read is the immediate need. Full Structural Engagement when naming the failure without a change sequence would simply restart the cycle.
Start here when something keeps breaking but the real failure is not yet visible. Use it to make the real rules visible before builders move.
When to use this: The same failure keeps reappearing. Teams disagree on what the problem actually is. Policy and reality have drifted apart. No one has a single structural read everyone can act against.
If redesign is commissioned separately at a later stage, the total across both engagements will be £35,000.
Includes the full diagnostic and redesign sequence, plus the Translation Artifact and Redesign Executive Summary required to circulate the work across leadership, product, operations, and builders. No hourly rates.
When to use this: The failure is serious enough that naming it is not sufficient. Leaving builders without a change sequence simply restarts the cycle.
Diagnosis always runs first. Redesign follows only after the governing diagnosis is accepted. Where diagnosis reveals a strategic fork, the redesign provides the decision surface and restricted specifications required to choose between incompatible futures.
The Diagnostic Artifact names the structural truth. The Full Structural Engagement carries that truth into the change sequence. Full details on the Services page.
Four questions. Answer them honestly and you will know whether the failure is structural, and where to look first. Use this as a first-pass fit check before briefing.
The Diagnostic Lens Trilogy is the entry point into a ten-paper public research sequence. Papers 1–3 diagnose recurring structural failure. Papers 4–6 define replacement, substitute construction, and admissibility. Papers 7–8 name the correction sequence and host constraint. Papers 9–10 reduce the series to coordination kernels and turn that reduction into a generative method. The papers define the public laws behind the artifacts; the client work applies those laws to a bounded failure pattern.
How reliability pipelines borrow the language of expertise. Introduces interface-legitimacy mismatch and the Transfer Test: systems that signal one kind of capability while operationally consuming another.
Introduces the Four-Function Law: institutions fail under scale when sensing, interpretation, authority, and memory remain fused in the same human node at the point of consequence.
Introduces the Redesign Law and correction collapse. Distinguishes execution, diagnosis, and redesign, and shows why the first two cannot reliably produce the third from within the same correction loops.
A failure has started repeating and nobody has a single structural read of what is actually wrong.
The issue is narrow, isolated, and already understood at the technical layer.
If your system keeps failing in the same way under growth, send the failure pattern first. I review fit and confirm whether the right path is the Diagnostic Artifact alone or the Full Structural Engagement.
The five-line brief is a fit screen, not the diagnosis itself. Do not send a solution. Send the repeated failure.
Send the brief. Five lines plus any relevant material you already have.
I review fit. I confirm whether the right path is the Diagnostic Artifact alone or the Full Structural Engagement. No one moves directly to redesign — diagnosis always runs first.
You receive the artifact. Either one Diagnostic Artifact, or the full deliverable set in the Full Structural Engagement: Translation Artifact, Diagnostic Artifact, Redesign Executive Summary, and Full Redesign Artifact.
If neither engagement is the right fit, I will say so.
