Skip to main content

Versalist Assurance

Compare agent changes before they ship.

Run the skill your agent uses today and the revision you want to ship on the same cases and model. See which cases got worse, then record Ship, Hold or Needs work.

Versalist Challenges page showing workspace navigation and challenge cards.

Versalist works with the coding agents and models your team already uses

  • Claude Code
  • GitHub Copilot
  • Codex
  • Cursor
  • Antigravity
  • OpenCode
  • JetBrains Junie

Plus models from OpenAI, Anthropic and Google.

The problem

A better average can still ship a worse agent.

An overall score can rise while individual cases get worse. A release review shows both versions case by case, so you see the drop before your users do.

Without Versalist

  • Spot checks on a handful of examples
  • One average score that hides what got worse
  • Release calls made in chat, with nothing on record

With Versalist

  • Both versions run on the same test cases
  • A lower dimension score is flagged as a regression
  • Ship, Hold or Needs work, recorded with the review

How it works

From change to decision in three steps.

  1. Define the test

    Turn a real workflow into fixed test cases and a scoring rubric your team agrees on.

  2. Compare versions

    Run both versions on the same cases and model. Read the scores case by case and dimension by dimension.

  3. Decide and ship

    The review owner records Ship, Hold or Needs work, and can export the review.

See a sample comparison

Features

What a release review puts in front of you.

Scores for both versions, the regressions between them, and every decision made on the review.

  • Side-by-side scores

    Scores for both versions, per case and per rubric dimension. A review holds up to 500 case rows and 100 dimensions per run.

  • Regression flags

    A comparable dimension score that drops is marked as a regression.

  • Like-for-like comparisons

    Both runs must share the challenge, skill, rubric and case identifiers. A missing model identifier does not prove the models match.

  • Decisions on record

    Ship, Hold or Needs work, saved with the evidence and the full decision history.

  • Print and export

    Print a review or export it to Markdown for your release notes and sign-off.

  • Shared with your organization

    Share a review with your organization, or create a public link for eligible reviews.

Built for engineers

Check what the runs have in common.

Versalist checks the challenge, skill, rubric and case identifiers before creating a review. Model identifiers are compared when present. Missing model identifiers do not prove a model match.

Review created

Every key field matches, so the review is created.
FieldBaselineCandidateMatch
challenge_id3f9a…3f9a…same
skill_bundle_id8c21…8c21…same
challenge_content_hashe4d0…e4d0…same
rubric_content_hashb07c…b07c…same
cases_content_hash91fa…91fa…same
model_contract_hash6e2b…6e2b…same
agent_model_idmodel-amodel-asame

skill_version2 to 3

the change under review (not part of the key)

Refused

rubric_content_hash differs, so the review is refused.
FieldBaselineCandidateMatch
challenge_id3f9a…3f9a…same
skill_bundle_id8c21…8c21…same
challenge_content_hashe4d0…e4d0…same
rubric_content_hashb07c…5d93…differs
cases_content_hash91fa…91fa…same
model_contract_hash6e2b…6e2b…same
agent_model_idmodel-amodel-asame

Select two completed episodes with the same challenge, skill, rubric, cases, and model contract.

Read the developer docs

The platform

Where a release review gets its inputs.

Use Assurance on its own, or with the rest of Versalist. Challenges fix the cases. Skills hold the revisions. Assurance compares them.

Versalist Skills

Guided setup

A private registry for your team's agent skills. Publish a version once and everyone pulls the same one. Roles and review policy decide who can publish, and every rollback is recorded with a reason.

revision · file digests · rollback reason

Versalist Challenges

Guided program

Challenge programs on your team's real workflows. Each challenge fixes the task, the cases, the rubric and the execution policy, which is what lets two runs be compared.

cases · rubric · execution policy

Versalist Tools

Free, no account

A free directory of tool contracts. See what a tool can do and what access it needs before your agent calls it, and verify contract exports in your browser.

Browse Tools

Continuous learning

A failed case becomes the next revision.

The model behind your agent does not learn from yesterday’s failure. Its skill can. Versalist turns a failure into a proposed amendment and tests it before anyone promotes it.

  1. Observe

    Import the execution receipts from a completed episode and read what failed.

  2. Propose

    An improvement cycle drafts an amendment: the skill version it starts from, the new content and the reason.

  3. Test

    Baseline and candidate run on a random sample of acceptance cases. Cases that produced the proposal are excluded.

  4. Promote

    A person promotes the amendment when the comparison supports it. A model proposal alone cannot.

The skill changes, not the model weights. A proposal alone cannot authorize promotion: the comparison has to support it. The workflow runs on personal skills today.

Read the improvement workflow

Security

Review access and data handling

Reviews start private. Owners control how they are shared.

  • Private by default

    Reviews start private. Owners can share with an organization or create a public link for eligible reviews.

  • Secure credential storage

    Model-provider keys are stored per user in Google Secret Manager.

  • Scoped, revocable API keys

    Give each integration only the access it needs, and revoke it at any time.

  • No prompt text in traces

    Trace capture stores prompts as hashes, never as text, and never records model reasoning.

  • Locked evidence

    The evidence behind a review can’t be edited, and decisions are added, never overwritten.

  • Your production runtime

    Versalist never operates your production agent.

Get started

Start with one workflow.

Our team works with yours to scope one workflow and review the results.

  1. Scope

    Pick the workflow and agree on what good looks like.

  2. Set up

    Prepare your agent’s skill and model, and turn real cases into a test suite.

  3. Compare

    Score every candidate version against the one you run today.

  4. Decide

    Make the release call and share the results with leadership.

What you’ll need

  • A pilot owner, about an hour a week
  • One engineer for setup, one to two days
  • One security review session

Need to make the case internally? Build your business case

Frequently asked questions

Can’t find what you’re looking for? Talk to our team.

Request a demo
A release review for AI agents. Before a change ships, your team sees the version you run today and the new one side by side, case by case, and records Ship, Hold or Needs work with the evidence.