TECHNICAL / AI-GUARD
What decides. What executes.
What leaves a trace.
An overview of the documented architecture, its limits and the project’s goals.
Explore the code on GitHub ↗A Rust foundation.
An interface for clarity.
Adapters for practical use.
Documented local architecture.
Docker / Podman, rootless by default.
Provided README: product capabilities, reading actions and events, and exporting, verifying and stopping. The HTTP ingress relay is omitted for clarity; it is separate from the proposed inter-worker application relay.
Provided documentation · 29 October 2026
Provided architecture, sections 2 and 3; correction dated 29 October 2026 in PRODUCTION_READINESS. The worker count illustrates boundaries and is not a demonstrated capacity.
Provided documentation · 29 October 2026The documented local architecture separates the trusted broker, the advisory dashboard and Docker / Podman workers. Rootless is the default mode. This overview does not replace testing the runtime and its configuration.
DOCUMENTED LOCALThe interface explains. The broker decides whether to launch. The runtime enforces execution restrictions.
These roles are not interchangeable. Choosing Rust, keeping a log or using an AI decision does not prove containment.
Provided README: capabilities, security profiles, optional Jev and known limits. Architecture: section 6, action lifecycle and recovery; a documented contract is not execution evidence.
Provided documentation · 29 October 2026The README describes a filtered copy in a session volume, an unprivileged worker, a read-only root filesystem and networking disabled by default. Exports go to a new destination.
Inspect mounts, permissions and restrictions on the chosen engine. The broker, engine and their administrator remain trusted.
The strict, review and observe profiles govern the invocation submitted to the broker. The request and its decision are logged; a denial or an unavailable mandatory audit blocks this workflow.
This decision does not control every internal command of an agent or script individually. Optional bridge networking does not provide application-level filtering.
The SQLite audit is independent of the worker. It distinguishes requests, decisions, observed starts and results. Provider-reported claims remain labeled as such.
The documented Codex/Claude outputs are normalized after the session. A missing value remains unknown. Persistence, recovery and integrations each need their own evidence.
The README describes a Rust client for Jev, disabled by default. It supports decision-making; a deterministic denial cannot become an approval.
Tests against the real service still need to be confirmed. Jev replaces neither the broker nor runtime containment.
Provided README: capabilities, exporting, verifying and stopping, and known limits. Architecture: section 3, separating files and tenants.
Provided documentation · 29 October 2026Two workers for client A.
One for client B.
Choose a route. Test the rule.
Run an exchange to see the decision and its audit trail.
This interaction explains the intended permission model. Its relay is not presented as delivered. It demonstrates neither runtime containment nor the product’s security validation.
The project is open source under Apache-2.0 and remains in development.
This overview distinguishes documented mechanisms from project goals and their validation status. It does not replace current results in the repository.
The working copy, Rust broker, Docker/Podman workers, dashboard, audit and export are described in the README. Check the repository for a version’s availability and limits.
Each system/engine combination, agent integration and failure scenario needs its own reproducible results.
The multi-client registry, quotas, application relay and usage accounting are not announced as delivered. Kubernetes orchestration and the cloud offering still need to be built and validated.
The production-readiness documentation corrects earlier claims of delivered features. Historical tests do not automatically validate the current version. The files docs/engineering/CURRENT_STATE.md and docs/engineering/VALIDATION.md are the progress references identified by the project.