AI VERIFICATION / BY NOVA LABS

AI says it’s done.Tesven checks.

Tesven independently checks whether AI work matches the expected result, using real checks and evidence.

v0.1.0 release candidate · consumer installer planned

See the difference
Interactive demonstration · example data
Dovren

Update the website logo.

Task completed.

The agent’s claim.

Tesven4/4
  • Website reachable
  • Expected logo found
  • Deployment active
  • Change persisted after refresh
Verified

The evidence supports the expected change.

Illustration of the method. This is not a live run or an application screenshot.

01 / THE GAP

“Done” isn’t evidence.

AI can do useful work and still miss the final step. Completion and correctness are different things.

What the AI saysTask completed.Dovren
What actually happenedThe expected change wasn’t saved.Observed result

Tesven checks the gap.

02 / THE CHECK

The result. Not the promise.

It compares what should have happened with what the evidence actually shows.

01

Did the expected change happen?

02

Does the file exist with the right content?

03

Is the website reachable?

04

Does the underlying system reflect the change?

05

Does the result remain after refresh?

The exact checks depend on the task, authorized access and available evidence.

03 / THE METHOD

From action to evidence.

  1. 01

    AI works

    Dovren or another supported system performs a task.

  2. 02

    Tesven receives

    The expected outcome and authorized evidence.

  3. 03

    Tesven checks

    Independent reads compare the actual and expected states.

  4. 04

    You see the result

    Verified, failed, insufficient evidence or human review.

See how it works

04 / THE CHALLENGE

It can disagree with “done.”

When the evidence contradicts the claim, Tesven says so. Missing evidence is never silently treated as success.

Illustrative example

Update the customer name.

DovrenTask completed.
TesvenVerification failed.

The expected customer name was not found after refresh.

05 / THE PRODUCT FAMILY

Dovren executes.

ACTIONby Nova Labs

Tesven verifies.

EVIDENCEby Nova Labs

One does the work. The other checks the outcome. Two products. One clear responsibility each.

Explore Dovren

Today: optional, manual import of a local Dovren evidence bundle. Direct connection and verification inside Dovren are planned.

06 / THE EVIDENCE

A checkmark with a reason.

See what was checked, what was found and where the evidence came from. A verified result is always limited to those checks.

If it can’t verify, it says so.

Tesven / VERIFICATION RECORDDEMO–024

Homepage update

Verified · within the scope of 4 checks

Expected
The new hero appears on the website.
Observed
Expected content present after refresh.
Limit
Does not assess design quality or every page.

Concept interface · example data

07 / THE EXPERIENCE

Verification without the setup.

The experience we’re building: download, open and connect Dovren. The verification engine takes care of itself.

Planned consumer experience

  1. 01Download
  2. 02Install
  3. 03Open
  4. 04Connect Dovren
  5. 05Ready

The current v0.1.0 candidate is a technical source distribution. It still requires local setup. No one-click installer or automatic Dovren connection is available yet.

08 / USE CASES

Where the final state matters.

01

Website changes

Check whether the expected content appears after an update.

02

Files & reports

Confirm that an authorized file exists and contains the expected result.

03

Business workflows

Compare the final state in supported tools with the intended change.

04

Connected systems

Check a supported system response against an expected value.

Examples of verification methods; support depends on the configured verifier. v0.1 is for synthetic demonstrations, not customer operations.

For anyone relying on AI work.

Individuals

Know whether the expected result actually happened.

Teams

Keep the evidence behind each result.

Businesses

Evaluate outcomes before relying on automated actions.

Developers

Define checks for supported verification workflows.

09 / TRUST & PRIVACY

Local by design.

The v0.1 runtime runs on your computer, stores its verification history locally and includes no analytics or model-provider calls.

Security at Tesven

Evidence encrypted at rest

Evidence objects use AES-256-GCM; database backups are not automatically encrypted.

Authenticated local communication

The local service requires a token and listens only on loopback.

Explicit limits

No network deployment. Use synthetic data only in this release.

If it can’t verify, it says so.

Independent checks. Evidence-backed results. Clear failure states. Human review when the evidence is ambiguous.

10 / THE PRODUCT

Every state has a place.

Explore the proposed product experience, including failure and disconnection. These are concept views, not screenshots of the shipped console.

Concept interface

Overview

● Engine ready · Dovren connected

18verified1failed2unverified
Update homepage2 min agoVerified
Create report12 min agoVerified
Change contact24 min agoFailed

Example counts. They do not represent product usage or performance.

11 / QUESTIONS

A few clear answers.

What is Tesven?

Tesven is a proprietary AI verification product developed by Nova Labs. It independently checks whether work performed by AI agents matches the expected result and records supporting evidence.

What does Tesven verify?

Defined conditions in authorized file, browser, desktop, HTTP and permission-state evidence. The exact checks depend on the configured verifier and available access. v0.1 is limited to synthetic demonstrations.

How does Tesven work?

It receives the expected outcome, independently reads authorized evidence, compares the actual state with defined conditions, and records a verdict with evidence references.

Does Tesven work with Dovren?

Yes, through an optional, manual import of a local evidence bundle exported by Dovren. Automatic connection and results directly inside Dovren are planned, not available in v0.1.

Does Tesven use AI to verify results?

The v0.1 local runtime does not call a model provider. Verification uses defined checks and independent readbacks. The result depends on the quality and scope of those checks.

Can Tesven detect an AI agent failure?

It can identify when available evidence shows that a defined condition was not met. It cannot detect every error or verify an outcome it cannot observe.

Does Tesven work locally?

Yes. The v0.1 runtime and verification history are local. Initial dependency installation requires package-registry access. This release is for synthetic data, not real or confidential customer data.

Is Tesven open source?

No. Tesven is proprietary software owned and developed by Nova Labs. Its third-party components retain their own licenses and notices.

Who develops Tesven?

Nova Labs, a software and AI company based in Paraguay.

Can I download a consumer installer?

Not yet. v0.1.0 is an unpublished release candidate distributed as source for technical evaluation. The consumer installer and automatic setup are planned.

AI can do the work.Tesven checks the result.

Verify AI work with checks and evidence.

v0.1.0 release candidate · consumer installer planned