Execution Control Stack

ECS

ECS carries the governance state, applicable rule results, and execution-eligibility outcome immediately before the Execution Boundary.

This page explains the public architecture role, relationships, and boundary. It does not disclose implementation mechanisms, interfaces, credentials, or rule packages.

Upstream

Governance state, rule results, execution eligibility

ECS does not receive raw Agent output as its ordinary upstream. Its upstream is the status produced by governance and rule review.

Downstream

Execution Boundary

The downstream point is the Execution Boundary, where permitted action may become real-world effect.

Core role

Keep action controllable before the boundary

ECS holds the execution-control position that ensures the action remains governed before crossing into execution.

Output

Allow, Block, Escalate, or hold state

Public outcome categories may include allow, block, escalate, hold, or route to another governance path.

Not responsible for

Not the execution layer itself

ECS is not the Execution Layer. ECS governs whether action may proceed; the Execution Layer is where permitted action takes effect.