Why our specs only contain decisions

A spec should be a decision document, not a documentation document.

The human writes only what only a human can decide: the problem, the success metric, the definition of ambiguous terms, the edge-case calls, and what's explicitly out of scope. Everything mechanical — accessibility, internationalization, telemetry, rollout patterns, acceptance criteria — is scaffolding the system fills in.

The 30% tax

Thin specs feel fast. They aren't. The gaps surface later as bugs, and fixing them after the fact costs roughly a third of the build again. A decisions-only spec front-loads the thinking that actually requires a human, and lets the pipeline handle the rest.

That same spec then feeds both the build and the launch pack — one source of truth, two outputs.

This is the discipline behind every product in the showcase.