Authorize the exact action. Preserve evidence of what crossed the boundary.
TrustAccept separates an agent or workflow’s proposal from the human decision, the short-lived authority to execute, target-side verification, and the signed evidence record. Approval creates accountability; enforcement happens only when the production execution boundary validates the exact authorization.
Five boundaries, not one approval button.
TrustAccept is designed for actions where “someone clicked approve” is not enough. The system must bind the approved action to the executor and target, deny material mutation or replay, and preserve scoped evidence.
Proposal
The agent or workflow proposes an actor, action, target, protected parameters, and business context.
Decision
An authorized human approves or denies under the required identity and assurance policy.
Authorization
A short-lived grant is bound to the exact approved action, target, policy, executor, environment, and expiry.
Enforcement
The connector, broker, gateway, executor, or target verifies the grant and rejects mutation, expiry, revocation, or replay.
Evidence
Signed receipts preserve the governed request, decision, authorization, validation, outcome, and linked evidence hashes.
Wire Evidence for consequential API exchanges.
Hash the exact captured request and response bytes, bind them to bounded transport and action context, link the record to prior evidence, and sign the manifest—without copying credential-bearing payloads into the receipt.
- Exact request-byte SHA-256 and byte length
- Exact response-byte SHA-256 and byte length
- Length-framed request/response pair hash
- Protocol, method, authority, path template, status, and TLS metadata
- Action, actor, target, policy, capture, and prior-receipt references
- Signer metadata, manifest hash, signature, and receipt hash
One core control model, scoped reviewer paths.
IBM program
Reviewer material for exact-action authorization, human decisions, target verification, and signed evidence in IBM-oriented workflows.
Microsoft Entra / EAM pathMicrosoft program
A dedicated path for identity-governed enterprise actions, approver assurance, and marketplace-readiness conversations.
Partner distributionMarketplace paths
Scoped technical and commercial paths for IBM, Microsoft, MCP, Auth0/Okta, and other enterprise identity ecosystems.
Bypass resistance is architectural.
If an agent retains another standing privileged credential or alternate route to the target, it can bypass TrustAccept. A deployment is described as TrustAccept-enforced only for actions that must cross the configured verification boundary.
A signed receipt proves its signed manifest—not every surrounding claim.
Evidence quality still depends on capture authorization, completeness, clock and identity quality, target integration, and custody controls. TrustAccept scopes the claim instead of overstating it.