Bengar Trust AVAILABLE
Bounded authority for anything that acts on someone else's behalf.
What it is
- The authorization platform: identities, permits, policy, approvals, execution and proofs. It decides whether an action may happen, performs it, and records what happened in a form somebody else can check.
- It works with no chain. The network is a witness for the audit trail, not a step in a decision.
Why it exists
- The alternative is a credential. A credential does not know what it was issued for, so its blast radius is everything it can reach — and reviewing the prompt that uses it is not a control.
- Bengar's unit is a bounded, signed, expiring statement of what may be asked for. A compromised caller can ask for more and be refused, and the refusal is a fact somebody can read afterwards.
How it works
- An issuer signs a permit for a subject: actions, resources, conditions, a window.
- A project publishes a policy: deterministic rules over action, resource, agent, amount and time.
- An agent presents the permit and asks. The Gateway takes the meet of permit and policy, and consults risk.
- ALLOW proceeds; DENY stops; REQUIRE_APPROVAL opens an obligation a person must discharge.
- The decision writes an audit event. Events are batched, the root is anchored, and any event can be proven against it.
Who uses it
- Teams putting an AI agent anywhere near money or customer data.
- Platforms that need per-tenant authorization they can explain during an audit.
- Anybody who has to answer “who allowed this, and how do you know”.
Security boundary
- A permit is not authority. Authority is the meet of permit, policy and approval.
- REQUIRE_APPROVAL is not an allow — it is its own value, never an ALLOW carrying a flag.
- A dependency that cannot be reached produces a refusal, not a permissive default.
Example flow
A purchase, end to end
- Acme issues a permit: the procurement agent may purchase from `resource://company/procurement/*`, up to 5,000 ₺ per transaction, for 30 days.
- Acme's policy allows that resource under 5,000 ₺ and requires approval above it.
- The agent asks to buy a 5,000 ₺ laptop. Permit allows; policy allows. **ALLOW**.
- The Gateway calls the merchant with an idempotency nonce and records SUCCEEDED.
- An audit event is written, batched, and anchored. Six months later a reviewer proves it was not edited.
Current status
| Capability | Status | Where |
|---|---|---|
| Authorize an agent action | AVAILABLE | The API: POST /v1/authorize |
| Read the audit trail | AVAILABLE | /projects/:id/audit |
| Verify an audit event against its anchor | AVAILABLE | /projects/:id/proofs |
Related API
POST /v1/authorizePUT /v1/projects/:id/policyGET /v1/projects/:id/audit/:auditId/proof