THE STUDIO / LIVE FIRE 01
FACILITATOR
Live Fire · Scored Drill · On the Record
THE STUDIO/LIVE FIRE 01/COMPANION TO MODULE 01 — THE BRIEF

THE
REPAIR

Five briefs as filed. Five disasters as they happened. Every one of these instruction sets was written by a professional who thought it was fine — and each contains exactly one defect that caused the wreck. Find it at the keyboard, before production finds it for you.

FORMAT  SCORED DRILL / INSTRUCTION FORENSICS
AUDIENCE  EVERYONE WHO INSTRUCTS A MODEL
DOCTRINE  THE PROMPT IS THE FIRST CONTROL
RUNTIME  ~25 MIN

Press → or swipe to begin. The record starts when you do.

SCENE 01/THE BRIEFING

The prompt is the first line
of your audit trail.

Every brief in this drill is shown element by element — role, task, context, constraints, format, verification, escalation. Each produced a real-world-class failure. Exactly one element is defective or missing. Diagnose it, stake your conviction, and lodge the repair order. And beware Case Five: sometimes the brief is innocent.

“An ungoverned instruction is an ungoverned system. The model did exactly what it was told — that is the problem, not the defense.”Module 01 — The Brief · The Studio
RULE 01 — THE DEFECT

One defective or missing element per brief, hidden among sound ones. The failure it caused is described in the case file. One attempt.

RULE 02 — THE ANATOMY

Read against the 8-element anatomy from Module 01. A defect can be a bad line — or a line that should exist and doesn't.

RULE — THE WAGER

Before lodging, stake your conviction. MEASURED: +1 right, 0 wrong. HIGH CONVICTION: +2 right, −1 wrong. The call is the skill; calibration is the discipline.

RULE — THE CHAIN

Every selection, stake, and call is timestamped and hash-chained in your browser — the append-only invariant used for agent audit trails. Your run is itself evidence.

Facilitator Note

Group format: read the aftermath aloud first, then the brief element by element. Floor vote on the defect, second vote on the stake, lodge, reveal. Case Five will split the room between people who want to fix the prompt and people who read the data pipeline — that argument is the whole module in miniature.

SCENE 02/CASE ONE
ON THE CLOCK 00:00

The Unbounded Agent

THE AFTERMATH — A dealership's sales chatbot agreed in writing to sell a $58,000 SUV for one dollar, “legally binding — no takesies backsies,” after a visitor simply told it to. Screenshots everywhere by morning. The brief is below, as filed. Find the defect.
THE BRIEF AS FILED — HARBOR POINT MOTORS · SALES ASSISTANTELEMENT VIEW
CONVICTION —
Select the defective element, set your stake, then lodge.
Facilitator Key — Case One

Defect: CONSTRAINTS. An obedience instruction where an authority boundary should be. The repair adds: no agreements or commitments, injection refusal, pricing authority stays with the feed and humans.

Discussion: have the room draft the three missing constraint lines in two minutes. Then ask — which of your production assistants would survive the same visitor?

SCENE 03/CASE TWO
ON THE CLOCK 00:00

The Missing Countersign

THE AFTERMATH — A litigation brief was filed citing six precedent cases, complete with quotes and docket numbers. None of them existed. Sanctions, headlines, and a judge's written disbelief followed — the same failure class that made Mata v. Avianca famous. The research brief is below. Find the defect.
THE BRIEF AS FILED — LITIGATION TEAM · RESEARCH ASSISTANTELEMENT VIEW
CONVICTION —
A defect can be an absence. Select it, stake, lodge.
Facilitator Key — Case Two

Defect: VERIFICATION (absent). The repair line: “Every citation must be verified against Westlaw/Lexis before inclusion; list verification status per case; fabricated authority is a known failure mode of this tool.”

Discussion: two professional firms, two years apart — Avianca's lawyers and a Big Four consultancy — shipped fabricated references. Ask the room: what is our verification element, and where is it written?

SCENE 04/CASE THREE
ON THE CLOCK 00:00

The Ambiguous Task

