decision procedures shipped as executable artifacts

Everybody has decision templates: how a group picks among options, who may act for whom, how a bridge between two groups gets authorised. Those templates usually live in prose, and prose drifts. Two implementations of "the same" rule diverge in silence, and the divergence is discovered by whoever loses an argument to it.

The tension is that a template has to be readable by people to be legitimate and executable by machines to be enforced. Pick one and you inherit the other's failure — words nobody enforces, or logic nobody can audit.

The decision is to make the template an artifact. Each default is a typed object with a fixed identity, registered in the shared catalog at genesis; spawning an instance means pointing at that identity rather than copying its text. A handful of defaults were registered: a decision anchor that holds the choice, a verifier that watches and objects, a migration role that executes movement, a negotiation role for agreements between worlds, a deliberation role for coordination among delegates. Each is declared an example and not a rule, in the record's own words — anyone may write their own in any language and register it.

The cost falls on the registry, which must stay deliberately ignorant: it records a type without ever parsing it, or the shared base becomes an arbiter of whose code counts as legitimate. What it proves is that executable type definitions were treated as a primitive designed to preserve neutrality, not as a convenience.