Workflow blueprint
Workspace
Start a new service.
Describe work your team currently does manually. VVDex compiles it, and you run it on a sample before anything else.
Technical detail · the contract, the graph and the tests
Compiled authority graph
How every event moves through the service.
Authority ledger
Split-release architecture
Reads come in. Writes wait for authority.
No business write exists in the intake flow. Every write sits in a separate release flow that runs only with a signed, single-use grant.
The VVDex engine
Connect real accounts. Deploy in steps.
Our own execution engine runs the service: it reads new mail, holds every consequential write for you, and releases each approved write once. Credentials are checked with the vendor, then encrypted; no screen ever shows them again.
Connector library
Every action, governed.
Open-source connectors run inside VVDex, never on someone else's platform. Every action is classified before it can run: reads run on request; writes are held until a person signs the exact parameters, and run once.
Live split-release
Nothing is written until you sign.
Events arriving from the execution plane wait here. Approving releases exactly the writes on the slip, once, through a signed single-use grant.
Every event, every decision
What happened, and who decided.
Every event any service received, with its decision, the person who signed, the outcome and its sealed evidence. Replay runs an event again through the service's current design as a new held event; it never re-uses an old decision.
Agents, tools, memory and control
Every agent, what it did, and what it learned.
Each step inside VVDex is done by a specialist and checked by a reviewer on a second model. Here is every agent and whether it is on, every step it did with its reviewers and evidence, what your approvers kept or changed, the lessons the agents learned from it and where each was used, and the tools they read with. Every change you make here is written to the audit log.
Verifiable evidence
Don’t trust the run. Re-check it.
Every terminal run seals its receipts under one SHA-256 digest. Change any receipt and verification fails, visibly.
People, agents, keys and the record
Every decision has a name on it.
Operators sign in with their own key and role, and every step an agent does names the agent and its reviewers. Every approval, deploy, connection and key change is written to an append-only log where each entry seals the one before it, so a removed or edited entry is detected.