Ships today · npm
Veritas
Merge autonomy for AI-authored code. Turns your repo's standards into evidence-backed readiness reports that agents and reviewers can rely on — with just-in-time guidance while the work happens.
Agents write code, run processes, and make claims faster than anyone can inspect by hand. Kontour shows what was claimed, what supports it, which gates it passed, and what's still uncertain — so people and agents can decide what deserves trust before they act.
What we're building
Pull a finished product off the shelf, or build on the open primitives underneath it. Either way, the trust state stays inspectable by people, agents, and the systems downstream.
Products you can use today
Merge autonomy for AI-authored code. Turns your repo's standards into evidence-backed readiness reports that agents and reviewers can rely on — with just-in-time guidance while the work happens.
Workflow discipline inside the agent tools you already use — Claude Code, Codex, Kiro, GitHub Actions. Durable plans, review, verification, and release evidence that survive compaction and handoffs.
Primitives to build on
One shape for claims, evidence, freshness, policies, and gaps — so the same trust state can be read by a person, an agent, or another system.
Process transparency for required-path work. Shows why work was allowed to advance, gate by gate, with the evidence behind each transition.
The producer side of claims. Turns sources, extractions, candidates, and reviews into Surface-ready claims with provenance attached.
Console sits above the primitives — one place to visualize and manage claim status, process state, proof, queues, decisions, and next actions across every product, without owning their semantics.
The promise
AI can make any output look finished. Kontour shows the work behind it — the claim, the evidence, the required path, the gate decisions, and the gaps — so people and agents can tell what actually holds up before they act on it.
Early access
We're building in public. Drop your email for build updates and an early look — or start a focused design-partner conversation about the workflow you want to make inspectable.
Prefer to talk specifics? Start a design-partner thread →