Case studies are a side effect of the work.
We publish anonymized writeups of completed engagements: the audit findings, the migration shipped, and the followup-loop outcome four weeks after delivery. No invented success stories, no client logos before the engagement is real, no marketing-led case studies.
Status
Booking opened in May 2026. We publish a case study from each engagement that crosses two gates:
- The client's
PUBLISH_POLICY.mdhas the case-study checkbox set yes. - The four-week followup loop has produced a measurable outcome (positive, negative, or null — we publish all three).
Until the first engagements clear both gates, this page is empty by design. The discipline is build-in-public, not market-in-public.
What a case study looks like when it lands
Each case study covers five fields, in this order:
- Situation. The client's stated pain point at intake, the workflows reported, the tier purchased.
- Findings. The most-load-bearing gap the audit surfaced — usually one of: vendor lock-in, sovereignty drift, audit-trail thinness, observability cost.
- What we shipped. The concrete migration steps the client executed (or had us execute under a separate engagement), and the prerequisites we flagged.
- Outcome at the followup loop. Numeric where possible (break frequency change, maintenance hours change, cost delta, time-to-detect change). Honest where the numbers don't move yet.
- What we'd do differently. The decision in the engagement that, with hindsight, would have changed direction. Every engagement gets this section.
Anonymized by default. The client name only appears if they explicitly opt in twice — once in their publish policy and once in writing on the published draft.
If you want your engagement published
Most engagements stay private — that's the default. If you'd like yours considered for public writeup, set the case-study flag in your publish policy at any time before, during, or after delivery. You always have the right to revoke it before publication.
How case studies get here (in the public repo)Methodology + receipts in the meantime
Until the first case studies publish, you can read how we operate in three places:
- The methodology page — operator gates, agent execution boundaries, evidence trails.
- The public repository — ADRs, runbooks, infrastructure audits, commit history.
- Orchestral — the open-source methodology framework.
Receipts compound. Trust accretes through visible decisions, not through claims.