09 Why the method holds

09 · Why the method holds

At the base of the method stand, then, four principles — the specification as source of truth, the reasoned and tracked decision, the iterative dialogue that opens and records its own open questions, the multiplicity of interlocutors; one then considers scope and the good-enough criterion, glossary and references as attributes that make them operative effectively. None of these is independent: they work because they reinforce one another, as the experience accumulated in their use suggests.

The specification as source of truth gives the dialogue a place to settle: without it, the dialogue evaporates. The numbered decisions give the specification a memory structure: without them, the specification is a text re-read from scratch every time. The open points give the process a way to proceed without lying about its own incompleteness: without them, one either stalls or feigns a certainty that is not there. The distinct interlocutors give the reasoning a range of perspectives: without them, the quality of thought is limited to that of a single point of view.

• Source — the specification is the primary artefact; the product is derived from it and verifiable against it
• Memory — numbered decisions make what has been chosen citable and not up for re-debate
• Continuity — the additive constraint prevents the silent loss of content between versions
• Perspective — distinct interlocutors multiply the points of view on a single problem

Each of these pillars comes from a consolidated practice, born for work among human beings. What the method adds is their recontextualisation in human–AI work, where each acts on two fronts at once: it disciplines a failure mode proper to the model and, in the same gesture, structures the reasoning of whoever guides it.

Pillar	Origin	Gain on the human side	Model failure mode it answers
Specification as source of truth	spec-driven development	a single place where the group's reasoning settles and can be found again	the model's reasoning evaporates in the flow
Reasoned and tracked decision	architecture decision records	the team does not re-litigate what had already been settled	state revisitation: the model recycles solutions already discarded
Iterative dialogue with open points	design doc, open points	forces the operator to be explicit and not to feign certainties	passive acceptance of the output, false certainties
Multiplicity of interlocutors	groupthink, dialectical inquiry	opens the operator's perspective beyond their own point of view	echo chamber, crystallisation of the single model

The decision log keeps the model away from recycling discarded solutions, and at the same time spares the human team from re-deliberating what is closed; the multiplicity of interlocutors breaks the crystallisation of the single model, and at the same time opens the operator's perspective beyond their own. No pillar, alone, covers all the fronts; it is their working together, on the same persistent artefact, that produces what the sum of the pieces does not give: a reasoning of many voices — human and artificial — that is not lost, and that remains executable by whoever comes after. The effect observed in use is a leap in yield: a few people assisted by models produce, with this framework, results that would previously have required larger teams and longer times. It is an observation from use, not a measurement; and it is in this composition, not in the single bricks, that the method finds its own reason and its own name.

The observed result is twofold. On one side, the work becomes recoverable: an interrupted session is resumed from the document, not from memory; a new person enters the project by reading the decision log. On the other, the quality of the reasoning increases, because the method forces the making-explicit of what would otherwise remain intuition, and because it exposes the problem to more perspectives than a single operator would bring.

There is a third effect, which answers directly the echo chamber described at the outset. By concentrating competence in the drafting phase of the specification — and multiplying the interlocutors there — the method curbs the amplification of the operator's limits precisely where it would be most damaging. And the product of that phase, the specification, remains as a structured artefact that whoever comes after can execute without having to re-confront the open problem: competence spent once is reusable by whoever lacks it, be they human or agent.

A method recoverable, traceable, and open by construction

---

← 08 · Two ways to break the single perspective · The Method · 10 · Where the method costs and where it falls short →