Five stages. Five named approvals. No hidden steps.

Software the AI can’t sign off on

CARI Forge turns a plain-English brief into a governed workflow — and never lets it past a stage without a named human approving it.

Submit a brief See how it works

Forge Canvas — ticket triage

BuildRunsApprovalsMissionsAudit

SStarttriggerAClassify the ticketagentHHuman approvalpausedEReleaseend

named human gates — every stage needs a person to sign

specialist agents run the pipeline — Partner and Impact work alongside

stages that can clear without a named approver

Why CARI Forge

Governance that isn’t paperwork

The approval isn’t a checkbox bolted on at the end. It’s the thing the workflow stops for.

Stops for a person, by design

A run reaches an approval node and pauses — it does not proceed on a timeout, a default, or a confidence score. Someone named has to approve it, with a typed reason, before the next step executes.

Every decision keeps its receipt

Who approved, when, on what evidence, and the reason code they chose — recorded against the stage and replayable afterwards. Corrections are recorded too, rather than quietly overwriting what happened.

Most AI tools ask you to trust the output. CARI Forge assumes you can’t — so it puts a named human in front of every stage, and keeps the record that proves it.

Governed

How it works

Brief in. Governed workflow out.

Describe it once in plain English. Shape it on a canvas. Take it through five named gates.

Describe it, then draw it

Write what you want in plain English and CARI Forge drafts the workflow for you. From there it’s a drag-and-drop canvas — add a step and it connects itself to the one you had selected.

Plain-English briefAI-drafted first passVisual canvas

Start a brief →

1Describe the outcomeplain English

2Review the drafted workflowcanvas

3Run it, with gatespauses for approval

Five gates, each with a named signer

A mission crosses five gates. A named Elder Oracle must personally sign the first and the last; the three in between are signed by that stage’s named specialist. No gate clears itself.

See the stages →

0Need acceptedElder Oracle

1Ready for workflowReadiness

2Workflow approvedWorkflow

3Governance clearGovernance

4MVP build approvedElder Oracle

Argued in five voices

Before a gate is put to a human, the council argues the case in five fixed voices — so the person signing sees the objections, not just a recommendation. Objections are recorded and have to be resolved, not dismissed.

Meet The Oracles →

RiskDemandGrowthCompetitionMoney

Getting started

Three steps to your first run

No configuration, no integration work, no schema to learn before you see something happen.

Say what you want, in a sentence

“Triage inbound support tickets and escalate anything about billing.” That’s the whole input. No schema, no config file, no integration to wire up first.

›Triage inbound support tickets…your brief

›Drafting workflow4 steps found

Adjust it on the canvas

You get a drafted workflow, not a blank page. Drag steps around, add one and it wires itself to whatever you had selected, and drop in a human approval anywhere you want the run to stop.

AClassify the ticketagent

CIs it about billing?condition

HHuman approvaladded by you

Run it and approve it

The run executes until it hits your approval step, then stops and waits. You approve with a typed reason, it carries on, and the whole thing is recorded against the run.

✓Start → Classifysucceeded

⏸Human approvalwaiting for you

✓Releasesucceeded

Evidence

Built to be audited

The record is the product. Every layer below exists so a decision can be defended later, by name.

CARI Forge is built for buyers who will be asked to justify an automated decision after the fact — procurement, public sector, regulated industries. That means the audit trail can’t be a log file bolted on afterwards; it has to be the thing the workflow produces.

How the council works →

Audit-trail bundle per run

Persisted as a SHA-256 hash chain

90-day minimum retention on every artefact

Typed reason code on every gate decision

EU AI Act Articles 12 & 14 readiness memo

Engagements

Start with one brief

Three engagement shapes. Each is scoped and quoted per buyer rather than sold off a price list.

Pilot

One one-line brief, one council ruling, one Software Build. Includes the audit-trail bundle per run, persisted as a SHA-256 hash chain, with a 90-day retention minimum on every artefact.

See what’s included

Most common

Procurement

A programme of briefs with a consolidated evidence package at handover: a cross-case audit-trail bundle with a per-case hash chain, and a reporting cadence tailored to the procurement timeline.

Talk to us

Public Sector

Extended-timeline posture with an explicit EU AI Act Articles 12 & 14 readiness memo, a typed reasons log per gate decision, and supplementary evidentiary artefacts produced to the buyer specification.

See what’s included

Bring us something you’d need to defend.

Send a one-line brief. You’ll get back a governed workflow with every approval attributable to a named person.

Submit a brief See pricing