Audience 01
Enterprises
Needs the same permission model for people and agents.
Authority & assurance · Concept
Where the work actually changes.
ApprovalAuthority is aimed at Enterprises, financial operations teams, compliance organizations, automation developers.
01
Who it is for
Three audiences, one boundary model.
Audience 02
financial operations teams
Uses the product where the cost of an unscoped action is higher than the cost of setup.
Audience 03
compliance organizations
Adopts it to replace a patchwork of tools with one reviewable surface.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Approval policy configuration | Makes an existing action reviewable. | Specified |
| Delegated authority and thresholds | Makes an existing action reviewable. | Specified |
| Multi-party approvals | Turns a manual control into an explicit contract. | Specified |
| Signed decision receipts | Removes an ad hoc step from the workflow. | Specified |
| API, MCP and workflow integrations | Turns a manual control into an explicit contract. | Specified |
03
Migration
How a team would move from the status quo without a big-bang cutover.
Step 01
Map the current path
Name the tools, owners and handoffs that the product replaces. Nothing is removed yet.
Step 02
Run one capability
Pick a single scoped capability and run it alongside the old path, with evidence compared side by side.
Step 03
Retire the old path
Remove the previous tool only when the new record is complete enough to audit.