Vectadyne
Vectadyne is not a vector database
Section titled “Vectadyne is not a vector database”It is a governed memory control plane for engineering agents. Evidence from your real engineering activity goes in. A typed, scoped, provenance-bearing memory graph comes out. An agent asks it two questions — what should I know here? and is what I am about to do safe? — and gets back an answer it can cite.
A vector database gives you nearest neighbours. Vectadyne gives you an answer that knows whose memory it is, where it applies, how confident it is, and what happened last time. The retrieval is a means; the governed answer is the product.
Start here
Section titled “Start here”| If you want to | Go to |
|---|---|
| See it work, in any language, in five minutes | Quickstart |
| Understand what you get at each stage of adoption | The adoption ladder |
| Integrate with an SDK | Go · Python · TypeScript |
| Point an existing MCP client at it | Connect an MCP client |
| Know exactly what the API accepts | MCP tools |
The one thing to get right
Section titled “The one thing to get right”Vectadyne is advisory-first. preflight.action and context.assemble return a verdict; they
do not stop your agent mid-run. A block becomes an actual gate in exactly one place — the CI/PR
check you opt into.
That is a statement about action verdicts, and only that. Tenancy, scope, clearance and capability are enforced on the server for every single request: a caller reaching outside its authority is refused, not advised. See Advisory-first — it is the claim most often got wrong, in both directions.