Refusals free · prohibitions free · authority_effect = 0 · shadow by default · unbound is honest. These are not five safety features. They're five faces of one law — and every departure from the safe ground state costs exactly one human signature.
Build Intuitively · Design Absolutely
The default is safe. Every step away from it is one human signature — and nothing else can move it.
You don't build the interlock. You find the abstraction, and the architecture falls out — the pieces assemble themselves because they were the same piece all along. That's the signature of a right abstraction: not that it solves the problem, but that it makes whole categories of the problem stop existing.
The Lumen "prohibition gap" is the proof. The swarm found the compiler couldn't express "may not X." Under the wrong abstraction, that's a missing feature to go build. Under the right one — prohibition is the ground state, permission is the only thing you say — that entire modality dissolved. Not fixed. Unnecessary.
A design that needs more rules as it grows was built under the wrong abstraction. A design where new problems keep turning out to be the old problem, already solved, was built under the right one. Ours keeps returning to a single point — because there is only one.
That is what "Design Absolutely" actually produces. Every angle of approach — pricing, authoring, enforcement, memory, identity, the moats, the fractal — lands on the same point: the safe state is free and given, and only a human, once, can pay to leave it. When you cannot find a corner where the law fails to hold, you haven't written a lot of rules well. You've found the primitive. And a primitive, met from a new direction, feels like discovery every single time.