Tools, grouped by
what you came to do

Each one is a plugin to a coding agent, and each runs a deterministic check — no model call at check time. Start where your problem is: the code an agent writes, what an agent is allowed to do, or the outcome you are designing toward.

Verify the code

The SAM v2 gate

Six tools in one lifecycle around one deterministic gate — they run in order, and each hands the next an artifact rather than a claim — and a seventh that draws what any of them produced.

polynvpolygenpolygraphpolygatepolyrunpolyvers
Govern the agent

What an agent is allowed to do

The same substrate pointed at a different question: not “is this call acceptable?” but “can this session ever reach a situation it must never be in?” The argument, the tools and the reading in one place →

Design the outcome

Before anyone writes code

Not a tool — Polytrion

Our digital-twin design platform is a separate line of work, and it is not something you install. It runs as a hosted platform in soft launch, by invitation. See what it does →