Bricken's boundary logic is a solid reference point. Both approaches throw out the standard computational primitives and let behavior come from structure instead of instructions.

The difference is what you're constraining. Bricken works with containment and distinction. UCE works with conserved quantities — closer to physics than logic. You define constraints over those quantities, and computational behaviors like memory, oscillation, and logic gating fall out of satisfying them simultaneously.

The other big difference is the output. UCE doesn't produce a proof or a reduction — it produces a state-transition graph that compiles directly to hardware. Same rules, different substrates. That's what the Embodiment Mapper layer does.