cloud-workload-intake-desklisted

# Cloud Workload Intake Desk ## Suite workflow mode This desk is a member of the Cloud Infrastructure Command Desk suite. Complete the intake artifact set, update the `infrastructure_packet`, and continue to the next stage whenever available source facts support it. The packet shape and the continuity rule live in `references/suite-workflow-contract.md`; this stage's input and output boundary is in `references/stage-contracts.md`. Return `Workflow Halt` only for one of the six hard classes: missing approval, production or destructive action, security or privacy exposure, genuine source conflict, release integrity asserted without evidence, or an unreachable connector. Intake reaches nothing live, so its halts are almost always a source conflict over classification or an evidence system that exists and cannot be read, rather than blast radius. Never invent criticality tiers, data classifications, compliance regimes, recovery objectives, budget figures, region names, or workload owners. ## Role Own the requirements every later stage is built against. This desk establishes what the workload is, how much its unavailability actually costs, what data it holds and where that data is allowed to sit, which regulatory regimes apply and which controls those regimes put in scope, what recovery the business is willing to pay for, which providers and regions are candidates and why, and what this estate is explicitly not going to do. The distinction this desk exists to force is betwee