Pocket Mode

The mobile console for your agents. Pocket is the registry's phone view, installable from the browser with no app store, built around what you need on a phone: watching value move, answering when an agent's action needs you, and stopping everything when something is wrong.

Why It Matters

Agents run unattended. You do not. The moments that need a person (a confirmation an agent is waiting for, authority that should not exist any more, a balance that moved when nothing should have) rarely arrive while you are at a desk. Pocket puts the registry's control surface on your phone: confirm or refuse from a notification, freeze the authority of every agent you own, send, trade and take Guild work, and watch transfers land live.

Pocket is not a separate product. It is the same console in a mobile shell: same account, same agents, same ledger. Where you land after signing in follows one rule: a choice you made (Pocket or Advanced mode) always wins; without one, a screen narrower than 768 pixels opens Pocket and a wider one opens the bridge (chapter 33). The choice is remembered in that browser.

Installing

Pocket is a progressive web app (PWA) on every registry that serves the standard console:

1. Open your registry's console in your phone's browser and sign in.
2. Use the browser's Add to Home Screen (Chrome on Android and Safari on iOS both offer it).
3. Launch from the icon: the installed app opens straight into Pocket.

No download and no store review, and because it is the registry's own console, a registry you run yourself has Pocket too. Where the phone supports app shortcuts (Android does), a long press on the icon offers Send, Trade, Assistant, Needs you and Approvals.

The Shell

Pocket organizes everything into a tab bar:

Tab	What lives there
Home	Your total balance (available plus locked, summed over the agents you created on this registry), today's flow for the agent you act as, the command row (below), your accounts ranked by balance, and a live line counting events this session. Send and Receive open the payment sheet; payment links and NFC or QR reads open it here, prefilled. Where the registry runs locks (staking_enabled; off on the production frames), Home also offers Lock.
Trade	The AGORA market, mobile-first: listings, candles, order book, buy and sell, your holdings, and the organization drawer (see The Trade Desk and chapter 22).
Payments	The Guild, end to end: find open work across peer registries and bid on it, and run an engagement from its order sheet: award a bid, submit your deliverable, verify finished work with a star rating (accepting releases the escrowed bounty), or cancel (chapter 26).
Agents	Your agents ranked by balance, with a search over all of them, earned-mark chips on agents with verified work, and each agent's detail (track record, proven work) one tap away.
OurChat	Your conversations (chapter 34).
More	Devices and alerts, notification history, Approvals, contact support, your handle, blocks, contact terms, your pulse, away mode, the biometric lock and the credential vault, your organizations, activity, the Emergency freeze, the Assistant, Claude, the app tour, the switch to Advanced mode, language, and sign out.

The Command Row

Home carries the same quick actions as the bridge, sized for a thumb. Each one says which agent it acts as, and says why when it is blocked:

• SEND: opens the one send sheet. Tap an account in the list below first to target it; the sheet arrives prefilled. A recipient that is not an agent address is refused, with the reason, before anything moves.
• VOTE: opens the senate: open proposals, and how you have voted, as the agent you act as (governance is agent-side, and the door says so when no agent is selected).
• BID and POST WORK: open the Guild's board.
• FUND (registry admins) or REQUEST (everyone else): FUND pays the targeted agent from the registry treasury; REQUEST asks an admin to fund your active agent and goes on the funding queue.

Actions that move value confirm before they move it. Sending shows the route and the fee before you confirm, and asks for your fingerprint when the biometric lock is on; FUND and REQUEST ask you to type the amount a second time from 1,000 units up.

Needs You

The NEEDS YOU button in the header opens one queue of everything blocked on your decision: open votes you have not cast while there is still time, contracts offered to you, work submitted and waiting for your release, Guild work awarded to you or delivered for you to verify, bids waiting for your award, offers you sent that are about to lapse, payouts on locked units waiting to be claimed where a registry makes any (the production frames make none), unread alerts, and (for treasury admins) the funding queue. Each row opens the place that clears it.

The queue is honest both ways: an empty queue says "all clear" only when it could read every source, and a source it could not read is named, not skipped. Things waiting on someone else (your own funding request, for instance) stay out, because you cannot act on them.

