Give Corin your new‑hire paperwork.
SOPs in, Procedures out — uploaded, compiled, tested, approved, versioned — ready to act in SAP or Infor.
Quote approval — new customers
- Quotes over $50,000 to new customers need the sales director.
- Pull a credit report if we haven't sold to them in 90 days.
- Never discount below the 22% margin floor.
procedure: quote-approval-new-customer
check: quote.value > 50000 → approval: sales-director
check: customer.tenure < 90d → credit report (read)
stop: margin < 22% — no override
tools: allow [credit.report, erp.price-read]
tools: deny [quote.send, margin-floor.edit]
tests: 41 past quotes replayed · 41/41 matched
quote-approval-new-customer
v7owner: sales-ops
41 past quotes replayed · 41/41 matched
released · j.okaforIllustrative Procedure — sample rule, not a customer record.
Turn SOPs into AI agents your auditors can read.
Upload the operating rules your team already wrote. Corin compiles them into Procedures — versioned objects that govern what each agent may do.
An operating rule as an owned, testable object.
The person who owns the outcome writes the rule in plain English. Corin compiles it into checks, tool permissions, and tests — released like code.
01rule
The operating instruction, in plain English.
02applies_to
The workflow and segment it governs — quote, order, AP, onboarding — and for which customers.
03allowed_tools
The exact tools the Procedure may call. Anything outside the list does not exist at runtime.
04prohibited
Actions it may never take — hard stops, not preferences.
05preconditions
Checks that must hold before it acts — compiled once, the same on every run.
06approvals
The thresholds that route to a person — value limits, new counterparties, margin floors.
07tests
Example cases replayed on every version change — a change that breaks history doesn't ship.
08owner
A named owner, a version, a release state. No orphaned automation.
Quote Agent, bounded by your Procedure. The RFQ agent cannot touch AP. Restriction is a feature: an agent's world is exactly its Procedure's tool list.
Uploaded. Compiled. Tested. Approved.
01Uploaded
The person accountable for the outcome uploads the rule in their own words — the SOP, the pricing memo, the onboarding checklist. No flowchart tool.
02Compiled
The English becomes controls and tests. Ambiguity is surfaced and resolved now — not at runtime, in front of a customer.
03Tested
The Procedure replays against real past cases from your tenant. A mismatch goes back to the owner, never into production.
04Approved
A named owner signs the release. Every version is recorded; rollback is a lookup away.
Versioned, always: a Procedure may not act until the replay passes AND an owner releases it — and every change afterwards is a new version.
Like an AGENTS.md for your operations.
The file your engineers give a coding agent, generalized to the business: rules, bounds, and tests that travel with the work.
Capability records
No tool may execute without a capability record — a Procedure's tool list is enforced by Corin's engine, not suggested in a prompt.
Corin's handbook
Procedures collect into Corin's handbook — reviewable, diffable, versioned like code.
Corrections become versions
When a reviewer fixes a draft, the fix ships as a versioned Procedure update — never an invisible model change.