Skip to content
C.W.K.
Stream
Lesson 02 of 04 · published

The Plan Gate Decides the Shape, Not the Schedule

~12 min · process, planning, collaboration, design

Level 0Wet Clay
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

Where the Gate Sits

The plan gate is not the first thing in a run, and putting it first is the most common way to make it useless. Before it comes a survey stage: read the anchors, measure the neighborhood, check what the topic actually looks like today rather than what memory says. Only then does the gate open, because a plan proposed without that survey is a guess dressed as a decision, and the person approving it has nothing to push against.

After the gate, the run is autonomous until it reports. That asymmetry is deliberate. The expensive conversation happens once, at the point where changing course is nearly free, and then the work proceeds without interruption.

What the Gate Has to Decide

A gate that asks "does this look okay?" produces "looks good" and protects nothing. What makes it real is an explicit list of the decisions that are expensive to reverse. In this workshop that list is: the identifier the work will live under, the kind of thing being made, the angle — the reason it is worth making at all — the structural breakdown and its size, the density per unit, the voice, the placement in whatever catalog or index the result has to appear in, the prerequisites, the difficulty, and the open trade-offs the author cannot resolve alone.

Notice what is absent: no resourcing, no schedule, no estimate of how long the author will take. The only hours the gate names are the reader's, because density is part of shape. Those other questions are real and they belong somewhere else. The gate is about shape, and shape is the thing that cannot be repaired afterward without redoing the work.

The Trade-Offs Section Is the Load-Bearing One

The list above is mostly things the author can propose confidently. The last item is different: it is the author saying "here are the calls I should not make alone." A gate without that section degrades into a presentation, and a presentation gets approved.

The useful form is a decision with a recommendation attached, not an open question. "I plan to redact the numbers because they teach nothing; say so if you would rather match the sibling that publishes them" gives the approver something to disagree with in one word. "How should we handle the numbers?" hands the work back.

The Gate Is a Stage, So It Gets Logged

What was approved, by whom, and on what basis becomes a record at the moment it happens — not a sentence in a final report written hours later. Three separate runs in this workshop's history reached the end and discovered the gate had never been recorded, because the session treated it as a conversation rather than as a stage boundary. The work was fine; the evidence that it had been agreed was missing.

A gate whose output is "approved" has not done anything. Its output should be a short list of decisions, each of which could have gone the other way, and at least one of which the author flagged as not theirs to make. If nothing in the plan could have been decided differently, you did not hold a gate — you held an announcement.

Code

The gate's required fields, and the shape of a good trade-off item·text
PLAN GATE - present all of these, then wait

  identifier        what the work will be called and live under
  kind              which of the available shapes this is
  angle             why this is worth making; the one-sentence thesis
  structure         the breakdown, its size, and what anchors the size
  density           how heavy each unit is, against a measured floor
  voice             register, and any per-project conventions measured
                    rather than assumed
  placement         where it appears in the catalog / index / registry
  prerequisites     what a consumer needs first
  difficulty        the honest label
  trade-offs        the calls the author should not make alone

GOOD trade-off item (a decision + a recommendation):
  "Numbers and addresses: my default is to redact - they teach
   nothing here. Say the word if you'd rather match the sibling
   that publishes them."

BAD trade-off item (a question):
  "How should we handle numbers and addresses?"
  -> hands the work back, and will be answered with 'use your
      judgment', which is where you started.

External links

Exercise

Find the last piece of work you had to redo, and identify the earliest moment at which the decision that caused the redo could have been made differently. Write the plan gate you would have needed at that moment: the four or five fields that had to be agreed, and the one item you should have flagged as not yours to decide. Compare it to what you actually did at that point, which was probably nothing.
Hint
The decision is usually structural and boring — a name, a boundary, where something lives — rather than the interesting technical choice you remember agonizing over. The agonizing choices get discussed precisely because they feel like decisions; the structural ones get made by default because they feel like details.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.