A source of truth is the artifact or signal a team treats as authoritative when deciding whether work is correct or complete. That choice shapes how the team resolves disagreements and where waste accumulates. Depending on the work, the authority might be code, tests, documentation, interface contracts, or AI output; no single approach fits every context. section 4.1
Table 4.1 Abstraction shift over the evolution of software development
|
Approach
|
Source of truth
|
Motivation
|
Primary waste created
|
|
Waterfall
|
The code
|
Ship working software
|
Defects, Overproduction
|
|
Test Driven Development (TDD)
|
The tests
|
Catch defects early
|
Motion
|
|
Behavior Driven Development (BDD)
|
Human-readable feature files
|
Align business and dev teams
|
Overprocessing, Motion
|
|
Domain Driven Design (DDD)
|
Upfront design docs
|
Reduce requirement ambiguity
|
Waiting
|
|
Interface Oriented Design (IOD)
|
The interface contract
|
Enable loose coupling
|
Inventory, Overproduction
|
|
Spec Driven Development (SDD)
|
The explicit specification
|
Constrain AI from overproducing
|
Potentially none
|
Compare how different development approaches assign authority to different artifacts, from code and tests to explicit specifications. section 4.1
With a spec-first approach, define correctness before building and use the specification as a quality gate. If code diverges from it, treat the mismatch as an Andon signal: make the drift visible and resolve it before it spreads. Clarify intent upstream only when the specification itself is ambiguous. section 4.1.4
Listing 4.4 Spec file
Accept: GET /api/orders/export (authenticated user) Return: CSV file with columns: order_id, date, total, status Filter: Only orders belonging to the requesting user Format: Standard CSV, UTF-8 encoding Never: Include other users' data, build the CSV in the browser, load all orders into memory, allow unauthenticated access Prefer: Stream CSV rows from the server using bounded database reads
An order-export specification makes expected behavior concrete, including the response format, access restrictions, and streaming requirements. section 4.1.4












