Components are blocks; patterns are how they're arranged so the user reads the decision moment correctly. The decision packet is the signature element — every layout that explains how BehalfID works should make a verify call legible somewhere on the page.
Decision packet
The hero element. A vertical card with three regions: request, boundary, decision, then an audit footer. Use it to dramatize what verify does.
Action requestPOST /v1/verify
Agentagent_ollie
Actionpurchase
Vendorcoachella.com
Amount$742.00
BehalfID decision boundary
Decisiondenied
ReasonNo active purchase permission.
Auditverification.denied · req_3xZ9q
Product model pipeline
Four-step explainer used in marketing and docs introductions. Always in this order. Numbered 01–04.
01Action request
Agent, action, resource, vendor, amount, route — packaged before execution.
02Decision boundary
BehalfID verifies the request against the active passport before the tool runs.
03Execution state
Allowed actions continue. Denied or missing permissions fail closed.
04Audit event
Decision, reason, and enforcement result recorded for review and webhooks.
Marketing hero
Agent permission infrastructure
The permission layer between agents and action.
Define what an agent may do, verify every action before it runs, and fail closed when permission is missing.