Fable
All tasks are written as the same kind of handoff form
The key here is to apply the concept's constraints to specific objects, rather than merely describing an outcome.
As scale and exceptions increased, the methods previously held together by ad hoc coordination began to expose blind spots.
Short-term patches restore surface order, but do not address what the concept truly constrains.
The old craftsman turned to recording conditions, actions, results and the chain of responsibility, so that subsequent adjustments had evidence to rely on.
The chief clerk switched to a unified handoff: incoming items first stated clearly "what needs to be done," and outgoing items delivered only one organized piece of text; the methods in between were left to the clerk's own discretion. This step was troublesome and at first even slowed the schedule; but after a few rounds, rework decreased, and the craftsmen no longer changed rules on a whim. Everyone finally saw that a unified text interface can reduce handoff costs between tasks, but quality constraints, evidence, and tool boundaries still need to be accepted separately.
Unified handoff reduced interface friction, but each type of task still kept its own quality checks.
The same sheet of paper could be sent for rewriting, classification, excerpting or answering, and with fewer counters, the flow became faster instead. From then on, much text work could first be collected into one kind of input and then emitted as one kind of output, with the difficult parts left to the craft in the middle.