liveBook · Manning

Decorative specification

As explained in Spec-Driven Development

A decorative specification is a specification that neither governs system changes nor accurately represents the code.

A decorative specification neither governs system changes nor faithfully represents the code. With low control authority and low fidelity, it cannot be safely relied on to evolve the application. section 3.5.3

A specification is authoritative only when it both drives change and accurately constrains what is built. The contrast makes control authority and fidelity separate tests of whether a specification is alive. section 3.5.3

Figure 3.5 How alive a specification is depends on the control authority and fidelity.

The two-by-two matrix places decorative specifications in the low-authority, low-fidelity quadrant, opposite authoritative specifications. section 3.5.3

How Spec-Driven Development covers it

How deep it goes
Defines the low-authority, low-fidelity state and warns against relying on it to evolve an application.
What you can do after
Evaluate whether a specification can safely guide evolution by checking whether it drives change and faithfully reflects code.
How it connects
Contrasts with authoritative, underspecified, and reconciled specifications through control authority and fidelity.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.