---
schema: "bureau.instrument/v1"
id: bureau-instrument-009
title: "The Red-Thread Minutes"
kind: "Five-Minute Ritual"
version: "1.0"
status: "active"
execution: "sequential"
agent_ready: true
source: "https://thefantasticbureau.com/briefs/do-not-summarize-the-disagreement/"
publisher: "The Bureau of Fantastic Strategy"
language: "en"
---

# The Red-Thread Minutes

> Issued Instrument 009 · Five-Minute Ritual

## Objective

Minutes that preserve the fork in the road instead of reporting that the road was discussed.

## Use when

AI has produced admirably tidy notes from a meeting that contained an actual strategic choice.

## Required inputs

- The meeting transcript or notes.
- The decision at stake.
- The competing claims and their evidence.
- Known unknowns.

## Machine execution rules

- Check the required inputs before starting. Ask only for inputs that are missing.
- Follow the procedure in order. Do not silently skip a step.
- Use supplied evidence and named sources. Label assumptions and inferences.
- Do not invent research, quotations, people, statistics, or certainty.
- Return only the required output, followed by a short list of unresolved questions.
- If the evidence cannot support the requested outcome, stop and state what is missing.

## Procedure

1. Before the summary, open three boxes: settled facts, open questions, and live disagreements.
2. Write each opposing claim in the words its advocate would recognize.
3. For every disagreement, record what would need to be true for each side to win.
4. Name the consequence of choosing either path and the evidence that should reopen the decision.
5. Only now permit the machine to summarize. Gerald may retain the almonds.

## Required output

- Settled facts, open questions, and live disagreements in separate boxes.
- Opposing claims and the conditions under which each could be right.
- Consequences, missing evidence, and a trigger for reopening the decision.

## Bureau voice

- Be precise, accessible, imaginative, and formally understated.
- Use short sentences, concrete nouns, and evidence that can survive daylight.
- Keep one consequential choice visible. Remove hype, consultancy fog, and generic AI phrasing.
- Permit one useful oddity. Do not perform whimsy.
- End with a decision, test, refusal, or next move.

## Completion check

- Every required input was used or explicitly marked missing.
- Every procedure step was completed in order.
- Claims are separated from assumptions.
- The output contains one consequential choice and one next move.
- No invented evidence or decorative certainty was added.

---
The Bureau of Fantastic Strategy · https://thefantasticbureau.com