Skip to content
Perspectives
← All perspectives

WEB4-041 · WEB4

Wallet Security for Machine Actors

A machine wallet should carry bounded authority, not a bag of master keys.

01

Big idea

A machine wallet should carry bounded authority, not a bag of master keys.

02

Picture

See the structure

A valet key that starts one car but cannot open the trunk, house, or safe.

Machine wallet boundary connecting identity and delegation to current authority, bounded capability and scope, provider-neutral enforcement mappings, evidence, and revocation.
Machine Wallet Authority Stack. Figure 1. A machine wallet binds identity and delegation to current authority, capability and resource scope, provider-neutral enforcement mappings, and evidence-backed revocation. Possession never becomes permission by implication.
03

The simple version

Explain it like I’m ten

A family gives a parking helper a valet key. It can start the car and park it, but it cannot open the trunk or the house. If the job ends, the key stops working.

04

Tell it at dinner

A story worth remembering

A family gives a parking helper a valet key. It can start the car and park it, but it cannot open the trunk or the house. If the job ends, the key stops working.

Now make the same problem larger: replace the children and ordinary objects with people, organizations, AI agents, robots, records, and resources moving at machine speed. A machine wallet is a governed authority boundary separating identity, authority, policy, secret custody, provider enforcement, observed access, and lifecycle state. Machine-wallet architecture reduces blast radius and makes issuance, suspension, revocation, and observed provider state legible to risk owners.

Pause at the moment the small system could go wrong. That is the design question the paper keeps in view: not whether people or helpers are clever, but whether the surrounding structure preserves the intended meaning when action scales.

That is why the small story holds: a machine wallet should carry bounded authority, not a bag of master keys.

05

Explain it to a CEO

Why leaders should care

Machine-wallet architecture reduces blast radius and makes issuance, suspension, revocation, and observed provider state legible to risk owners. A machine wallet is a governed authority boundary separating identity, authority, policy, secret custody, provider enforcement, observed access, and lifecycle state.

06

Explain it to an engineer

What the model means

Separate wallet control state from credentials and provider state; bind actor, principal, consumer, workload, capability, resource, purpose, policy, posture, duration, and evidence. Desired revocation and observed enforcement may diverge and must be reported honestly.

Talk hook

When a machine holds a wallet, what exactly is inside: identity, authority, credentials, or all three confused together?

Ask the room

Could one compromised machine wallet reach more resources than its current mission requires?

Go deeper

The Canon is the source of truth.

WEB4-041 formalizes this structure: A machine wallet is a governed authority boundary separating identity, authority, policy, secret custody, provider enforcement, observed access, and lifecycle state. The ordinary-life story is an intuition aid, not a replacement definition; the canonical paper remains authoritative for scope, terminology, limitations, and argument.

Read WEB4-041 — the authoritative paper →

Same idea. Different resolution.

Perspectives explain the Canon. The research papers remain authoritative.

Open the Canon library