The graph

Two node types. Five edges. One of them derived.

Decisions rest on assumptions. Assumptions hold, get questioned, or break. Conflicts are computed from scope overlap and opposed direction, never entered by hand, and recomputed on every write.

loading the graph

The schema

Small on purpose. Everything the resolver, the pipeline, and the compiler do is defined in terms of these, and nothing in the model exists that a human cannot point at.

EdgeDirectionDeclared or derivedWhy it exists
governsDecision to ScopedeclaredFour-level scope algebra, most-specific-wins. Load-bearing.
rests_onDecision to Assumptiondeclared or extractedMakes cascade invalidation possible. Many decisions, one assumption.
supersedesDecision to DecisiondeclaredTemporal replacement. Both records survive; the history stays intact.
exceptsDecision to Scopedeclared, with an expiryScoped carve-outs are the most common real pattern. Without this edge every legitimate exception reads as a contradiction and the feed becomes noise.
conflicts_withDecision to Decisionderived onlyThere is no field in the schema for typing one in. A conflict a human can enter is a conflict a human has already resolved.

Statement types decide enforcement

This single field is the precision control. Automated violation detection reaches 91.1% accuracy overall, but 42 percent of its errors land on infrastructure and 26 percent on principle-driven intent. Mentat never auto-enforces either.

TypeAuto-enforcedBehaviour
code_inferableyesEligible for hard flags and for blocking.
structuralyesDependency direction and layering. Good accuracy.
infrastructurenoContext only. 42 percent of model errors live here.
intent_orientednoContext only. Never reported as a violation.
processnoHuman-routed. Not checkable from code at all.