01
Define what good looks like
Repo Standards
Capture the repo expectations reviewers keep in their heads: required tests, protected files, shared contracts, release checks, security scans, boundaries, and authority rules.
code and change readiness made inspectable
Define what good looks like for your repo. Veritas checks each change against those standards, gives the agent just-in-time guidance while it works, and produces a readiness report that says what passed, what failed, what evidence is stale, and whether the change has enough fresh evidence to merge with reduced human review. It is not a code-review bot; the repo owns the standards and people keep authority over merge risk.
$ npx veritas readiness --working-tree
veritas 0.4.0 — readiness
repo map: loaded
repo standards: loaded
PASS evidence-check: npm run verify
PASS repo-standards-present
PASS ai-instruction-files-synced
PASS merge-readiness: ready
INFO evidence-freshness: current
→ checked against this diff and standards version
→ boundary crossing: none
───────────────────────────────
0 failures 0 warnings
evidence → .veritas/evidence/<run-id>.json
Change boundaries
Fast AI development breaks down when several agents and developers touch the same repo without knowing which work areas are independent, protected, or coupled. Veritas makes those boundaries explicit.
A change that stays inside its work area can move quickly. A boundary crossing asks for the right evidence, owner context, or coordination before it becomes another surprise in review.
This is how teams keep code DRY without turning every shared package, contract, or generated artifact into a manual-review bottleneck.
What Veritas makes possible
Repo Standards
Capture the repo expectations reviewers keep in their heads: required tests, protected files, shared contracts, release checks, security scans, boundaries, and authority rules.
Change Guidance
When an agent or developer touches a risky work area, Veritas supplies the relevant standards before context drift turns into a bad merge.
Readiness Reports
Every change gets a clear answer: what passed, what failed, what evidence is stale, what needs recheck, and why this change can or cannot merge with reduced human review.
Example use case
An agent rewrites an API handler but skips the test that covers it. Instead of surfacing days later in review, Veritas flags the missing evidence at the moment of change — and tells the agent exactly what it needs before the work is submitted.
Reviewers spend their attention inspecting evidence, not rediscovering the standard from a diff.
$ npx veritas readiness --working-tree
veritas 0.4.0 — readiness
repo standards: loaded
PASS change-boundaries: within work area
BLOCK evidence-check: api handler changed, test missing
→ expected: test covering src/api/handler.ts
merge-readiness: blocked — 1 requirement unmet
next action: add the missing test, then re-run
Beyond the gate
A readiness verdict is the start. Veritas also tracks whether your standards are actually helping, recommends adjustments from real run history, and projects every claim into Surface so the evidence is inspectable downstream.
Longitudinal tracking of whether each standard helped, got in the way, or needs adjustment — built from real run evidence.
Data-driven suggestions for tightening, relaxing, or retiring standards, accepted or rejected with authority backing.
Deterministic scoring of whether Veritas guidance actually improves agent outcomes, not just whether checks pass.
Author and manage Surface claims directly from the repo, so readiness state is portable to people, agents, and other systems.
Current CLI
veritas init Bootstrap Repo Standards, Repo Map, and guidance veritas readiness --working-tree Generate a readiness report for the current change veritas explain --file <path> Show just-in-time guidance for a work area veritas attest bootstrap Record authority evidence for protected standards veritas claim list Author and inspect Surface claims for the repo veritas feedback summary Review whether standards are helping across prior runs veritas recommendation list Review data-driven standards recommendations veritas integrations claude-code install Wire agent hooks where supported Veritas is built with Surface. Users don't need to configure Surface — it's the shared shape under the readiness state.