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.
A deterministic three-state stop controller. Constraint-first design through executable clarity.
Core execution boundary engine (decision + proof + ledger)
Execution boundary for GitHub pull requests that interprets repository mutations before CI enforcement.
Small, deterministic control primitives for software systems. Testable, auditable bricks.
A deterministic admissibility layer for interpretation proposals before verdict and execution.
Admissibility Rotation Corridor — closed constitutional runtime with visible interrupt geometry
Transport-layer application profile for Execution Boundary Core Spec.
Deterministic execution boundary for AI systems enforcing signed approvals, replay protection, and cryptographic receipts.
AI Execution Boundary Standard (AEBS) - Pre-incident reference for execution governance
Observability profile for Execution Boundary systems — OTel collector topology, semantic conventions, dashboards, alerts
Demonstrates how information pre-positioning causes cascading execution failures. Publishes phenomenon + conformance tests. Gate implementation private.
Minimal reference model for separating proposal, authorization, and execution in side-effecting systems.
A minimal Python reference implementation of execution-bound governance: no state mutation unless a signed, scoped, unexpired, unreplayed DecisionRecord authorises the exact commit.
Minimal proof of execution-bound admissibility: no present-state proof at bind, no execution.
Entry point and architectural map for execution boundary research.
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."