Two Episodes
The previous lesson argued that the production queue should be a message thread in a system people already read, and it ranked its reasons. The thread carried exactly two episodes. On 2026-08-01 production moved into a delegation engine that belongs to the workshop, and the thread went back to what it had always been for. That makes this a rare chance to watch a well-argued decision age in the open: which reasons held, which one expired, and what the expiry looked like from inside.
The Ledger, Run Again
"The handoff already exists." This was the top reason, and it is the one that expired — without ever becoming false on its own terms. It said: do not build a second delivery mechanism beside one people already read. By August the family had the same delegation engine running in two other workshops, working sessions already started from its launch tickets, and its core was about to become a shared kit. Adopting it was no longer building a second anything. It was joining the mechanism that had become the one people read. The principle held; the inventory it was reasoning about changed.
"The thread becomes the production trail." Replaced by something purpose-built. Every job now carries an append-only log of its stages, each stamped with the session that did it; the run's own rejection log holds the verdicts; and when the job lands, the engine writes one history row back to the shared message system. A thread is a good trail for a conversation. A production needs a trail with structure — which stage, which brain, which machine, in what order — and a thread has nowhere to put those.
"Zero schema change." Still true, and still why the thread was right for the first two episodes. A decision can be correct at one size and wrong at the next without any of its reasons ever having been wrong.
What the Thread Could Not Hold
The warning in the previous lesson named volume as the limit. Volume is not what ended it; a few episodes a week is still low throughput. What ended it was shape. A delegation needs things a thread has no field for: a claim, so two sessions on two machines do not take the same job; a lease, so two landings do not race each other into the repository; a review ledger that verification can read, so a run whose script review had not closed before the synthesis stage was first recorded done is refused mechanically; and a brief committed where every machine can open it. Each of those can be imitated by convention in a thread. Conventions are precisely what a busy week forgets.
The Caller Got Smaller
The move had a side effect on the other side of the seam, and it is the best evidence that the seam was designed well. When the queue moved, the calling side's endpoint, its request-writing code, and its one-line modal were all deleted. What remained is a link: about thirty lines that build a URL carrying the pointer's kind, its identifier, and a display title, and open the workshop's compose screen — where the one line of why is now written. The caller used to write a message. Now it writes nothing, anywhere. The prohibition from the first lesson of this track held through a change of transport without anyone having to defend it, because it had been aimed at the caller from the start.