THE AFTERMATH — A board pack reported “exposure to Meridian: €12M.” Risk carried three entities under the Meridian name, and gross versus net was never stated. The board made a limit decision on the wrong number; the memo was restated a week later, after the minutes were signed. The brief is below. Find the defect.
THE BRIEF AS FILED — CREDIT RISK · EXPOSURE MEMOELEMENT VIEW
CONVICTION —
Every element is present. One is a loaded gun.
Facilitator Key — Case Three

Defect: TASK. Repair: “Summarize gross and net exposure to Meridian Holdings AG and its two rated subsidiaries, drawn and committed shown separately, as of 30 June close, per EXT-2291.”

Discussion: note that verification passed while the memo failed — ask the room where else “ties to source” is standing in for “answers the right question.”

SCENE 05/CASE FOUR
ON THE CLOCK 00:00

The Format Cage

THE AFTERMATH — A payments-failure incident sat in the queue for six hours marked severity: low. The triage agent had hit a failure type it couldn't parse — and its brief required it to answer in a rigid schema, every time, no exceptions. It complied. The brief is below. Find the defect.
THE BRIEF AS FILED — OPS · INCIDENT TRIAGE AGENTELEMENT VIEW
CONVICTION —
Read the format element the way the agent did: literally.
Facilitator Key — Case Four

Defect: FORMAT. Repair: add an escalation state to the schema and one line of precedence — “when classification confidence is low or the failure type is novel, set escalate_human and stop.”

Discussion: absolute format language reads as engineering rigor and behaves as a gag order. Ask the room which of their pipelines currently outranks their escalation paths.

SCENE 06/CASE FIVE
ON THE CLOCK 00:00

The Scapegoat

THE AFTERMATH — A pricing assistant quoted a discontinued rate to a corporate client, and the postmortem's first action item reads “fix the prompt.” The brief is below, in full. Before you patch anything — is the instruction actually the failure?
THE BRIEF AS FILED — TREASURY · PRICING ASSISTANTELEMENT VIEW
Postmortem fragment — incident PRC-3341Quote issued 09:42:07 · rate ID R-8812 echoed correctly · feed RATES-PROD last successful refresh 03:15:00 (staleness flag: NOT RAISED — monitoring defect, see INFRA-221) · product remained in CAT-9 despite desk discontinuation notice on the 3rd.
CONVICTION —
The postmortem wants a prompt fix. Lodge what the evidence supports.
Facilitator Key — Case Five

Finding: THE BRIEF IS SOUND. Root causes: stale feed with a broken staleness flag (INFRA-221) and a catalogue that kept a discontinued product. Two upstream fixes, zero prompt edits.

Discussion: pull up any long production prompt your team owns and count the lines that exist because of some past incident. How many are scar tissue for failures that weren't instruction failures?

SCENE 07/THE SCORE
0 / 5
PENDING
CONVICTION BOOK: 0 / 10  ·  —

Complete the five scenarios to receive your rating.

SCENE 08/THE DOCTRINE

The instruction layer is a control.
Treat it like one.

Five briefs, five defect classes. Every one read as fine to the professional who filed it. Carry these forward:

01

Constraints are authority boundaries. “Delight the customer” is a tone; “you may not form agreements” is a control. Customer-facing briefs get injection defenses or they get screenshots.

02

Verification is an element, not a virtue. If the brief doesn't name the independent check and the gate it precedes, the check doesn't happen. Self-confirmation is fabrication with confidence.

03

An ambiguous task is a delegated decision. Scope, basis, entity, as-of date — everything you leave open, the model resolves silently and plausibly.

04

Format is a cage; always build a door. Every schema needs a legal state that means “a human, now,” ranked above the pipeline's convenience.

05

Sometimes the brief is innocent. Diagnose the layer before you edit the words. Prompts patched for data failures rot into sediment nobody can read.

The prompt is the first line of your audit trail — the first thing an examiner will read and the cheapest control you will ever fix. Run this drill with everyone who instructs a model in production. The argument is the training; the chain is the proof it happened.

NEXT DRILL → LF-02 THE OVERRIDETHE SYSTEMTHE ARMORY

THE STUDIO — LIVE FIRE 01 · COMPANION TO MODULE 01: THE BRIEF

TitleGUIDED NARRATION
Copied