This is a design-partner case study. Logo and company name are placeholder until our partner consents to public attribution. Numbers are real.
The problem
A regulated claims processing platform with 4,500 internal pages of runbooks, policy interpretations, and decision-tree documentation. Compliance team kept finding "doc-code drift": the runbook described one decision flow, the production code did another. Why? Because the runbook lived in Confluence and the code in git, and no one ever proved they matched.
What changed
- StaticOwl became the doc store. Every page lives in the graph, with valid-time and recorded-time stamps.
- Engineering's runbook edits trigger a workflow transition that requires a compliance reviewer.
- The compliance reviewer's approval is bound to the content hash of the version they approved. Edit after approval → review goes
stale→ re-review required. - Quarterly audit pulls a compliance bundle (signed JSON + Markdown) for offline verification. Auditor verifies the chain in 4 minutes; previously took two weeks.
Result
- Doc/code drift findings: 17 in the prior quarter → 0 in the first audit after rollout
- Audit prep time: 80 hours → 6 hours
- Compliance reviewer NPS: from -23 (Confluence) to +51 (StaticOwl). The biggest win was knowing what they were approving wouldn't silently change.