Deterministic pre-execution gate for AI agents (fail-closed, YAML policy)
Deterministic execution boundary for AI agents. IFC enforcement at the sink. 5 frameworks. 50 attack vectors. Apache 2.0.
Deterministic three-state stop controller. Constraint-first design. Fail-closed.
Core execution boundary engine (decision + proof + ledger)
Small, deterministic control primitives for software systems. Testable, auditable bricks.
Transport-layer application profile for Execution Boundary Core Spec.
Observability profile for Execution Boundary systems — OTel collector topology, semantic conventions, dashboards, alerts
Deterministic execution boundary for AI systems enforcing signed approvals, replay protection, and cryptographic receipts.
Admissibility Rotation Corridor — closed constitutional runtime with visible interrupt geometry
Minimal proof of execution-bound admissibility: no present-state proof at bind, no execution.
Deterministic admissibility layer for interpretation proposals before verdict and execution.
Execution-boundary gate interface. Contamination cases. Adversarial suite. Admissibility at execution time.
Runtime commit gate: no state mutation without a valid DecisionRecord. Execution-boundary AI governance.
Add a description, image, and links to the execution-boundary topic page so that developers can more easily learn about it.
To associate your repository with the execution-boundary topic, visit your repo's landing page and select "manage topics."