Versatil
The work-OS

Where a decision lands, with its dissent still attached.

Approvals, goals, and the board, all sitting on the twin. A call comes in, the brain scores it, the disagreement is kept, and it settles as a record you can reopen. This is the surface your team works in.

The work-OS

Watch a decision land, with its dissent still attached.

This is the Versatil work surface. A call comes in, the twin scores it, the disagreement is kept on the record, and it settles as something you can reopen. Not a chat log. A decision you can defend.

versatil, approvals

Approvals

2 open ยท twin scoring live
Vendor A for the ingestion pipeline
In review
twin conviction0.00
4 of 5 for, 1 dissent kept
Historian: vendor A's SLA failed twice in regulated orgs. Reopen if incidents > 2 per quarter.
Record
Vendor A, recorded with dissent conviction 0.72
Data residency, EU region conviction 0.91
Read the technology
app.versatil

Coordination: parallel agent sessions holding scopes, each reading and writing the twin, dissent kept.

Read the technology
Control

You keep the pulse of the operation.

One place where the work, the people, and the agents are visible at once, so nothing runs where you cannot see it.

Board

Kanban across the work

Every card carries the decision that spawned it, so work never drifts from the reason it exists.

Goals

The outcome, delegated

Handed to people and agents together, seeded from the twin rather than a blank brief.

Missions

A bounded objective

What the crew and the agents are running right now, with its own record.

Approvals

What needs your call

Arrives with a conviction score and the dissent attached, not buried in a thread.

Coordination

Who holds what

Live claims showing which agent holds which scope, so parallel work cannot collide silently.

Conference Room

Talk it through

Where the crew and the agents work a live situation together, in the open.

Board, goals, tasks, approvals, missions, and coordination are shipping. The Conference Room is behind a flag, and a timeline view is being wired.
See it per profession
Detection

It starts by reading the work you already have.

You do not configure it first. You point it at your work, it tells you what it found, and you decide what becomes real. Nothing is applied without you.

01

Scan my work

Point it at a folder or a workspace. It reads what is already there. No migration, no blank setup to fill in.

02

It proposes

Projects, goals, and teams drawn from your ingested work, each carrying what it found and why it thinks so.

03

You approve

Every proposal sits pending until you apply it or skip it. The twin proposes, it never auto-applies.

The scan and the proposal gate are shipping surfaces. Every screen on this site runs on specimen data you can open.
See what it proposes
Capabilities

One surface, four moves.

The work-OS is not a chat box. It is where judgment is captured, delegated, and kept.

Approvals

Score, keep, record

Requests arrive with a conviction score and the dissent attached. Approve with the objection on the record, not lost in a thread.

Board

Work that stays anchored

A kanban where each card carries the decision that spawned it, so work never drifts from the reason it exists.

Twin activity

Watch the brain reason

A live view of what the twin ingested, recalled, and concluded, so the operator trusts they see the real output.

Goals

Delegated to agents and people

Goals seed an Atelier run in under a second, grounded in the twin, so agents act from the record, not a blank prompt.

You do not need another pilot. You need enterprise AI you can answer for.

In production, on a sovereign twin, with the record of every consequential call. Early, with paying design partners, and honest about it.