Define the Outcome. Staff It. Reach Every System It Touches.
What the business signs, who works it, where the work goes. One signed definition of done. One roster of people and agents. Reach into every system the work lives in, including the ones with no API.
- Backlog cleared to the agreed agemeasure · source · risks
- Every case has a disposition on recordmeasure · source · risks
- Exceptions routed to a named ownermeasure · source · risks
- Evidence pack accepted by auditmeasure · source · risks
before anything runsSignedby the business
> submit JOB0142ok · recordedWhat Are We Trying to Prove Done, and Who Does It?
Three answers, in the order the page tells them. Select one to see it up close.
A definition of done the business signs. Not a prompt, a deck or an intention. The objective every agent is bound to.
Section 01 · Outcomes ↓Agents and people with named roles, and one rule: the agent that validates is never the one that executed.
Section 02 · Workforce ↓An API, documentation only, or a console. Three ways in, one contract, one record.
Section 03 · Reach ↓Nobody argues about done after the fact.
Before a single agent runs, the business signs what done means. Everything that follows is measured against that signature, and the proof is built as the work happens.
Start from the outcome. Not the ticket.
One portfolio of every outcome in flight, each criterion tied to the evidence behind it.
Go to Outcomes, section 01 →Set the standard once. Apply it a thousand times.
A map sets the shape; every deliverable inherits it. Progress is counted, never typed.
See maps and deliverables, section 01 →Agents and people on one roster, under one supervisor.
Every agent has a name, a contract and a job. So does every person. And the one that checks the work is never the one that did it.
No black boxes. Every agent accounted for.
What it did, why, under which rules and at what cost, down to each tool call.
Go to Workforce, section 02 →The validator is never the executor.
Planning, execution, validation, oversight: enforced by the platform, not a line in a prompt.
See the four roles, section 02 →Door one is an API. Every vendor has that. Doors two and three are where the demos stop.
Your highest-consequence systems were never built for agents. Two doors nobody else opens get Ariad to them anyway, under the same contract, onto the same record.
No connector? Not a blocker.
Hand Ariad the vendor's documentation. It builds the binding this outcome needs, and nothing more.
No API at all? A console will do.
A governed Workspace in your own cluster, where the contract decides what the agent may type.
The page tells it in that order: 01 Outcomes · 02 Workforce · 03 Reach · 04 Integration control
The page tells it in that order: 01 Outcomes · 02 Workforce · 03 Reach · 04 Integration control
Start from the outcomes you are accountable for. Not from tickets.
Every outcome in flight in one place: criteria met, approvals pending, the whole workforce. Each criterion links to its evidence, and anything waiting on a person arrives with a recommendation.
- Define an outcome, or describe a problem and let Ariad propose candidates
- Progress is n of N verified, never a percent typed by hand
The map sets the standard. Deliverables apply it at scale.
A map sets the phases, owners and expected evidence once. Each deliverable applies it to one real unit, a branch, a region, an application, with its own checklist.
- Change the map once; every deliverable inherits the standard
- The second outcome reuses the shape of the first
No black boxes. Every agent and person on the outcome, with what it did, why, under which rules, and at what cost.
A supervisor holds every agent to the result over one shared working state, with runs, errors, cost and health visible per agent down to each tool call. People sit on the same roster, in the same audit trail.
- Four roles: planning, execution, validation, oversight. The validator is never the executor
- Each agent has its own identity and a contract; hand-offs verified, never trusted
Your most important systems have no API.
Ours doesn't need one.
Mainframes, green screens, appliances, vendor products with nothing but documentation: the highest-consequence systems in the building, and where every other demo stops. Ariad reaches them under the same contract, onto the same record.
The vendor has an API and no connector. Ariad reads the documentation and builds one.
Ariad reads the vendor's documentation and binds only the operations this outcome needs, each one allowed, gated or denied by the contract. Nothing else is bound.
The binding runs inside your environment under the agent's own identity; every call is signed into the pack.
A console is enough. The contract is the allow list.
A Workspace is a governed sandbox in your own cluster where an agent reaches a system with no API, through a terminal, for instance. Not screen automation, which replays a recorded path and breaks when the screen moves: the agent gets an environment and a contract, and the contract bounds what it may do.
Workspace images are certified with your platform team; where policy requires, your people execute the production steps at a gate.
Each connected service, and exactly which of its tools each agent may call.
Allow and deny are decided at plan review and enforced for the life of the outcome. Connections are monitored, versioned and owned.
- Least privilege per agent, per integration, per outcome
Every category, three doors, one rule: nothing is connected until a plan review grants it, tool by tool. The catalog lists each system by how it is reached.
Application onboarding at an F500 payment processor, run as one outcome under governed automation.
The process mapped, the systems named up front, the approvals built in as gates. The time moved because the work and the controls moved together.
In Your Words.
Can we start with a single outcome?
Yes. Runtime Edition is a fixed set of outcomes built with you and handed over. Most clients start with the one they are measured on.
What if the system has no API?
A governed Workspace drives it through its console, every keystroke signed. The contract is the allow list.
Who signs the definition of done?
The business owner of the outcome. Risk and audit see it first. Our Outcome Desk drafts it with you; it is yours once signed.