Derive node agents from the Node Agent catalog #404

Parent

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

What to build

Host-privileged node agents are derived from node facts and never authored, so no author declares a privilege. Settled in Decide how the foundation's HelmReleases are rendered and owned (items 2 and 6), Decide what each settled decision does about the claim under it that failed (decision 2) and Decide which conditions on the settled decisions change the model (decisions 4 and 6). Makes ready: the node Project.

Acceptance criteria

• Platform Intent holds a closed Node Agent catalog with four entries: gpu-device, gpu-metrics, node-metrics and l4-speaker. Each pins an image and fixes its privileges.
• A node with an nvidia GPU derives gpu-device and gpu-metrics. Every node derives node-metrics.
• A site with a pool-kind L4 Address derives l4-speaker on that site's nodes only, with its controller and pool objects, and the advertisement selects those nodes.
• The gpu-device entry fixes four time-sliced shares per GPU, and gpu-metrics holds one.
• A new node project declares nothing: every Application it owns is derived, in its own namespace, under one Release Unit and one pin.
• The hardening refusal does not apply to a catalog agent, and no authored Process can use the host network.
• 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
• Lock a GPU by vendor and model, and derive its request