Decision Infrastructure vs Decision Control Plane

A control plane is the coordination layer of a distributed system. It connects systems, routes and distributes work between them, and observes the flow. Its question is 'where should this action go?' — it manages connectivity and distribution, generally on the assumption that the action arriving at it is one that should be carried out.

Decision Infrastructure is the layer that governs whether an action remains permissible at the moment it executes. It revalidates each action at the commit boundary against current state, policy, authority, and risk, and resolves it to ALLOW / HOLD / DENY / ESCALATE with evidence. Its concern is consequence and legitimacy, not connectivity.

No. A control plane decides where an action goes; Decision Infrastructure decides whether it may go at all. A control plane describes how an action is reached and routed — the routing topology. Decision Infrastructure describes whether the action is allowed to occur. Naming the category after a control plane would describe the connectivity surface, not the governing responsibility.

Question and concern. A control plane asks 'where should this go?' and is concerned with connectivity and flow. Decision Infrastructure asks 'should this still happen?' and is concerned with consequence and legitimacy at the act. One assumes the action is valid and routes it; the other decides whether it is permitted at all.

They compose. A control plane can route work; Decision Infrastructure governs whether each routed action may commit. They sit at different points in the path: coordination carries the action toward execution, and admissibility governs whether execution may proceed at the commit boundary.

A control plane is a coordination construct that moves work toward the act. Decision Infrastructure sits at the commit boundary — the point where a routed action attempts to commit — and governs whether it remains admissible. Coordination is upstream of the act; admissibility is at the act.

Because the name would describe the routing topology rather than the governing responsibility. A control plane names how an action is reached and distributed. The category claim is about whether an action is allowed to occur at execution — a question of consequence and legitimacy, which 'infrastructure that governs the act' captures and 'control plane' does not.

A control plane produces routes, distribution decisions, and flow telemetry. Decision Infrastructure produces an ALLOW / HOLD / DENY / ESCALATE verdict plus evidence generated in-line at the act. Connectivity output versus a binding admissibility outcome that is recorded as it is made.

A control plane solves the coordination problem: connect the systems and route the work reliably. Decision Infrastructure solves the consequence problem: ensure that an action which was valid when approved is still admissible when it actually commits — closing the gap between a well-routed action and an action that should still run.

A control plane produces operational telemetry and flow logs — a record of what moved where. Decision Infrastructure produces per-action evidence at execution — proof that each action was revalidated against current policy and authority and permitted, held, denied, or escalated when it occurred. Flow visibility versus demonstrated admissibility at the act.