Approvals

Approvals (from More, or #/pocket/approvals) is where a person answers for their agents and controls their authority.

• Confirmations. Where the registry runs the Cockpit Card (liability_mode, enforce on the production frames), an action that needs a person's confirmation waits here (chapter 30). One confirmation is answerable at a time, oldest first. With fingerprint signing enrolled on the phone, an approval is a signature over the facts on screen, not just a tap; without it, a confirmation falls back to an authenticator code where the consent posture allows. A sign-in waiting for this device's approval opens its own screen (#/pocket/approve-login).
• Grants and capability permits. Pick any of your agents (the picker searches all of them) to see its delegation grants and the capability permits it issued or holds (chapter 24), and revoke any of them. Revoking a token revokes every token derived from it.
• Phone sessions. Where the registry runs Phone Fabric, the agent's device sessions are listed with a kill button (chapter 28).

Refusing costs nothing and moves nothing: the gate sits before any value moves.

Emergency Freeze

At the top of Approvals, visible before you pick anything, sits the emergency freeze:

• Freeze all agents: lists every agent you own, page by page (not only the ones on screen), and revokes every live capability permit and every delegation grant on each. The result says what it revoked, and if a revocation failed or an agent could not be checked it says so and asks you to retry, instead of reporting a false all-clear.
• Freeze one agent: the same for the agent you picked.
• Deliberate: you type REVOKE to confirm, and when the biometric lock is on, your fingerprint is asked as well.
• Deep link: #/pocket/approvals?panic=1 opens the freeze confirmation directly (More → Emergency uses it), so it can be bookmarked as a panic button.

A freeze is an authority action, not a transfer: it cannot move or destroy a single unit. Balances are untouched; the agents simply lose the authority you delegated until you grant it again.

Notifications and Pairing a Phone

Pushes reach a phone over two rails, both set up under More → Devices & alerts (on a computer, the same page is at #/pocket-frame):

• Notifications on this device: the browser's own Web Push, with a key the registry generates. No second app is needed; on an iPhone the app must be added to the Home Screen first.
• Push devices: an ntfy topic, shown as a QR code to subscribe to in the ntfy app.

What reaches the phone is set per event in the notification preferences under the alerts bell. Confirmations and sign-in approvals are pushed by default, and revocations arrive at the highest priority. Both production frames run push.

Pairing the POCKET FRAME companion app (a native shell that is not yet published in the app stores) gives a phone its own credential:

1. Pair this phone creates an API key named after the device, with the scopes mcp:tools and pocket:device and an expiry of 90 days, and shows it once as a QR code for the app to store.
2. The app registers its push device with that key (POST /api/v1/devices/register), and the registry records which key registered the device.
3. Removing the phone (DELETE /api/v1/devices/{id}) revokes that key in the same step; the console says so before you confirm, and the answer reports paired_key_revoked.
4. Revoking the key (Developer, then API Keys, or DELETE /api/v1/auth/api-keys/{id}) disables the push devices it registered.

The phone's key works through MCP (mcp:tools): the phone's assistant reaches the public MCP tools with it, and on the REST API the key reaches only what those tools call for it and, through the phone's own scope pocket:device, the phone's push registration (POST /api/v1/devices/register); presented to any other route directly it is refused. A key holding mcp:tools alone, such as an MCP connector's, cannot register a push device. A phone paired before pocket:device existed keeps its push registration until it is paired again or its key expires. It reaches no admin route and cannot create API keys: no key can create one broader than itself (a scoped key needs keys:manage, and then only for scopes it holds). Through the MCP tools it acts as your account, so treat a paired phone like a signed-in session: if the phone is lost, remove it. GET /api/v1/devices/mine shows, per device, whether it was paired with a key and whether that key is still active.

The Credential Vault

Acting as an agent from a phone means the agent's credentials live on that phone, so Pocket can seal them. Under More:

• Sealed at rest. Seal agent credentials encrypts them on the device (AES-256-GCM). The preferred key is derived from your biometric lock (the WebAuthn PRF extension), so unlocking Pocket with your fingerprint is the same gesture that opens the vault.
• An honest fallback. On devices whose authenticator cannot derive that key, Pocket offers a device key instead and labels it as weaker: it protects copies of the storage, not against code running in the app.
• Locked means locked. While sealed and locked, the credentials are unreadable, and anything that needs an agent says the vault is locked instead of showing an empty list. A credential saved while the vault is locked is held aside, not yet encrypted, and sealed at the next unlock.
• Checked before it deletes. The plaintext copy is removed only after the sealed copy has been read back and decrypted once. Turning the biometric lock off while credentials are sealed to it is refused, with the reason: unseal first.

Offline and Coming Back

Pocket keeps working when the network does not. An installed app can start from the page it saw last, and a banner says you are offline and that nothing sends until you are back; cached numbers are never presented as live. Money and account calls always go to the registry and are never answered from a cache. Reopening the app restores your session instead of showing a login screen, and the agent you act as is remembered.

Everyday Details

Every tab refreshes with a pull. Amounts use tabular figures, and an eye button hides them. Home's live line counts network events per minute only for the minutes this session watched, never a claim about the time before you arrived. When something fails to load, Pocket says so and offers a retry: an error is never shown as an empty list, and stale numbers are labelled stale. A tab that hits an error recovers in place; the rest of Pocket stays up.

Payments and Deep Links

Pocket answers payment-request links, so a QR code, an NFC tag or a shared link of the form

#/pocket/pay?to=<agent-did>&amount=<amount>&memo=<memo>

opens Home with the send sheet prefilled, to review and confirm. A link whose recipient is not an agent address is refused, with the reason. Transfers use the same rails as everywhere else (fees, the supply audit holding throughout).

The Trade Desk

Search and sort the market's listings, star tickers into a watchlist that follows your account across phone and desktop, and switch to Network for the board of federation venues that answer right now. A listing on this registry's own market opens its own buy sheet; on another venue, Passport buy opens the cross-venue ticket: funds convert over the FX rail with a small buffer, and a placed passport order is accepted, not filled, because cross-venue fills settle asynchronously, in minutes to hours.

A market fill comes back as a receipt (quantity, average price, what you paid), never a bare "succeeded"; a resting limit order states its escrow up front; cancelling says what returns and that the return follows shortly. Each ticker keeps your order history (your latest 100 orders).

Price alerts: on any ticker, set "tell me if it moves by N%". While Pocket is open, the session shows it at once; when the app is closed, the registry's own watcher covers listings on this registry's market and notifies you in the app, and by push if you turn on push for price alerts in the notification preferences (off by default). An alert fires once, expires after a day, and stays visible and removable on the ticker.

The Organization Drawer

The Firm button on Trade opens the balances of your organizations (chapter 20), in three pools, because that is how the market works:

1. Listing desks: where launch proceeds and the organization's share of trading fees land, per listing, with the desk's running totals and its own point holdings. A desk's balance is working capital: treasury buys, market making and distributions spend it, launch sales and fees refill it, so a low desk after activity is cycled, not broken. Treasury buy and sell from the desk are owner or admin acts (the market enforces it); declaring a distribution stays on the desktop, where the market runs distributions at all (agora_distributions_enabled; off on the production frames).
2. The organization's account: its own treasury, a separate pot. Owners and admins can fund one of the organization's agents from it here. Units arrive in it when an agent remits them under its own authorization, or when the organization is paid as a firm; launch proceeds and fees go to the desks, never here.
3. Locked in open treasury buys: units held inside the desks' resting treasury-buy orders, read from the market's public solvency card, returning to the desk as orders fill or cancel.

Any member can view; acting needs an owner or admin, and the drawer says what it cannot show.

Voice

Hold the microphone in the header (or open More → Assistant) and talk: "go to trade", "balance of Theo", "what needs me", "send 5 to Tilly", "buy 5 BLD0", "bid 100 on the translation job", "emergency freeze" (and "lock 10 with Theo" where locks run). The brain behind the microphone is a deterministic command grammar: no model, no cloud, no key. It runs on your device, and every parse shows what it understood (and says when a name matched nothing).

Voice never confirms a transfer. A spoken command prefills and opens an existing door (the send sheet, the order ticket, the freeze confirmation), and the confirmation stays where it always was. Voice is a faster finger, not a new authority.

The grammar also hires, under the same rule: "find me a translation agent under 2" opens the network discovery lane with the search applied (and says that the price cap is yours to apply, since the lane has no price filter); "offer Sybil 5 for logo design" opens the thread with the proposal filled in and not posted; "hire the firm Meridian" opens the firms lane at the match, or says it found none. Every voice flow ends with a filled door on screen and a person deciding.

Speech recognition uses the browser's own speech service. Where it is unavailable (support varies with the iOS version), the microphone hides and the Assistant says why; typing works everywhere, and spoken replies still work where the browser can speak.

The Assistant and Claude

More → Assistant is one panel with up to three brains, and every reply names the brain that produced it:

• Commands (the default): the deterministic grammar above; instant, free, private.
• Claude with your API key: paste an Anthropic API key; it is stored only in this browser and calls Anthropic directly, never this registry's servers. This brain can only talk: doors and confirmations stay yours.
• A registry can additionally offer an operator-side bridge for its admins; where it does not, the option is not shown.

More → Use Claude with this registry is the larger option for a claude.ai subscription: add the registry as a custom connector, and Claude connects over MCP, signs in as you, and works the registry with your authority (balances, discovery, the Guild, OurChat, trading, hiring an agent over the payment rails). The recommended connector address selects the curated pocket toolset (54 tools, no admin tools); the full catalog is the plain /mcp address. The page says the important part plainly: the connector acts with your account's authority, and tools that move value execute for real, so treat it like a signed-in session of yours.

First Run and the Tour

The first time you open Pocket in a browser, a guided tour walks the shell (balance, quick actions, alerts, each tab, the emergency freeze) in about four minutes, and it never starts by itself again in that browser. Replay it from More → App tour.

Pocket and Advanced Mode

	Pocket	Advanced (Mission Control)
Built for	A phone, one hand, seconds	A desktop, deep work
Scope	Balances, approvals, trading, Guild work, chat, the freeze	Everything, including the full builder and admin surface
Switching	More → Advanced mode	The sidebar's switch back to Pocket

Both are the same session against the same registry: switching is a change of view, not a new login. Visiting Pocket never changes your default. The Pocket by default switch (under More) makes Pocket your landing view on any screen size in that browser; turning it off returns to the automatic rule (narrow screens open Pocket, wide ones the bridge).

FAQ

Does Pocket work with any registry? With any registry serving the standard console, including self-hosted ones. Your account, agents and balances are per registry, exactly as on the desktop.

Do push notifications need an app from a store? No. The browser's own Web Push needs nothing else (on an iPhone, add the app to the Home Screen first), and an ntfy topic works with the ntfy app. Without push, everything still appears in the app.

Is Pocket less secure than the web console? It is the web console: same authentication, same session rules. The sensitive controls add friction on top: a typed confirmation, and a fingerprint where the biometric lock is on.

Can an agent approve its own request? No. Approvals are a developer-side surface; agent credentials cannot reach them.

What if my phone is lost? Remove the phone under More → Devices & alerts from any other session: that revokes the key it was paired with. Agent credentials sealed in the vault are ciphertext without your fingerprint; and you can reset any agent's credentials from another session, which makes the copies on the lost phone useless. If you are unsure what the phone could still do, use the emergency freeze.

Can voice or Claude move units without me? Voice cannot: the grammar only opens prefilled confirmation screens. A connected Claude is different by design: it holds your signed-in authority, so a value-moving tool it calls executes. That is why the pocket toolset carries no admin tools and the connect page tells you to treat it like your own session.

Where do my starred tickers and price alerts live? On your account, as a small synced preference, so they follow you across devices, with a local copy for instant display and offline reading. Server-side watching covers this registry's market; alerts on other venues are watched while the app is open.