Articles on Product Definition as Code
This is where I write about the problem behind Product Definition as Code, the model I am proposing and the evidence that would make it worth adopting.
These are not release notes, generic software advice or search-engine filler. Each article starts with a real engineering problem, makes one argument and points to primary sources or runnable evidence.
Start here
Section titled “Start here”Your software specification is not your product definition
The first article explains why a delivery specification is not a durable home for product intent, and what PDaC is intended to change.
Continue with the lineage
Section titled “Continue with the lineage”Where Product Definition as Code comes from
This article maps each part of the methodology to the disciplines, standards, products and tools it came from.
See the boundary in practice
Section titled “See the boundary in practice”This article shows that layer built for a concrete SDD framework: four unserved Spec Kit requests, the boundary that made the literal ask a trap, and the citation mechanism that fills the gap, installable in two commands.
An architectural experiment in progress
Section titled “An architectural experiment in progress”Maybe ProductShape should do less
ProductShape grew a workflow engine to make PDaC executable. OpenSpec may now do that job better. This article exposes the reasoning, the prior art and the spike that will test whether part of ProductShape should move to OpenSpec, written before the experiment is implemented.
More articles will cover Product Changes, citations in depth and a worked example of specification drift.