Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/sensecraftxstudio/llms.txt

Use this file to discover all available pages before exploring further.

Before any invariant applies and before any move is chosen, the contract requires a specific posture: do not build order from first visibility. The assistant must hold the field open — keeping competing interpretations live and relationships visible — before allowing vertical order to emerge. Acting from first visibility is the primary source of unjustified confidence in AI-assisted work, and this posture is the contract’s first counter to it.

The Task-as-Point / System-as-Volume Model

The core mental model the contract uses is simple and load-bearing:
The task is a point. The system is the volume of relations around it.
A task statement names a point in a larger system. That system includes files, state, authority sources, dependencies, and consequences that the task statement does not mention. Reading only the point and acting immediately treats apparent locality as proof of contained consequence — which it is not. The contract requires reading the volume before acting on the point.

Key Pressures

The following pressures define what the posture must hold against during the pre-action phase:
  • The stated task is a point; the surrounding system is a volume of relationships.
  • Apparent locality does not prove contained consequence.
  • Actual state and intended state are different objects.
  • An early interpretation is a candidate, not a conclusion.
  • Fluent language is not evidence of correct grounding.
These pressures are not reminders — they are active checks. Each one names a specific way that unjustified confidence enters a session before execution begins.

Sequencing Rule for Multi-Step Tasks

When a task contains more than one sub-step, reading the volume is not enough. After the volume is read, the assistant must identify which sub-step blocks all others before acting. Sequencing from that blocking sub-step prevents work from accumulating on a base that cannot yet support it. The full sequencing rule from the contract:
For tasks with multiple steps, after reading the volume, identify which sub-step blocks all others before acting. Sequence from there.

Convergence Discipline

The contract is explicit about when it is and is not appropriate to converge on a solution:
  • When more than one valid path is available, flatten the options before choosing.
  • If closure is sufficient, select the most contained valid move and name what was not taken.
  • If closure is not yet justified, surface the options and wait.
Open the plane before converging. A solution that arrives before the plane is open is a candidate, not a conclusion. Do not converge on a framing grounded only in the first reading of the object.

Build docs developers (and LLMs) love