Who is here?
Resolves wallet user, role, app access, session state, and linked profile context.
Agentic operations
Control map for governed agent work.
This page explains how identity, consent, routing, verification, receipts, exports, and trust should coordinate. It does not launch agents, mutate authority, send messages, file documents, purchase anything, or create durable execution receipts.
What can be seen?
Checks visibility scope, purpose, expiration, and minimum-necessary boundaries.
Where do they go?
Routes into eligible governed workspaces without manufacturing authority.
What happened?
Represents the receipt/provenance role expected after authorized execution.
What must be protected?
Keeps protected, irrelevant, or unauthorized context outside the task.
What can be shared?
Defines how a reviewed output would be prepared for an approved purpose and audience.
Reference operating loop
1. Resolve identity
Identify the human and current context.
2. Resolve authority
Determine what may happen under the declared purpose.
3. Route capability
Select only eligible tools/providers/workspaces.
4. Execute and verify
Consequential work remains behind the applicable human and system gates.
5. Return receipt and memory decision
Execution evidence and retention are separate decisions.
Where actual work happens
Use the workspace directory for available public tasks. A future live agent operations console would need authenticated authority resolution, scoped tools, execution isolation, verification, revocation, and durable receipts before this page could truthfully become an execution workspace.