liveBook · Manning

Source of truth

As explained in Build High Value Software Systems

The artifact or signal that a team treats as authoritative for determining correctness, completion, and resolving disagreements.

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

How Build High Value Software Systems covers it

How deep it goes
Defines authority, compares development approaches, and applies spec-first checks to code drift without prescribing one universal authority.
Examples
Compares authoritative code, tests, feature files, design documents, interface contracts, and specifications, then gives an order-export spec.
What you can do after
Evaluate/understand it by defining correctness before building and treating code–spec drift as a signal to resolve.
How it connects
Connects source-of-truth choices to TDD, BDD, DDD, IOD, SDD, tests, code, and interface contracts.

Also explained in

Compare how 13 books explain source of truth →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.