Skip to content
Octopus Research Institute
Status: ExperimentalReference implementation

Governed Execution Boundary (reference implementation)

A reference implementation of a single policy-enforcing execution boundary with human approval and evidence capture.

Description

Accompanies the governed-agent-systems programme. Provided as a reference for research and discussion, not as a production-hardened library.

Highlights

  • Routes every agent action through one policy-enforcing point
  • Requires human approval where policy demands it
  • Captures an evidence trail for each action passing the boundary
  • Reference implementation, Apache-2.0, release 0.2.0
  • Companion code to the governed-agent-systems programme

The Governed Execution Boundary is a reference implementation of a single control point placed in front of an autonomous agent's actions. Rather than trusting a model to police its own outputs, it makes every action pass through one place that enforces policy, pauses for human approval where that is required, and records what happened. Because the boundary is singular and explicit, it is auditable: there is exactly one place to reason about what an agent is permitted to do, and exactly one place that produces the record of what it did.

How it works

Conceptually the boundary separates proposing from disposing. The model proposes an action; a sovereign predicate at the boundary decides whether that action proceeds, is escalated to a human, or is refused — and either way the decision and its context are captured as evidence. This is the same governance gene the family applies elsewhere: the model proposes, a sovereign predicate disposes, and everything leaves an evidence trail. The value is architectural rather than algorithmic — the design keeps the enforcement surface small and inspectable instead of scattering checks through agent logic.

Why it matters

It exists to support the governed-agent-systems research programme: a concrete, readable substrate for studying how a single approvable, evidence-producing boundary behaves in practice, and for grounding discussion in something runnable. It is deliberately experimental — interfaces may change without notice, and it has had no independent security audit — so it is intended for research and discussion rather than production use. Anyone considering it beyond that setting should commission independent review first.

Limitations

  • Experimental; interfaces may change without notice.
  • Not security-audited; do not deploy in production without independent review.

Security status

No independent security audit has been performed.

Related research