prism.

Verification

Configurable quality gates enforced at every stage — not suggested, enforced.

PRISM doesn't trust that code works because it compiled. It verifies that code delivers what the requirement asked for — before planning, after execution, and at every gate in between.

PRISM verification interface showing quality gate results

How verification works

Multi-layer verification that catches problems at the right stage — before they reach production.

Goal-backward verification

The verifier doesn't ask 'did it compile?' — it asks 'did it deliver what the requirement specified?' Every phase is checked against its original goals, not just technical correctness.

Configurable quality gate matrix

Unit tests, integration tests, e2e tests, Playwright, type-checking, linting — configure which gates apply per project. Finalize and deploy are blocked when gates fail. No exceptions.

Plan-level verification loop

Before execution begins, a checker agent reviews every plan against requirements. Plans that don't satisfy the goal are revised. Execution only starts when the plan passes inspection.

Post-execution codebase audit

After execution completes, a verifier agent reviews the actual codebase — not the plan, not the diff, but what the code actually does. Gaps between intent and implementation are caught before merge.

Atomic commit verification

Every task produces an atomic commit. Each change is independently revertable and independently verifiable. No tangled diffs, no 'which commit broke it?' debugging.

Coverage threshold enforcement

Set minimum coverage thresholds per project. PRISM enforces them as hard gates — not aspirational targets in a README that nobody checks.

Three layers of verification

Pre-execution

Plan checker verifies every plan satisfies the requirement before any code is written. Bad plans never reach execution.

During execution

Quality gates run continuously — type-check, lint, tests. Failures halt execution immediately. No accumulation of broken state.

Post-execution

Verifier agent reviews the codebase against phase goals. Not 'did tasks complete?' but 'did the code deliver what was asked for?'

Ship code with proof that it works

Start a 14-day pilot and experience verification that actually catches what matters.

Verification — PRISM