Park a Process #389

Parent

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

What to build

An Application author writes parked: {reason} on a Process of any lifecycle. It stops running, and nothing it owns is pruned. Settled in Decide how the model meets soft scheduling, spread, anti-affinity and parked replicas (item 6) and Decide which conditions on the settled decisions change the model (decision 2).

Acceptance criteria

• A parked Process renders zero replicas, or a suspended CronJob when it is scheduled.
• Its claims, grants, Service and network policy stay rendered.
• It gets no disruption budget and is left out of its Application's switchover readiness.
• It runs every build check, eligibility included.
• An edge from a running Process to a parked provider is allowed.
• Chapter 11 states what parking does to a run in flight (it finishes) and what unparking does (a run starts at once only when a slot fell within the last 300 seconds).
• 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 a scheduled Process