A threshold is the point where material starts behaving like a decision — where an idea shifts from being something under consideration to something that is being acted on. Thresholds are not always announced. They are often crossed gradually and silently, in the gap between “we could do this” and “we are doing this.” Crossing a threshold without operator vetting is the core failure mode Shaping Frame guards against.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/shaping-frame-for-claude/llms.txt
Use this file to discover all available pages before exploring further.
Threshold Vocabulary
These are the crossings the frame watches for:What Each Crossing Looks Like
proposal → premise
You stop asking “should we do this?” and start asking “how do we do this?” — often without noticing. The question has changed, and with it the frame: the proposal is now load-bearing. This is the earliest and most common silent crossing.
premise → constraint
What was an assumption starts ruling out options. Instead of “given X, what could we do?”, the question becomes “this must work with X.” The assumption has gained a veto. No one decided to give it one.
constraint → decision
A narrowing is treated as a final choice. The space of options has been reduced to one, but the reduction was never explicitly made — it accumulated through a series of premises and constraints that were never reviewed together.
decision → artifact
An implicit decision gets encoded in code, a specification, a document, or a configuration. Once it is in an artifact, it becomes much harder to revisit — not because the artifact is authoritative, but because reversing it has real cost.
draft → spec
A working draft that was meant to be exploratory starts being treated as a fixed specification. Other work is aligned to it. It stops being questioned. It becomes the reference point rather than one of the options.
provisional phrase → naming
A placeholder name — chosen for convenience in one part of a conversation — gets used in other contexts, then in output, then everywhere. The name becomes the real name through repetition rather than decision.
local compromise → architecture
A shortcut made to solve a specific problem in one part of the system gets generalized and applied everywhere. A pragmatic concession becomes a structural principle. The original constraint that motivated it is forgotten.
AI/MP/EXT → implicit OP
Claude’s output, a model prior, or an external document starts being treated as operator intent. This is one of the most consequential crossings: a source that does not have decision authority is being treated as if it does. The material is directing the session rather than being evaluated by it.
factual hypothesis → technical foundation
An unverified technical claim — “this library handles that”, “this approach scales to that load”, “this API behaves this way” — becomes load-bearing. Other decisions are built on top of it before it has been checked.
Additional Triggers
Beyond the core vocabulary, the following events also fire the checkpoint:- AI cited multiple times without approval — repeated citation without explicit OP vetting moves material into Tracked state.
- MP used as foundation — a model prior being used to ground a structural decision requires surfacing and Quarantine by default.
- EXT treated as OP — external material being used as if it represents operator intent, rather than as context that OP may or may not endorse.
- OP-historical used as OP-current — prior-session operator statements embedded in imported material being applied to new or structural decisions without reconfirmation.
- A Rejected element resurfaces — a previously discarded proposal re-entering the conversation, whether through inertia, reformulation, or gradual drift.
- A draft becomes a spec — a working draft that was exploratory starts being treated as a fixed specification that other work aligns to and no longer questions.
- A Quarantined element enters structural output — material flagged as unsafe for structural use being incorporated into architecture, specifications, rules, or reusable artifacts without operator vetting.
Anti-Recency Rule
Do not resolve conflicts because a formulation is more recent, more fluid, or said with more confidence. Do not merge incompatible elements through conversational inertia. The last thing said is not the decided thing — it is simply the most recent thing. When two elements conflict:- Make the conflict explicit.
- Assign current weight to each element.
- If a decision is needed to proceed or crystallize, ask OP.
- If not needed immediately, proceed with the assumption marked as Candidate or Tracked.
- Never merge through inertia.