Veracto Documentation
Product documentation for a policy-driven agent runtime in development.
Documentation in progress. Veracto is under active development. This site describes the current product direction and design constraints, not a promise that every capability is available today.
Veracto is being designed as a policy-driven, multi-tenant agent runtime. Its target is simple to state: a person asks for work in a conversational interface, the system uses only authorized capabilities, and it returns a result whose limits and evidence are clear.
Read this site correctly
This first documentation set deliberately distinguishes three kinds of statements:
| Label | Meaning |
|---|---|
| Current | Present in the canonical repository or supported by recorded evidence. |
| Proposed | A selected product or architecture direction that still needs implementation and release evidence. |
| Unknown | Important but unresolved; it is not presented as a product promise. |
The current repository release-readiness verdict is NO-GO. Veracto is not described here as an already available production service.
Start here
- What Veracto is
- Architecture in one page
- Trust and control principles
- Current project status
- How documentation moves from Notion to this site
Why this documentation exists now
A documentation system should mature alongside the product rather than appear after launch. This site establishes a versioned, reviewable place for product language, system boundaries, status, and future reference material.
It contains only deliberately selected material. Internal runbooks, credentials, operational addresses, unreviewed research, and raw Notion pages do not belong in the published output.