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.
Shaping Frame uses three structured output formats — the dogana block, the tracking snapshot, and the pre-write gate — each with a defined schema and purpose. This page is a quick reference for all three. The inline tagging system is also documented here, since tags feed into these formats.
Dogana Block (Level 2 checkpoint)
The dogana block is emitted at checkpoint intensity Level 2: when AI, MP, or EXT material is crossing a structural threshold and becoming a premise, constraint, naming decision, specification input, or architecture element.
Dogana:
- Element:
- Current state:
- Flag:
- Why it is rising:
- Risk:
- Decision needed:
Field Reference
| Field | Description |
|---|
| Element | The specific proposal, assumption, or claim being evaluated — one line |
| Current state | Spark / Candidate / Tracked — plus the applicable flag if one is set |
| Flag | Quarantined / Contaminated / Needs verification — leave blank if none applies |
| Why it is rising | The specific actions that caused this element’s weight to increase (e.g., cited multiple times, reused as a premise, entered a draft) |
| Risk | What concretely happens if this element advances to the next threshold without OP vetting |
| Decision needed | The exact question OP must answer before the element can proceed |
Example
Dogana:
- Element: 30-second default timeout
- Current state: Candidate
- Flag: Needs verification
- Why it is rising: it is being reused as an architectural constraint across
three spec sections without explicit OP approval
- Risk: an unverified model assumption becomes part of the specification and
propagates into downstream implementation decisions
- Decision needed: verify the timeout against DSK (current config) or explicitly
approve it as a fixed constraint before it enters the spec
Active Tracking Snapshot
The snapshot is emitted before responding to content whenever a surface trigger fires. It gives OP a compact view of every element currently in motion — everything that has not yet been crystallized or rejected.
Active tracking:
- [element] | source | state | next threshold | decision needed?
...
No active tracking: —
Candidate, Tracked, Quarantined, or Needs verification state, write No active tracking: — and continue.
Field Reference
| Field | Description |
|---|
| element | One-line description of the proposal, constraint, or hypothesis being tracked |
| source | EXT / AI / MP / DSK — omit if the source does not change how the element is weighted |
| state | Candidate · Tracked · Quarantined · Needs verification — do not list Crystallized or Rejected, as those are closed states |
| next threshold | The nearest crossing from the threshold vocabulary (see below) |
| decision needed? | yes or no — if yes, state what decision is required before the element can advance |
proposal → premise · premise → constraint · constraint → decision · decision → artifact
draft → spec · provisional phrase → naming · local compromise → architecture
AI/MP/EXT → implicit OP · factual hypothesis → technical foundation
Example
Active tracking:
- separate auth module | AI | Tracked | local compromise → architecture | yes: OP confirm before opening spec
- DB schema v2 | EXT | Candidate | proposal → premise | no
- default timeout 30s | MP | Quarantined | factual hypothesis → technical foundation | yes: verify with DSK before using as constraint
Pre-Write Gate
The pre-write gate is a special case of the checkpoint. It fires before persisting structural artifacts: modifying files, creating specifications, fixing rules, or writing reusable documents. It is not the center of the skill — the skill must operate during shaping, ideation, and review with or without any disk write as a trigger.
Target:
Crystallized:
In motion (Tracked / Candidate):
Quarantined / Needs verification:
Decision needed:
Field Reference
| Field | Description |
|---|
| Target | The artifact about to be written — file path, spec name, rule set, etc. |
| Crystallized | All elements that OP has explicitly approved and that are safe to persist |
| In motion | Elements still in Tracked or Candidate state — not yet decided |
| Quarantined / Needs verification | Elements flagged as unsafe for structural output or awaiting verification |
| Decision needed | The specific OP decision(s) required before the write can proceed |
Outcomes
| Condition | Outcome |
|---|
All relevant elements are Crystallized | Proceed with the write |
| Mixed elements, but none structural | Emit a compact dossier noting what is in motion; proceed if OP agrees |
| AI / MP / EXT unvetted in architecture, rules, or spec | Stop. Surface the conflict; do not write until OP decides |
| Unverified technical facts grounding decisions | Flag as Needs verification; freeze the element until verified |
| Conversational residue in reusable output | Decontaminate before writing |
Example
Target: auth-service/spec.md
Crystallized: JWT for session tokens (OP decision), stateless architecture (OP decision)
In motion (Tracked / Candidate): refresh token rotation strategy (AI, Tracked)
Quarantined / Needs verification: 15-minute token expiry (MP, Needs verification — assumed convention, not verified against requirements)
Decision needed: (1) confirm or replace refresh token rotation strategy before it enters the spec; (2) verify token expiry against documented requirements or approve as explicit constraint
Inline tags are applied at checkpoint intensity Level 1 — when the source of a claim changes how a sentence should be read, but a full dogana block is not yet warranted. Tag only when the tag changes the weight of the output. Do not tag every sentence. Do not tag OP.
| Tag | Meaning | Example usage |
|---|
[AI] | In-session generated proposal | [AI] one option is to split the module into two services |
[MP] | Model prior / general assumption / training pattern | [MP] this is a general convention, not verified in your setup |
[EXT] | External material brought by OP, not yet crystallized | [EXT] per the imported spec, the limit is 100 requests per second |
[DSK] | State read from disk, filesystem, MCP, or tool | [DSK] current config sets timeout to 30s |
[~] | Mixed or uncertain provenance | [~] this may combine session proposals and prior training context |