Expose a raw surface on a node's own address #392

Parent

Rewrite the spec and the compiler in place, release 1.0.0, and hand over every Project

What to build

An L4 Address may be a node's own address, for a site with no pool. The Application author writes the same exposure; the kind of the address decides the rendering. Settled in Decide what each settled decision does about the claim under it that failed (decision 3). Makes ready: mail.

Acceptance criteria

• A node-kind L4 Address names a node. An exposure on it renders a host port on the Process and derives a hard pin to that node.
• A port and protocol used twice on one node address is refused at build.
• No Application names a node, and a host port is never authored.
• The chapter states how a Process on a node address cuts over, given that a host port cannot hold two copies. If the existing cutover refusal does not cover continuous on a node address, the gap is raised with the maintainer before it is decided here.
• The chapter states the rule and its refusals, with short rationale only, and CONTEXT.md carries each new term in the same pull request.
• A worked example shows it; its resolved artifact and its rendered tree are updated and reviewed by hand, never regenerated in CI.
• Each refusal has a refusal example with its diagnostics file.
• The JSON Schemas and their corpus admit the new shape and refuse a malformed one.
• The behaviour-ledger row lands with its test, and npm run verify passes.

Blocked by

• Cut what the map cut and release package 1.0.0
• Declare L4 Addresses, and expose a raw surface on a pool