Two ways to engage.
I make the hidden rules visible, locate the structural failure precisely, and produce a written artifact your team can act against.
Two fixed-scope engagements: a Diagnostic Artifact that names the real failure, and a Redesign Artifact that defines the change sequence. Read the method →
The same failure costs more the second time than the first. At some point, the structure has to be named.
It does not add another summary or interpretation 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.
Humans stop carrying work the system should carry. The artifact defines what the system must enforce, what it must not absorb, and where the boundary sits.
Two fixed-scope written engagements. Start with diagnosis when the failure is still structurally unclear. Move to redesign when the failure is visible but the transition path is not.
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.
Start here when the failure is visible but the change sequence is not. Use it to define what changes first, what stays fixed, and how regression is blocked.
When to use this: The failure is understood but the transition path is not. Builders are being forced to invent design midstream. Implementation keeps drifting back to the same broken state.
Four questions. Answer them honestly and the structural problem — if there is one — becomes visible. Use this before you send a brief.
Three papers diagnosing recurring failure across platforms, institutions, and self-correcting systems. Together they move from mismatch between signalled and consumed capability, to collapse through function fusion under consequence, to the missing redesign layer that internal correction loops cannot reliably produce.
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 determine whether the work should begin with diagnosis or move directly to redesign.
The five-line brief is a fit screen, not the diagnosis itself.
Send the brief. Five lines plus any relevant material you already have.
I review fit. Diagnosis if the structure is still unclear; redesign if the failure is already visible.
You receive the artifact. One written document built for decision-making and builder execution.
If neither engagement is the right fit, I will say so.