Governed execution for agentic systems
Anthesis evaluates consequential agent actions against explicit policy, authority, approvals, capabilities, and evidence requirements at the boundary where a host system invokes it.
The decision becomes meaningful when a tool surface, gateway, credential boundary, downstream validator, or runtime prevents the agent from bypassing it.
Two proof paths
The evaluation and execution paths are deliberately separate so each can make a precise, testable claim.
Runnable now
Run the immutable public Rust evaluator against deterministic declarations and inspect stable decisions, reasons, rules, and aggregate reports.
Reference integration
Inspect a bounded tool-execution harness that normalizes actions, invokes Anthesis, resolves exact approval when required, executes constrained tools, and verifies evidence.
How the components fit
Keeping these responsibilities separate prevents a demonstration harness or runtime from becoming a self-certifying policy authority.
| Component | Responsibility |
|---|---|
| Anthesis | Policy authority, deterministic decisions, approval requirements, capability constraints, evidence semantics, provenance, and public evaluator contracts. |
| Governance Lab | Independent deterministic conformance, scenario packs, reports, and stakeholder walkthroughs. It is not in the runtime critical path. |
| Dubnium | Reproducible runtime, gateway, bounded tools, execution, and runtime evidence. It consumes decisions; it does not define policy authority. |
Integration assurance
The same integration mode can be advisory, moderate, strong, or runtime-enforced depending on which bypass paths remain.
| Enforcement location | Common modes | Required bypass control | Typical assurance |
|---|---|---|---|
| Application | SDK wrapper | Direct clients and raw credentials cannot remain an uncontrolled path. | Advisory to moderate |
| Tool surface | Tool wrapper / invoke, MCP mediation | Raw tools, downstream MCP servers, and service credentials are unavailable or constrained. | Moderate to strong |
| Infrastructure | Gateway / sidecar, capability tokens | Downstream effects are unreachable or reject missing, altered, expired, or out-of-scope grants. | Strong |
| Runtime | Sandboxed runtime | Filesystem, network, process, credentials, and tools are unavailable outside governed paths. | Runtime-enforced when complete |
The governing question: What prevents the agent from producing this effect without crossing Anthesis?
Current status
Public materials distinguish what can be run today, what is a reference integration, and what remains under active development.
Runnable now
Public evaluator acquisition, Governance Lab scenario packs, reconciled catalogs, aggregate reports, and stakeholder walkthroughs.
Reference integration
Dubnium demonstrates exact authorization binding, approval-gated constrained tools, source immutability, evidence sanitization, and manifest verification.
In development
Additional enforcement profiles and stronger live inference-integrity evidence, replay, verification, containment, and recovery.
Trust boundary: Governance Lab demonstrates deterministic contract behavior, not production effect enforcement. The Dubnium demo is a bounded reference integration, not proof that every Anthesis deployment is non-bypassable. Inference-integrity fixtures are not complete live exfiltration prevention.
Learn more
Execute and inspect the deterministic public proof surface.
Follow the Dubnium governed-agent decision, approval, execution, and evidence path.
Review mechanism, threat boundary, bypass assumptions, recommendations, and tradeoffs.
Use bounded trial criteria and evidence expectations rather than broad product claims.
A concise, printable explanation of the product, proof paths, and integration model.
The curated technical narrative, trust model, compositions, and adoption path.
Inspect immutable public evaluator releases and the canonical Anthesis implementation.