PLATFORM — DECISIONS

Autonomy is a dial, not a switch.

Per workflow, per amount, per counterparty — you set how far Corin goes in SAP or Infor.

The same flow at every rung — only your position changes; Autopilot stays inside the policy bracket.

AI agent guardrails for your ERP: four rungs, not a leap.

Watch. Draft. Approve. Autopilot. Corin earns autonomy one workflow at a time — you set the pace.

SET PER WORKFLOW

One dial per workflow — changed anytime, logged always.

Quotes can sit at Approve while invoice matching runs on Autopilot — each workflow earns its own rung.

The autonomy dial with its gate readout — each rung names the gates in force.
ESCALATION

When it's unsure, it asks.

Below the confidence bar, outside the bounds, or missing a fact — the case routes to a person with the full brief attached.

01

The recommendation

One action, stated in a sentence, with its confidence.

02

The reasoning

Which inputs decided it — credit state, stock, contract price — each traceable to its source record.

03

The runners-up

Every recommendation arrives with its runners-up and the reason they lost. Corin doesn't take the first answer — it scores the options and keeps the losers on file.

04

The blast radius

Exactly what will be written, where — before you click.

05

The gate

Approve, edit, or reject. The ledger writes itself either way.

BEFORE ANYTHING POSTS

Every change gets a dry run first.

The dry run isn't a preview screenshot — it plays the change forward against your live SAP or Infor numbers.

The full spread of outcomes

Each dry run returns the range of outcomes — best case, worst case, the percentiles between — and which assumption moves the result most.

Played forward against real state

A candidate decision runs against real state before anything executes — the outcome is on the table first.

Seeded and repeatable

Every run is seeded: the same inputs produce the same decision, every time. Rerun it and get the same answer.

Dry runs execute nothing — they read live state and write only their own record.

POLICY & RECEIPTS

Every action names the rule that allowed it.

Nothing hits your ERP without a rule that allowed it and a record that proves it.

Receipts, not logs

Executing a decision returns a receipt binding it to the rule version in force — "which rule allowed this" is a lookup, not an investigation.

Rules are versioned

Every rule change is versioned. Every action names the exact version of the rules that approved it.

Sealed entries

Every entry is sealed with a fingerprint — edit it and the fingerprint breaks.

THE LEDGER

Every gate leaves a receipt.

The ledger — a record of every decision: what changed, who approved it, when — queryable forever. Built for the audit, not the demo.

Sample ledger rows — every gate leaves its receipt: actor, action, id, gate, status.
timeactoractionidgatestatus
09:14:02m.chenQuotation 20005731 approved and releaseda41f…9c2ehumanapproved
09:12:47policy:margin-floorQuote held — price below floorwaiting on human review7bd2…e410policypending
08:58:19corinOrder acknowledgement staged for PO-10482c9a8…22f7autoapproved
08:47:30j.okaforTerms override rejected — outside policy5e19…d044humanrejected

Illustrative ledger rows — sample data, not a customer record.

Corin never moves money, signs, or sends without your confirmation — until you tell it to.

DECISIONS, WITH RECEIPTS

See what Corin will do before it does it.