Structural problems don't look like structural problems.
I don't just write about architecture.
I ship it.
A published protocol, its reference client and a portfolio spanning full-stack web, desktop applications, libraries and developer tooling, always clean architecture throughout.
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
Open protocol · spec
MMSP
A published protocol for structured multimedia feeds, an evolution of RSS.
I did not adopt a standard. I authored one.
Read the spec →
Reference implementation
Meridian
The reference client for MMSP: the protocol shipped as a desktop
application that people actually run.
See the client →
This page is itself an MMSP publisher.
The feed you would open in Meridian is served live from this site:
spec, client and a running instance, all here.
View feed
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 →