Scriven Labs's full product spec is written: more than 900 lines, architect-reviewed, with nine gaps closed before a single line of code. We're shipping the plan in public because the plan is the product's backbone.

Why a spec this heavy

Every constraint that makes Scriven Labs trustworthy lives in the PRD and traces to an explicit requirement: text-only output, no card without a citation, provenance-gated claims, publish-time access checks, blame-neutral shared cards, tenant isolation at the database layer. These aren't things you bolt on later. They have to be designed in from the first page.

Nine gaps, closed early

The architect review existed to find the places where the product would quietly break its own promises under load, at the edges, or when two rules collide. Nine such gaps were found and closed on paper, where they're cheap, instead of in production, where they're not.

The result is a spec every feature and every line of code can point back to. When something ships, it's because the plan said it should, and the plan said why.