Place Infrastructure Intent, the Stable Address and the Move in the compiler's structure #328

Parent

#326

What

Say in docs/architecture.md where each piece #323 specified lives, before #324's slices write any of it:

• Infrastructure Intent: a third reader in read/, its metamodel in model/, its constraints in check/, and how the node contract is generated from it and pinned.
• The Stable Address: which step derives it per named surface, how ${dependency:…} resolves to it, and which adapter renders the estate-scoped ExternalName objects.
• The Move: what composition reads from ClusterState's instances, which step derives the layer-2 move element, and which adapter renders the step Jobs, the move identity and the allow-set rules for both Instances (a move adapter of its own, or a family inside kubernetes).
• The parity table: the oracles the new example and the changed coordinates add.
• The rule ledger: the boundary rows that change, each with its enforcement and a failing fixture, or pending with its ticket.
• emf/docs/architecture.md: the Estate root (0098) and where the new metamodel and constraints sit.

A change to a layer or a dependency rule is Ask first: propose it, get the maintainer's approval, and land it with its ADR.

Blocked by

The audit and plan in this epic's first child.

Done when

Every #324 slice names the directory it writes into, and npm run verify is green with the new rows.