# Feature categories

![](/files/atey0J5HlJ3wvGkFkZk1)

This page explains how to think about Sudo's surface area using the same category model as the product inventory.

## Social / Viral

Growth and distribution mechanics: stories, invites, QR codes, channels, public discovery patterns, forwarding, and lightweight "share loops" embedded in chat.

## Web3 / Finance

Anything that touches assets, signing, or on-chain state: wallet onboarding, swaps, escrow, multisig, governance, validators, token creation/locks, payments inside premium, and Web3 affordances surfaced in chat (for example payment requests and transaction cards).

## Settings / Utility

Account management, personalization, storage hygiene, backups/exports, notifications, language, help, premium, and cross-cutting "make the app usable day-to-day" controls.

## Core Chat

The daily messaging substrate: inbox, threads, media, search inside chats, notifications per chat, and the composer behaviors users expect from a modern messenger.

## Privacy / Trust

Controls that reduce risk and increase confidence: encryption, verification flows, locks, permissions, blocking, disappearing messages, and wallet recovery surfaces (seed phrase reveal/confirm).

## AI / Bots

Conversational entry points that compress complex wallet operations into guided flows: explorer Q\&A, transaction history, alerts/watchers, approvals risk, and shortcuts to holdings/locks.

## See also

* [Feature inventory](/reference/feature-inventory.md)


---

# Agent Instructions: 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:

```
GET https://docx.sudochat.app/overview/feature-categories.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.