Three cases, chosen because each proves something the others cannot: technical architecture, leadership under constraint, and builder-operator discipline. They are organised by the decisions inside them rather than by employer or by year.

Waypoint — career intelligence with provenance

Read the case study →

A system built so that its own guarantees can be verified from outside it.

Privacy guards deliberately broken

6

That no test noticed

1

Assertions run against the live database

17

Product architecture · PostgreSQL · Access control · Data provenance · Verification

A submarine modernization program

Read the case study →

A modernization availability of roughly $200 million, delivered about two months early, with a technical team of about thirty.

Availability value (approximate)

$200M

Delivered ahead of plan (approximate)

2 months

Technical team led (approximate)

30

Program leadership · Schedule execution · Cross-functional coordination · Technical risk

A one-person operation, run as a system

Read the case study →

Curriculum production rebuilt as a compiler, with the write permissions of its own automation treated as a safety problem.

Artifact types compiled from one source

5

Zones bounding what automation may write

7

Enforcement points: write time and merge

2

Systems design · Build pipelines · Quality engineering · Multi-agent operations