Cryptographic Mandate Controls for Machine-Originated Payments
AI can propose. It cannot execute.
Most systems verify identity.
Some secure communication.
None enforce whether an action should actually happen.
That is the gap.
The Missing Layer: Enforced Execution
As AI systems begin to act in the real world, the risk is no longer incorrect responses. The risk is unauthorized execution.
Knowing who sent a request does not guarantee the request should happen.
Every action must be explicitly authorized before it can execute.
If it cannot be precisely authorized, it does not happen.
How Yebo Works
Passkey Identity
Approvers authenticate with passkeys (WebAuthn), not passwords: the private key stays with their device's authenticator. Platform passkeys can sync across a person's own devices. The gateway checks each approval session before a mission runs.
The Cryptographic Mandate
Every payment mission requires a human approval with a passkey. Your passkey approves the mission's limits (capabilities, per-transaction limit, payees), the gateway issues a time-bound mission token, and every payment in the mission is checked against those limits. Per-payment device signing is live and has been exercised in production: the approver's passkey signs the exact payment (amount, payee, agent, validity window), and anyone can check it offline with yebo-verify 0.2.0.
Policy-bound Mandates
All actions are defined as deterministic authorization contracts. Each mandate is bound to an active policy and precise execution parameters.
If the policy does not match at execution, the action is blocked.
Replay-resistant Execution
Every continuation token and approval challenge is consumed exactly once; mission tokens are reusable only inside the approved limits until they expire. Replays and duplication are structurally prevented.
Sentinel (Enforcement Layer)
Every action routed through the gateway must pass deterministic validation before execution: Sentinel's system invariants on the /execute path, the mission gate on payment missions.
If any check fails, execution is blocked.
An unreachable policy service means deny.
There are no silent approvals: every approval is recorded in the audit log.
There is no execution without authority.
Scoped Execution
Agents get narrow, time-bound mission tokens, and the gateway runs only actions inside the approved scope. Execution runs in dry-run mode today: Yebo issues signed dry-run receipts and no money moves. Live payment execution and isolated runtimes for external tools are coming soon.
What This Means
AI systems can propose actions safely
Humans retain final authority
Execution becomes deterministic, auditable, and enforceable
Not monitored.
Not inferred.
Enforced.
The Shift
The industry has focused on making AI more capable.
Yebo ensures that capability does not become risk.
Identity tells you who.
Yebo determines whether.
Yebo replaces trust with enforceable authority.
Enterprise security review in 48 hours