01 / capability
Approval policy configuration
Available through the product surface and the machine interfaces, with permission attached.
Authority & assurance · Concept
Authority before action.
An approval and delegation infrastructure platform that establishes, records and verifies who can authorize consequential actions.
01
What it is
ApprovalAuthority is built for Enterprises, financial operations teams, compliance organizations, automation developers.
The problem
ApprovalAuthority replaces email approvals, informal sign-offs and disconnected approval workflow software.
The approach
An approval and delegation infrastructure platform that establishes, records and verifies who can authorize consequential actions.
The boundary
Work stays inside an explicit scope: named sources, defined permissions, bounded execution, retained evidence.
02
Capabilities
Five contracts the product is specified around. Each one is a boundary as much as a feature.
02 / capability
Delegated authority and thresholds
Available through the product surface and the machine interfaces, with permission attached.
03 / capability
Multi-party approvals
Defined as an explicit contract so operators can review it before it runs.
04 / capability
Signed decision receipts
Exposed as a scoped capability with its own evidence trail, not a hidden setting.
05 / capability
API, MCP and workflow integrations
Defined as an explicit contract so operators can review it before it runs.
03
How it works
The same three steps apply whether a person or an agent is driving.
01
Define the scope
Start from the boundary ApprovalAuthority is allowed to act inside: the workspace, the sources, the budget, the authority.
02
Connect the surfaces
Expose the same capability through the interface a human uses and the interface an agent calls, with one permission model.
03
Act with evidence
Every action leaves a record that can be inspected, replayed and challenged before the next one runs.
Read the specification before you believe the category.
ApprovalAuthority is documented as a concept: requirements, interfaces and evidence expectations. It is not presented as a live service.