Codex · Chapter II

Writing a brief

A brief is a rail: named steps, named conduits, named holds. The desk will not invent the rest.

A brief is not a prompt. It is a rail. If a step is not written, the desk will not take it. If a hold is not marked, the desk will not wait.

Anatomy

Every brief has four parts:

  1. Trigger — what starts the rail (mail lands, a row changes, a watch begins)
  2. Relays — ordered steps, each bound to one conduit
  3. Holds — steps that require a named seal
  4. Seal — what “done” looks like in the ledger

If you cannot name those four, you are not ready to file.

Language the desk accepts

Write like a night order, not a slogan.

  • “When intake mail arrives, copy the sender into the harbor sheet.”
  • “If the row is marked commercial, hold for Nia.”
  • “Do not send a reply. Park it.”

Avoid “handle this,” “follow up as needed,” and “use your judgment.” Those sentences are how closed loops sneak in.

Holds are not failures

A hold is a designed pause. The queue is supposed to have them. A night with zero holds usually means the brief is pretending the work has no judgment.

Versioning

When you change a brief, the old rail stays in the ledger. Dawn replay uses the version that actually ran. Do not edit history to make the floor look cleaner than it was.