Interpretation Brief¶

Framing artifact — instantiates Context-Bounded Meaning Recovery

Opens an interpretation by fixing what is being read, what question the reading must answer, and who is reading it — before any meaning is claimed.

The Interpretation Brief is the short charter you write before reading, not after. It pins three things that interpretive disputes otherwise let drift: the exact substrate (which version, source, edges, and what is deliberately excluded), the question the reading is actually answering (literal content? intent? function? consequence? legal force?), and the interpreter's own position (who is reading, with what stake, training, and prior commitment). Its distinctive move is sequencing — it commits to object, question, and standpoint while the answer is still unknown, so that when readings later collide, everyone can check whether they are even reading the same thing, for the same purpose, before arguing about what it means. It produces no interpretation itself; it makes every later interpretation accountable to a fixed frame.

Example¶

A retail-analytics team sees weekly active users on a dashboard "drop 12%" and is asked what it means. Before anyone theorizes, they write the brief. Substrate: not "the dashboard" but the specific query, on the v4.2 event schema, for the ISO weeks in question, excluding internal test accounts — because a schema change two weeks earlier had quietly redefined "active." Question scope: they are being asked for a causal reading (did something break, or did behavior change?), not a descriptive one, and explicitly not a forecast. Interpreter position: the analyst writing it has been advocating a churn-reduction project, and says so in the brief, so her priors are on the table rather than smuggled into the reading.

That half-page changes what follows. The "drop" turns out to be partly the schema redefinition — visible only because the substrate was pinned to a version. The causal-vs-descriptive scoping stops the team from over-claiming a behavior change. And the disclosed prior lets a reviewer discount the churn-flavored reading appropriately. The brief settled none of it; it made all of it checkable.

How it works¶

The brief is deliberately thin and front-loaded:

Freeze the substrate. Record the exact object, its version/source, its boundaries, and what is excluded — so the thing being interpreted cannot silently change mid-argument.
Scope the question. Name which kind of meaning is sought — content, intent, function, consequence, significance, or force — because different questions license different frameworks and evidence.
Disclose the position. State who is reading, their stake, competence, and prior commitments, so standpoint is visible rather than laundered into "the obvious reading."
Stop there. The brief does not choose a framework, trace evidence, or reach a reading; it hands a fixed frame to the mechanisms that do.

Tuning parameters¶

Substrate granularity — how precisely the object is fixed (a whole corpus vs. a single versioned artifact). Finer pinning prevents target-drift but can over-narrow a reading that legitimately spans context.
Question breadth — one sharp interpretive question vs. several. Narrow scope keeps the reading accountable; too narrow and you answer the wrong question crisply.
Disclosure depth — how much of the interpreter's stake and priors to surface. More disclosure aids trust and later discounting; past a point it invites performative hedging.
Bindingness — whether the brief is a fixed contract for the reading or a living document revised as the object is understood. Firmer briefs anchor disputes; softer ones adapt but can be gamed.
Ceremony — a scribbled half-page vs. a signed-off document; match it to the stakes of the reading.

When it helps, and when it misleads¶

Its strength is that it kills a whole class of interpretive dispute before it starts — the arguments where two people "read the same thing" but were never reading the same version, answering the same question, or standing in the same place. By forcing object, question, and standpoint into the open, it separates disagreements about evidence from disagreements about framework or values, and it makes an interpreter's inference-ladder inspectable from its bottom rung rather than only at the conclusion.^[1]

Its failure modes are those of any charter. A brief can create false rigor — a crisp scope that quietly excludes the reading that actually matters, or a pinned substrate that amputates the context needed to read it. It can be run backwards: written after the interpretation to dress a foregone conclusion in procedural neutrality. And an over-ceremonial brief adds drag to readings whose stakes never warranted it. The discipline that guards against this is to write it first and cheap, to revisit the scope when the substrate resists it, and to treat the brief as the thing later evidence is allowed to overturn — not a commitment that outranks what the substrate turns out to say.

How it implements the components¶

The Interpretation Brief realizes the setup side of the archetype — the commitments made before any reading, not the reading itself:

representational_substrate_record — its first act: fixing the object, version, source, boundaries, and exclusions being interpreted.
interpretive_question_scope — names which kind of meaning the reading pursues, so later work knows what would count as an answer.
interpreter_position_disclosure — puts the reader's stake, competence, and priors on the record instead of inside the conclusion.

It does not choose or justify the reading framework (framework_selection_rule) — that is the Framework Selection Memo; it does not trace claims to marks (evidence_mark_trace, the Evidence-to-Claim Matrix) or generate rival readings (alternative_reading_set, the Alternative Readings Review). The brief only fixes the frame those mechanisms then work inside.

Instantiates: Context-Bounded Meaning Recovery — the brief supplies the fixed substrate, question, and standpoint the rest of the recovery hangs on.
Sibling mechanisms: Framework Selection Memo · Interpretation Red Team · Evidence-to-Claim Matrix · Close Reading Table · Context Reconstruction Worksheet · Alternative Readings Review · Pragmatic Force Walkthrough · Precedent Comparison Table · Stakeholder Meaning Check · Translation Backcheck · Ambiguity Register · Glossary or Code Key · Hermeneutic Loop Log

Notes¶

The brief is an input, not a verdict — it is the one artifact every other mechanism in the archetype reads first, which is exactly why writing it after the fact quietly corrupts all of them. Keep it upstream, and let evidence overturn it rather than letting it pre-empt evidence.

References¶

[1] The ladder of inference (Chris Argyris) describes how people climb from raw observation through selected data and added meaning to conclusions and action, usually without noticing the lower rungs. An Interpretation Brief forces the bottom rungs — the substrate and the reader's selections — into view before the climb. ↩