ADR-0087 exemption (no-migration-prescription): Nothing authorable is renamed, retired or re-typed: no `packages/spec` key changes its name, its type or its optionality, no stored shape moves, and every flow, node and start-node `config` that parses today parses byte-identically after this change — the start node's `config` is an OPEN record (ADR-0018), so the new `organization` key is an addition to a slot that already accepts anything. What narrows is the BIND-TIME accept set: a `schedule` or `time_relative` flow that declares no `organization` is no longer armed. The remedy is a value that only the deployment holds — a `sys_organization.id`, minted at runtime — so there is no authored artifact and no stored representation a rewrite could act on, and `objectstack migrate meta` has nothing mechanical to prescribe: it cannot know which organization a given sweep belongs to, and inventing one is precisely what the ruling forbids. The refusal names the flow and the key, which is the migration instruction, delivered where the deployment can act on it.