The conversion's boundary map now lives in this repo rather than outside it, because every implementation that has to build against these definitions can see the repo and nothing else. PORTING.md remains the porting doctrine — how to port; docs/conversion/ is the map — what the boundaries are, which end of each strand owns its contract, and what must be carried forward out of the Python. Three files plus a README carrying the vocabulary, the naming scheme, the one-contract-per-strand rule, contract tiers, write-new/read-old, the identity-beside-the-data rule with its three known instances, and the two reserved-word collisions that are live in shipped code. Deliberately definitional and present-tense. It carries no schedule, no status, no ownership of work and no decision history — those are tracked outside this repo, and anything of that kind appearing here is a defect. Within a boundary you own, correcting a fact or recording a carry-forward is expected. Adding, splitting or re-scoping a plate, changing a strand's definition or contract owner, or defining a cable are decided elsewhere. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>