The authority layer for consequential action.

Connect autonomous work to explicit authority. Evaluate the exact request, enforce the boundary, and keep the decision verifiable.

A credential is not a mandate.

VERAUTHOR separates the ability to connect from the authority to perform a particular action. A principal, an action, a resource and the relevant constraints form the authorization question.

Delegated authority and policy determine whether the request is allowed, held for an authorized human, or denied. Mapped workload access is not itself a grant.

Scoped principals

Keep the configured actor and tenant bound to the workload credential. Do not trust caller-supplied identity assertions.

Bounded authority

Express action and resource scope with constraints appropriate to the workflow, such as amount, currency, environment or revision.

Put the boundary before the call.

The mapped HTTP gate accepts an operation identifier, a small validated input object and an idempotency key. Server-owned mappings construct both the authority request and the outgoing business request from the same values.

Production HTTP startup requires mapped mode and valid configuration. An authorized decision does not make a caller-controlled arbitrary HTTP proxy safe.

ALLOW

Permit the unchanged request when the applicable authority allows it.

HOLD

Stop for the authenticated human approval process. Release rechecks the workload and requires a valid, bound, single-use ticket.

DENY

Do not release the protected request. Retain the decision context for investigation.

Make the decision inspectable.

Signed Verauthor Receipts record authorization decisions with verifiable integrity. The audit lifecycle connects the request, policy context, approval and ticket where applicable.

Evidence helps a reviewer ask who had authority, what was evaluated and why the decision was made. It does not turn an authorization event into proof of downstream completion.

Signed decision receipts

Verify the recorded decision and its integrity using the applicable verification material.

Audit exploration

Investigate the authorization lifecycle and its related principals, grants, approvals and receipts.

Keep people in the decision.

The operator experience brings decision explanations, approvals, authority administration and audit exploration into one workspace.

The authenticated operator path uses a server-side backend-for-frontend with tenant binding and scoped human roles. Long-lived control-plane credentials do not belong in browser JavaScript.

Explain the action

Review the significant business parameters, relevant authority and decision before approving a held request.

Validate the experience

Operator comprehension, redaction and real browser workflows must be accepted during a pilot—not inferred from passing unit tests.

Start small. Prove the boundary.

Python and TypeScript SDKs, HTTP enforcement and an MCP reference path support integration work. The reference refund and deployment contracts are bounded adapters, not drop-in vendor APIs.

Begin in an isolated or staging environment. Review transport, identity, secrets, upstream behavior and operational responsibility before expanding the scope.

Integration guide

Understand the interface and deployment responsibilities.

For developers

Security & readiness

See the controls and the remaining acceptance work.

Review the scope

See the boundary in context.

VERAUTHOR workspaceProduct demo

Change a request, review its authority, then approve or reject it. Every control below works with sample data.

Decisions

Sample data · this browser only

Customer refund

Principal
Refund agent
Resource
Example payment 001

Automatic limit: £100.00. Change it in Authority.

ALLOW

Within delegated authority.

The requested amount is within the example grant. You can simulate release without contacting a payment system.

Synthetic data only. No live authorization, payment or deployment. An authorization decision is not proof of a completed action.

Discuss your workflow.

Define the actions, limits and approval process your team needs.

Let’s discuss your pilot