STRATA Protocol

Case Studies

Real-world projects governed by the full five-stratum STRATA sequence — across varied classes, stacks, and domains, including the early implementations that shaped the protocol before it was formally specified.
Early Access

Every project documented here is a full five-stratum STRATA build — classification, derivation, authority chain, execution loop, and artifact trail, run end to end. What differs is the class, the stack, the domain, and the era, not the discipline: these span Class 1.1 (Greenfield MVP), Class 1.2 (Expansionary), and Class 1.3 (Platformization) across VueJS, NestJS, n8n, and Nuxt/Docus. 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.

Three Categories of Evidence

These case studies establish the framework three different ways:

  • Self-referential proof — StrataProtocol.org, the premier, fully formal application: the protocol documented, built with the protocol it documents. Its governance artifacts are inspectable on this site.
  • Formal early adoption — Fractal OSI, One Verse Daily, and AI9GM each converged on the same five-stratum discipline before the protocol had a name, governed by engineering rigor rather than a named specification.
  • Diverse stacks — from VueJS and NestJS to n8n AI workflows and Nuxt/Docus, the same five strata held across unrelated technology choices. STRATA is not stack-specific.

Fractal OSI, One Verse Daily, and AI9GM were developed before the formal STRATA specification. They are documented here because they informally applied STRATA's core principles through engineering discipline, and their inclusion demonstrates that the methodology emerged from real practice.

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. The Five Strata Artifact Trail

Fractal OSI

Proto-STRATA in production. A Class 1.2 Expansionary 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. The Five Strata Authority Chain

One Verse Daily

Early adoption, content-driven. A Class 1.1 Greenfield MVP 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. 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. 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:

  1. Classify the project — choose the right product category before any specification begins.
  2. Derive the document hierarchy — Vision, BRD, PRD, and Engineering Standards in dependency order.
  3. Establish the authority chain — a constitutional mandate for AI coding tools and human contributors.
  4. Execute in governed phases — requirement analysis, phase planning, AI-assisted delivery, and human sign-off.
  5. 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.

STRATA was extracted, not invented. The same five layers kept appearing across Fractal OSI, One Verse Daily, and AI9GM — different stacks, different domains, no shared specification — until the pattern was clear enough to formalize. The protocol is the write-up of something that already worked. These projects are the proof that it worked even before it was polished.

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.

Overview

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.