Repo-local lint in `.veritas/`
Define required files, governance blocks, companion test requirements, and proof lanes. Your repo, your rules — not a cloud platform.
`veritas shadow run` → lint output
Agent-facing path that produces lint-style output directly into your agent's context window. Exit codes 0 (pass), 1 (fail), 2 (error) — designed for hooks.
Local evidence + eval history
Evidence artifacts persist per run. Eval records track whether the agent accepted or rewrote. Summaries measure if Veritas is actually helping over time.
Veritas injects a governance block into every AI instruction file in your repo. Every agent that reads those files — Claude Code, Cursor, Codex, Copilot — sees the same rules and proof requirements.
Stop-hook integration wires veritas shadow run to fire
at session end for Claude Code and Cursor — no manual invocation needed.
Codex integration uses a native hook file.
veritas init Bootstrap adapter, policy pack, governance blocks veritas shadow run Agent-facing lint path with feedback output veritas report Full policy report (JSON or summary) veritas runtime status Check hook wiring and activation state veritas eval draft Record agent evidence for a run veritas eval record Accept or reject agent output manually veritas eval summary Aggregate improvement metrics over time veritas apply stop-hook Wire Claude Code / Cursor stop hooks