STRATA Protocol

The STRATA Protocol is a governance framework for AI-assisted software delivery. This portfolio entry is not about the framework itself — that lives at strataprotocol.org. It is about the platform: the server-rendered Nuxt 4/Docus application built to document and demonstrate it.

What makes this project distinctive is its self-referential architecture: StrataProtocol.org was built by applying the very methodology it documents to itself. The platform is the framework's Case Study #1 — governed by the framework's own authority chain, executed through its phased delivery loop, with a complete artifact trail published and publicly navigable.

The platform

StrataProtocol.org is a full-featured, production-grade SSR application, not a styled documentation theme. Its engineering includes:

• Two-layer content protection. Member content is independently guarded at the browser layer and the server layer. Each layer is insufficient alone; both must be kept in sync. SSR is a security requirement, not a preference — static export would bypass the server-side guard entirely.
• Dual user and role model. Membership tier and system role are resolved separately; admin authority supersedes membership level. Sessions are sealed HttpOnly cookies with timestamp-based invalidation — a password change rejects all prior sessions.
• Full account lifecycle. Registration, email verification, login, logout, password reset, and profile management — each built to a documented standard and tested.
• Admin console and audit trail. User management, account enable/disable, force-password-reset, and every privileged action recorded to a queryable audit event log.
• PostgreSQL data layer via Drizzle ORM, with generated migrations and a startup migrator/seeder.
• Lead-capture funnel. A multi-step qualification wizard that submits to the server before opening calendar booking — so the operator captures the lead even if the visitor abandons scheduling. Rate-limited and field-validated at the API boundary.
• Themeable design system. Five named theme presets, each a curated color pairing over the Nuxt UI token layer — a productized theming surface, not ad hoc overrides.
• Interactive embeddable diagrams. Live STRATA diagrams render inline through a sandboxed, chrome-less canvas embedded from a companion application — the same embeddable canvas engineered for Fractal OSI — with fail-closed configuration and a coordinated scroll handoff so the diagrams behave like native page content.
• SEO, authorship, and citation infrastructure. Structured author identity, per-page meta, and a formal citation surface ready for scholarly indexing.
• Legal suite. Five policy pages, clickwrap consent gating registration, and a full footer legal row.
• Containerized SSR deployment. Alpine Node image with a PostgreSQL compose stack; stateless application design with the content SQLite store relocated to a writable path and restored from a bundled snapshot on start.

Cadence: fast, and fully auditable

The delivery pace is itself part of the case. From its first commit, the platform reached a stable, production-ready version in under one month — a window of roughly four weeks that took it from an empty repository to two-layer RBAC, a full account lifecycle, an admin console, a hardened lead funnel, and a containerized PostgreSQL deployment — and it has been continuously refined ever since, never abandoned at "good enough."

What makes the pace credible rather than reckless is that none of it cost traceability. All of this — plus sixty-plus published documentation pages — was delivered across twenty numbered requirements, with every commit tagged to its requirement and phase (feat(REQ-020-legal): Phase 5 — …), so the entire month of work is reconstructable from the commit history alone, decision by decision. Governance did not slow delivery; the discipline is precisely what made the speed sustainable and auditable at the same time.

How this connects to the methodology

StrataProtocol.org is the canonical live demonstration of the approach described in Methodology: project classification, document derivation, authority chains, phased execution, and a full artifact trail — each one applied to the production platform whose purpose is to teach them. Every feature named above traces to a numbered requirement; every requirement traces to a business goal.

The framework's depth — its five-stratum structure, the full conceptual model, and the developer toolkit — lives at strataprotocol.org. The platform engineering is what this entry features.