Replacing 30-Page AI Specification Novels With a 4-Layer Progressive Intent Compiler
Why authoring giant upfront Markdown requirements documents recreates 1995 Waterfall for AI coding agents, and how lowering requirements vertically across four verified layers ships working software by Day 3.
Writing a 30-page Markdown specification before an AI coding agent writes a single line of code recreates 1995 Waterfall in a new file extension. The moment stakeholders test Slice 1 on Day 3 and adjust a workflow, pages 6 through 30 silently go stale while cloud spend burns loading obsolete prose. High-velocity organizations lock global business invariants on Day 1 and specify features strictly one verified vertical slice ahead of the compiler.
1. Why 30-Page Upfront Markdown Specifications Rot on Day 3
Burned by unstructured vibe coding, many enterprise teams have swung to the opposite extreme: spending weeks writing 30-page Markdown specification documents before an AI coding agent touches a repository. On paper, upfront completeness looks disciplined. In practice, giant upfront specifications fail for the exact reason Waterfall failed thirty years ago.
The first time a product owner or customer exercises Slice 1 in a live environment, edge cases surface and priorities shift. Pages 6 through 30 immediately drift out of alignment with reality, turning AI coding agents into fast engines executing outdated assumptions.
2. The 4-Layer Progressive Intent Compiler
Inside our Nomos governance runtime and our 14-day Gantlett Systems Seam Charters, we do not discard requirements; we compile messy business backlogs down four progressive layers underneath Claude Code, Cursor, Copilot, or Windsurf:
- Layer 0 - The 2-Page North Star Charter: Extract only non-negotiable business, mathematical, and security invariants upfront (for example, strict tenant isolation and integer minor-unit ledger math) while parking premature UI guesses.
- Layer 1 - Compiled Repository Boundaries: Encode module import boundaries and read-only main branch protection on Day 1 so coding agents physically cannot cross architectural lines.
- Layer 2 - Thin Just-In-Time Slice Specs: Author a concise 1-page specification with concrete compliance test rows strictly for the single vertical slice entering build today, tracked via cryptographic SHA-256 receipts.
- Layer 3 - Verified Sandbox Transactions: Execute code changes inside disposable Git worktrees verified by 42 millisecond structural sensor probes, sealing audit receipts and verified domain lessons on merge.
3. Converting Your Next Greenfield or Brownfield Initiative in 14 Days
Engineering leaders do not need a multi-month methodology overhaul to escape specification bloat. During a fixed-scope 14-Day AI Governance and Seam Charter Pilot ($15,000 - $25,000 USD), we distill your team backlog or legacy module into a 2-page North Star Charter, install compiled repository boundaries underneath your existing coding tools, and ship your first verified vertical slice with 100% client-retained IP.
Upfront Specification Waterfall vs. 4-Layer Progressive Lowering
| Governance Dimension | Advisory Rulebooks + Unit Tests | Deterministic Control Layer |
|---|---|---|
| Day-One Specification Footprint | 30-page unverified Markdown PRD detailing features A through Z upfront | 2-page North Star business invariant charter plus compiled repository boundary locks |
| Feature Specification Timing | Authored weeks before any code meets production data or customer feedback | Lowered Just-In-Time (1 page with test vectors) strictly for the active vertical slice |
| Impact of a Day-4 Requirement Pivot | Manual search-and-replace across 30 pages; agents build against stale paragraphs | Edit one 1-page slice spec; SHA-256 receipts pinpoint the exact affected code modules |
| AI Cloud Spend & Context Focus | Every session pays to load thousands of lines describing features months away | Agents receive only the active slice contract, cutting wasted session spend |
Install Deterministic Boundaries Underneath Your Existing AI Tools
Isolate one high-friction repository seam in 14 calendar days ($15,000 to $25,000 USD fixed fee, 2 principal-led slots/month) without changing your developers IDEs or coding agents.
Inspect the 14-Day Seam Charter Pilot →Inspect the Reproducible Lab Benchmark
Forward the underlying open-core configuration reference, raw episode telemetry, and reproducible test suite from our SophiaLabs R&D division.
Field Dispatch D-09: From 30-Page Waterfall PRDs to a 4-Layer JIT Intent Compiler (Architecture & YAML Reference) ↗