VEX is a governed execution architecture for autonomous AI systems.
This repository is the public entry point for the protocol. The primary implementation repository is private while the system remains under active security hardening, partner testing, and filing discipline.
VEX is designed around a simple premise: model output should not directly become execution authority for sensitive actions.
Instead, VEX is intended to ensure that important execution paths remain subject to explicit boundary, authority, and evidence checks.
At a high level:
- model output is not execution authority
- sensitive execution should not be structurally reachable without governance
- identity, evidence, and execution context should remain cryptographically coherent
This repository gives grant reviewers, research partners, design partners, and technical evaluators a clean public surface to:
- understand what VEX is
- understand the problem VEX is designed to solve
- understand what is public versus private
- request access to the main implementation repository when appropriate
VEX sits between model output and privileged action.
Instead of treating raw model output as execution authority, VEX translates or binds proposed actions into governed representations, checks admissibility, and then either:
- permits a constrained execution path, or
- fail-closes the request
At a high level, the architecture is organized around:
- execution boundaries
- authority and continuation controls
- evidence and custody preservation
- hardware-rooted provenance
- policy-aware escalation and replay
This public repository contains:
- protocol and architecture overview material
- access and evaluation guidance
- non-sensitive project context
This public repository does not contain:
- the full production implementation
- sensitive internal test harnesses
- private deployment or operator configuration
- the current private codebase
VEX is under active development and live integration testing.
The implementation remains private while we continue to:
- harden the system
- complete partner and operator testing
- tighten the protocol surface
- manage filing and disclosure timing around the core architecture
More detail:
If you were directed here from a grant application, diligence process, partnership conversation, or technical introduction and need access to the main repository, please email:
Please include:
- your name
- your organization
- your role
- why you are requesting access
- whether you are evaluating for grants, research, partnership, diligence, or technical review
- whether read-only access is sufficient
Additional guidance is available in ACCESS.md.
If you need to report a security issue or sensitive concern, please use the process in SECURITY.md rather than opening a public issue or sharing sensitive details publicly.
For legitimate evaluation, grant, research, or partnership access, contact:
This repository is shared as a public project overview. Unless otherwise stated, all rights are reserved. See LICENSE.md.