Model contracts over a generic transferable vocabulary, not hardcoded goods

To let entities owe each other ANYTHING (materials, labor/compute, information, tech licenses, relationships, protection) in a sim, do not build a subsystem per type. Represent a contract as a list of clauses where each clause DISPATCHES to a primitive that already exists: conserved goods -> ledger transfer; information -> non-conserved mint (telling you does not cost me the knowing); a relationship/tech-license/route -> create a graph edge; a standing pledge -> an edge read on trigger. This adds a contract LAYER, not new physics, so existing invariants (conservation, non-negativity) still bound everything. Key modeling insight: whether a transferable is conserved determines the primitive — materials transfer, information mints. Breach detection falls out naturally: only an owed CONSERVED stock can fail to deliver (obligor lacks it), which then feeds the existing trust/betrayal machinery. Second pattern that saved us: when wiring emergent behavior that mutates shared state (auto-minting contracts when agents ally), gate it behind an OPT-IN meta flag defaulting OFF, so a large existing test suite stays green and it ships as content a world turns on.