The spec is the interface

Module two is how you operate as a Director, and it rests on one move: you direct AI by handing it a specification, not a request. The spec is the interface between your intent and the model's output. This is the exact hinge from Module zero, the leap from Editor to Director, made concrete. A Director does not react to drafts. A Director writes the contract the draft must satisfy, then hands it over.

The reason this matters so much is mechanical. A model fills whatever you leave unspecified with the most probable continuation, and probable is not the same as what you meant. A vague request is not a small quality tax, it is an invitation for the model to invent the missing ninety percent confidently and build a coherent thing around a guess you never approved. A spec removes the invitation. It pins what the thing must do, what must be true when it is done, and what counts as broken, so the model has nothing left to guess about on the parts that matter.

What makes a spec a spec and not a longer prompt

A longer prompt is still a wish, just wordier. A spec pins specific things: what it does and why, the inputs and outputs, the invariants that must always hold, the edge cases, the constraints. The frontier calls the productive version of this handing the model a well-scoped task it can execute, and it is the difference between an agent that does the job and one that does a job. SpecMesh is the disciplined way to capture that, and it is the throughline of your whole practice.

The Field Manual's spec track drills the six parts and invariants in depth. Here, know that the spec is the interface: it is how a Director talks to the machine.

The takeaway: You direct AI with a spec, not a request, because the model fills anything vague with a confident guess. The spec is the interface that pins what must be true, leaving nothing load-bearing to invention.