T3

The playbook

The rules go in before the first word comes out.

For twenty years T3 has run content for banks, exchanges, and trading platforms, where a wrong number is a real problem. When agents arrived, we did not change the method. We wrote it down, so a model can follow it and a person can check it. Six beliefs it runs on.

  1. 01

    Start with the review, not the draft.

    In financial content the queue forms at review, not at the keyboard. So before anyone drafts, we write down what review is looking for: voice, banned terms, approved sources, disclosures. Every draft is checked against that list before a person reads it. The reviewer gets a clean draft and a log of what was caught.

    Write down what review is looking for, and the drafts start clearing it.
  2. 02

    Treat compliance as the foundation, not the obstacle.

    Your disclosure rules are constraints, not a step at the end. A banned term is a hard stop. A dead source is a hard stop. What reaches your compliance officer clears the mechanical bar first, so their time goes to judgment, not cleanup. Same reviewers. Same standards. A week's production, done in an afternoon.

    Compliance is not the bottleneck. It is the foundation the speed stands on.
  3. 03

    Match the voice before you match the tool.

    Which model you run matters less than whether it has read your voice file. Every client's voice, banned terms, and approved sources live in that client's own files. Before a draft is final, it is audited against them again. Our own voice never touches your work.

    The method is ours. The voice, the sources, and the rules are yours.
  4. 04

    Publish by hand, and log every run from the first one.

    The first pieces run with a person as the operator. Every run writes a log: what the checks caught, what was sent back, and why. Those logs are where the rules come from. A framing that slipped through becomes a trip wire with a date and a reason. Automation earns its place one logged run at a time.

    If the send-backs are not trending down, you are producing drafts and hoping.
  5. 05

    Codify the method. Interfaces change.

    The method is plain text: files a person can read and any model can follow. What is specific to a tool is a footnote, not a fork. Models will change, and the tools around them will change faster. What your organization knows should outlast every one of them.

    You don't write three recipes. You write one recipe and a footnote.
  6. 06

    The system drafts. A person publishes.

    Every deliverable arrives as a draft plus a log of what was checked. A named person reads both and decides. The upload, the send: that is their hand, every time, and nothing in the pipeline can do it for them. Because publishing is the one act you cannot take back.

    People own every call that carries risk. Agents carry the volume.

Four phases, in order.

  1. 01

    Encode.

    Write the rules down before anyone drafts.

  2. 02

    Publish.

    Run the first pieces by hand, and log every run from the first one.

  3. 03

    Codify.

    Turn what the logs caught into rules, each with a date and a reason.

  4. 04

    Automate.

    Make what a script can check a hard gate. Judgment stays with a person.

How to run them: the operator guide

Let’s get to work