> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/sonic-1.0.0-rc-production-architecture/product-and-wallet.md).

# Product & Wallet

Role-aware SONIC Wallet and Token Management architecture for 1.0.0-rc.0 revision 26.

`apps/wallet` is the authenticated Token Management and account surface. Authentication identity and wallet connection remain independent.

## Canonical roles

`OWNER`, `ADMIN`, `FINANCE`, `TOKEN_MANAGER`, `CREATOR`, `DEVELOPER`, `REVIEWER`, `MEMBER`, `VIEWER`.

Only `OWNER`, `ADMIN` and `TOKEN_MANAGER` qualify for token-administration authorization, and they still must pass resource, environment, authentication-assurance and risk policy checks.

## Wallet boundary

A connected wallet proves availability of an address/session context. It does not switch the authenticated SONIC account and does not authorize arbitrary transactions.

Role routes use stable slugs under `/token/management/roles/:slug`. Server authorization is authoritative; hiding a UI control is not an authorization mechanism.

## Realtime

Wallet balances, sale intent progress, receipts, market prices and notifications may arrive through `/ws/v1`. WebSocket events are projections only. On disconnect, clients recover from `/api/v1/realtime/events?cursor=...` and then reload authoritative resources.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/sonic-1.0.0-rc-production-architecture/product-and-wallet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.