Case Studies
Every project documented here is a Class 1.3 build governed by the full five-stratum STRATA sequence — classification, derivation, authority chain, execution loop, and artifact trail. What differs is the stack and the domain, not the discipline. Three of them — Fractal OSI, One Verse Daily, and AI9GM — were built before the protocol was formally specified: they followed the same layered governance independently, and their convergence is what revealed STRATA as a protocol worth extracting. StrataProtocol.org is the result, documented and built with the protocol itself. Together they serve as onboarding material, architectural reference, and proof that the governed approach works — even in its earliest, unpolished form. These narratives will be expanded progressively.
Available Case Studies
StrataProtocol.org
The reference implementation. The protocol documented, built with the protocol it documents — a Class 1.3 Platformization project on Nuxt Content and Docus. All five strata are live and traceable, from Vision and BRD through a running Artifact Trail in docs/strata/.
See: The Five Strata · Artifact Trail
Fractal OSI
Proto-STRATA in production. A Class 1.3 build on VueJS with a first-class NestJS backend and an n8n-driven AI workflow — governed by the full five-stratum sequence before STRATA was formally specified. One of the early implementations whose recurring patterns shaped the protocol.
See: The Five Strata · Authority Chain
One Verse Daily
Early adoption, content-driven. A Class 1.3 content application on VueJS with a first-class NestJS backend — delivered through all five strata, from classification to artifact trail, before the protocol had a name. Early proof that the layered approach holds for content products, not just platforms.
See: The Five Strata · Derivation
AI9GM
AI-assisted, fully governed. A Class 1.3 project on the same Nuxt Content and Docus stack as this platform — run end to end under the full five-stratum sequence while the protocol was still taking shape. Living proof that a governed authority chain keeps AI-assisted delivery on course, even in proto form.
See: The Five Strata · Execution Loop
Implementation Patterns Across the Strata
Every case study runs the same five-stratum sequence end to end — what differs is the stack, the domain, and the era. Three were built before the protocol was named; that they followed the same path independently is the strongest evidence the path is real:
- Classify the project — choose the right product category before any specification begins.
- Derive the document hierarchy — Vision, BRD, PRD, and Engineering Standards in dependency order.
- Establish the authority chain — a constitutional mandate for AI coding tools and human contributors.
- Execute in governed phases — requirement analysis, phase planning, AI-assisted delivery, and human sign-off.
- Preserve the artifact trail — maintain the living governance record across the full project lifecycle.
The complete framework documentation covers each stratum in depth. The case studies show what those strata look like when applied to real shipping projects.
See the Platform Roadmap for the case study publication timeline, and the Marketplace for practitioners available to guide implementations.
Introduction
What the AI Playbook covers — how to work with AI copilots inside the STRATA governance framework.
AI9GM
Case Study — AI9GM, a Class 1.3 project on the same Nuxt Content and Docus stack as StrataProtocol.org. An early adoption of the full five-stratum STRATA sequence for AI-assisted delivery, predating the protocol's formal specification.

