Structural problems don't look like structural problems.
Structure determines outcomes.
Not effort. Not talent. Not intent.
The written thesis lives here: essays, patterns and the four-book Decision Architecture series. The shipped evidence (applications, tooling and a published protocol) lives in the portfolio.
Most systemic failure is not caused by poor code. It is caused by unclear authority, delayed decisions and trade-offs that no one is explicitly accountable for.
I do not just build software. I design the conditions under which it can be built well.
Selected artifacts a protocol, its reference client, and this page proving both
Reference implementation
Meridian
The reference client for MMSP: the protocol shipped as a desktop
application that people actually run.
See the client →
/.well-known/mmsp.json →
Decision-support / simulation tool
Fulcrum: Decision Architecture as an engine you operate
Model any organisation, score its structural health from 0 to 100 and
find the moves that make it stronger.
Open Fulcrum →
Design-time / simulation tool
LatencyLab: the cost of structure, priced before it hardens
Model an event-driven system, run it deterministically from a stated
seed and see where queues, delays and contention actually bite.
Open LatencyLab →