The Control Plane is the enterprise place to state who may request an effect, which effects are in scope, and which approvals must occur before execution.
Agents and applications can call tools, APIs, and workflows with whatever permissions they inherited. A login or an API key does not record whether this exact effect is currently allowed.
Security, platform, and operations leaders who must put an explicit permit/deny step in front of agent or software actions that change records, money, access, or machines.
Hood provides the Control Plane as a HIOP surface. CRUSHIA — HIOP Authority Engine evaluates the requested effect. Hood does not replace the customer's models, agents, or systems of record.
Narwhal binds identity. Meerkat verifies the actor. CRUSHIA evaluates authority. Rain governs execution. Fossil preserves evidence. The Control Plane is where policy and routing for that sequence are administered.
A decision record of what was requested, which identity asked, whether CRUSHIA allowed or denied it, and what was observed if execution proceeded.
Described for evaluation and commercial scoping through START. Feature set, integrations, and environments depend on the applicable plan and written terms.
This page is not a live control-plane deployment, a certified SOC report, or a claim that every integration is active. Production_certified remains false unless a written Hood agreement says otherwise.