@fased/fased 0.1.13 → 0.1.14

package/docs/cli/index.md

@@ -1,5 +1,5 @@
 ---
-summary: "CLI reference for the self-hosted Fased runtime, Agent setup, diagnostics, channels, wallets, network, and mining."
+summary: "CLI reference for Fased setup, diagnostics, chat apps, wallets, network, and mining."
 read_when:
   - Adding or modifying CLI commands or options
   - Documenting new command surfaces
@@ -8,12 +8,12 @@ title: "CLI Reference"
 
 # CLI reference
 
-`fased` is the control surface for the self-hosted runtime. It is not just a
-gateway wrapper. The CLI manages:
+`fased` is the scriptable control surface for Fased. It is not just a Gateway
+wrapper. The CLI manages:
 
 - onboarding and install flows
 - config and secrets
-- Agent workspaces, channel accounts, routing, skills, services, tools, and tasks
+- Agent workspaces, chat app accounts, routing, skills, services, tools, and tasks
 - live gateway control and diagnostics
 - plugins, skills, and hooks
 - wallets, Fased Network, and mining where enabled

package/docs/concepts/architecture.md

@@ -48,8 +48,8 @@ flowchart TD
 ```
 
 The Gateway is the control plane. Agents own work identity and policy. Sessions,
-Tasks, tools, skills, memory, channels, and nodes attach through that selected
-Agent instead of becoming separate product owners.
+Tasks, tools, skills, saved context, chat apps, and nodes attach through that
+selected Agent instead of becoming separate product owners.
 
 ## Components and flows
 

package/docs/concepts/features.md

@@ -1,5 +1,5 @@
 ---
-summary: "Fased capabilities across gateway, channels, agents, wallets, Fased Network, SAT, offers, and operator workflows."
+summary: "Fased capabilities across the Gateway, chat apps, Agents, wallets, Fased Network, SAT, offers, and marketplace workflows."
 read_when:
   - You want the clean product-level feature list
   - You want to see what is live now versus what is still roadmap
@@ -16,42 +16,42 @@ Use it when you want the major capabilities without digging through lower-level
 
 <Columns>
   <Card title="Gateway and control" icon="monitor">
-    Browser-first control surface, CLI, runtime policy, sessions, and logs in one self-hosted stack.
+    Browser-first Control UI, CLI, sessions, logs, and safety controls in one setup.
   </Card>
-  <Card title="Channels" icon="message-square">
-    One runtime can serve many messaging surfaces at once instead of splitting setup across isolated bots.
+  <Card title="Chat apps" icon="message-square">
+    One Gateway can serve many messaging apps at once instead of splitting setup across isolated bots.
   </Card>
   <Card title="Wallet, Fased Network, and SAT" icon="coins">
-    Wallet policy, SAT mining, Fased Network profile, and bond controls are optional operator modules in the same runtime.
+    Wallet controls, SAT mining, Fased Network profile, and bond controls are optional modules in the same setup.
   </Card>
-  <Card title="Offers and operator workflows" icon="store">
-    Local offers, public discovery, and reviewed operator readiness live in the control surface.
+  <Card title="Marketplace workflows" icon="store">
+    Local offers, public discovery, and reviewed service readiness live in the Control UI.
   </Card>
   <Card title="Nodes and devices" icon="smartphone">
-    Mobile and local-device nodes extend the runtime to cameras, audio, screens, and Canvas-style surfaces.
+    Mobile and local-device nodes extend Fased to cameras, audio, screens, and Canvas-style surfaces.
   </Card>
   <Card title="Automation and plugins" icon="plug">
-    Skills, plugins, hooks, scheduled tasks, and sandboxed tools let the runtime grow into operator-specific workflows.
+    Skills, plugins, hooks, scheduled tasks, and sandboxed tools let the agent grow into your workflows.
   </Card>
 </Columns>
 
 ## Major features available now
 
-### 1. Self-hosted gateway runtime
+### 1. Gateway you control
 
-Fased gives you one runtime that you control on your own machine or server.
+Fased gives you one Gateway that you control on your own machine or server.
 
 Current core surfaces:
 
-- Dashboard, Chat, Agents, Logs, Usage, and Advanced operator surfaces
-- CLI for onboarding, status, channels, wallets, Fased Network, and ops work
+- Dashboard, Chat, Agents, Logs, Usage, and Advanced admin surfaces
+- CLI for onboarding, status, chat apps, wallets, Fased Network, and ops work
 - session management and chat history
-- routing, logs, runtime health, and restart-safe service operation
-- local versus hosting profiles for different operator postures
+- routing, logs, health checks, and restart-safe service operation
+- Local versus Hosting profiles for different setup needs
 
-### 2. Multi-channel messaging and remote access
+### 2. Chat apps and remote access
 
-Fased can expose one runtime across many communication surfaces.
+Fased can connect one Agent to many communication surfaces.
 
 Current channel and messaging capabilities include:
 
@@ -79,13 +79,12 @@ Current channel and messaging capabilities include:
 - images, audio, and document handling
 - long-response streaming and chunking
 
-The product point is that the same self-hosted runtime can serve many channels
-at once.
+The product point is that the same Gateway can serve many chat apps at once.
 
-### 3. Agent runtime and routing
+### 3. Agent work and routing
 
 Fased is not just a message relay.
-It is an agent runtime with operator controls.
+It is an agent setup with safety controls.
 
 Current agent capabilities include:
 
@@ -93,13 +92,13 @@ Current agent capabilities include:
 - isolated sessions by workspace, sender, or agent role
 - memory and session compaction
 - tool use and plugin tool registration
-- embedded Fased agent runtime over the gateway RPC path
+- embedded Fased agent over the Gateway RPC path
 - provider auth and subscription/OAuth paths where supported
 - sandbox and tool-policy controls
 
-### 4. Wallet runtime
+### 4. Wallet controls
 
-The wallet layer is a real product surface with inventory, policy, and signer
+The wallet layer is a real product surface with inventory, controls, and signer
 health.
 
 Current wallet features include:
@@ -107,32 +106,33 @@ Current wallet features include:
 - wallet inventory and role visibility
 - send flows and recent wallet activity
 - signer health checks
-- shared wallet policy and spend limits
+- shared wallet controls and spend limits
 - Agent wallet visibility
 - mining wallet visibility
 - bond Vault visibility
 
-The wallet page is the inventory and policy surface. Mining control and bond
+The wallet page is the inventory and controls surface. Mining control and bond
 lifecycle actions live on their own pages.
 
 ### 5. SAT mining
 
-SAT mining is a first-class capability in the runtime.
+SAT mining is a first-class capability in Fased.
 
 Current mining features include:
 
 - SAT mining page and controls
 - capital, commit, and cycle visibility
 - singleton Mining wallet assignment
-- cycle history and operator activity
-- restart-aware runtime support for continued operator use
+- cycle history and activity
+- restart-aware support for continued use
 
 Mining is the SAT issuance and participation layer. Payments and bond lifecycle
 controls remain separate.
 
 ### 6. Fased Network profile and public participation
 
-Fased Network is the network participation layer on top of a healthy runtime.
+Fased Network is the network participation layer on top of a healthy Fased
+setup.
 
 Current Fased Network features include:
 
@@ -140,10 +140,10 @@ Current Fased Network features include:
 - trust and hosted status visibility
 - hosted-route health awareness
 - public participation readiness checks
-- self-hosted runtime profile tied to the same operator stack
+- profile tied to the same Fased setup
 
-Fased Network is how the runtime becomes a public network participant.
-Local runtime control stays on the local/runtime surfaces.
+Fased Network is how the agent becomes a public network participant.
+Local control stays on the local setup surfaces.
 
 ### 7. Bonded operator path
 
@@ -168,7 +168,7 @@ Current first-layer bonded capabilities include:
 
 Fased now includes the operator surfaces for local offers and public discovery.
 
-Current offer/operator surfaces include:
+Current marketplace surfaces include:
 
 - local offer publishing and management
 - public marketplace discovery
@@ -204,7 +204,7 @@ What is true right now:
 
 ### 10. Plugins, skills, and automation
 
-Fased supports operator-specific extension and automation paths.
+Fased supports setup-specific extension and automation paths.
 
 Current extension features include:
 
@@ -219,7 +219,7 @@ Current extension features include:
 
 ### 11. Nodes and device surfaces
 
-The runtime can extend into paired device and node surfaces.
+Fased can extend into paired device and node surfaces.
 
 Current node features include:
 
@@ -233,8 +233,8 @@ Current node features include:
 
 If you want the shortest product summary, read it like this:
 
-- `Gateway`: self-hosted runtime, CLI, browser UI, health, sessions, logs
-- `Channels`: remote chat surfaces across many messaging platforms
+- `Gateway`: the service you run, CLI, browser UI, health, sessions, logs
+- `Channels`: chat apps across many messaging platforms
 - `Agent runtime`: routing, tools, memory, sessions, policy
 - `Wallet`: inventory, signer health, send flows, wallet-role visibility
 - `Mining`: SAT issuance and mining operations
@@ -242,7 +242,7 @@ If you want the shortest product summary, read it like this:
 - `Bond`: SAT-backed operator eligibility and proof
 - `Offers`: local publishing and remote discovery
 - `Operator status`: evidence and controlled maturity path
-- `Nodes`: mobile and device-linked runtime surfaces
+- `Nodes`: mobile and device-linked surfaces
 - `Plugins and automation`: extension and workflow system
 
 ## Roadmap, not current features
@@ -256,7 +256,7 @@ The next public roadmap lanes are:
 - reviewed market automation lanes
 - news and market-intelligence tools
 
-See [Roadmap](/reference/roadmap) for that next tranche.
+See [Roadmap](/reference/roadmap) for the next group of work.
 
 ## Related docs
 

package/docs/concepts/model-providers.md

@@ -76,12 +76,12 @@ Use this path after onboarding:
    model refs.
 3. `/chat`: talk to the selected Agent. The model picker can override the model
    for the current chat session when the selected provider route is usable.
-4. **Agent > Channels**: connect apps such as Telegram or Discord and route each channel
+4. **Agent > Channels**: connect apps such as Telegram or Discord and route each
    account/topic/guild to the selected Agent.
 
-The Agent owns model defaults, skills, services, memory, channels, tasks,
-and wallet policy. Chat and channels both talk to an Agent; they are different
-delivery surfaces for the same routeable setup.
+The Agent owns model defaults, skills, services, saved context, chat app
+routes, tasks, and wallet controls. Browser chat and connected chat apps both
+talk to an Agent; they are different delivery surfaces for the same setup.
 
 ```mermaid
 flowchart TD

package/docs/docs.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://mintlify.com/docs.json",
   "name": "Fased",
-  "description": "Fased docs for user-run agents: setup, tasks, wallets, skills, memory, channels, Satcoin mining, and Fased Network.",
+  "description": "Fased docs for the agent you run yourself: setup, chat, tasks, tools, wallets, Satcoin mining, and Fased Network.",
   "theme": "mint",
   "modeToggle": {
     "default": "dark"

package/docs/gateway/authentication.md

@@ -20,8 +20,8 @@ mode, and see [Gateway security](/gateway/security) for page and API protection.
 
 For normal browser setup, open the selected Agent and use **Agent > Models**.
 That page owns provider sign-in, API-key entry, per-Agent model roles, and model
-selection. The CLI commands below are for automation, repair, or advanced
-operator workflows.
+selection. The CLI commands below are for automation, repair, or advanced setup
+workflows.
 
 See [/concepts/oauth](/concepts/oauth) for the full OAuth flow and storage
 layout.

package/docs/gateway/configuration-reference.md

@@ -2531,7 +2531,7 @@ Auth: `Authorization: Bearer <token>` or `x-fased-token: <token>`.
 
 - `POST /hooks/wake` → `{ text, mode?: "now"|"next-heartbeat" }`
 - `POST /hooks/agent` → `{ message, name?, agentId?, sessionKey?, wakeMode?,
-  deliver?, channel?, to?, model?, thinking?, timeoutSeconds? }`
+deliver?, channel?, to?, model?, thinking?, timeoutSeconds? }`
 - `sessionKey` from request payload is accepted only when
   `hooks.allowRequestSessionKey=true` (default: `false`).
 - `POST /hooks/<name>` → resolved via `hooks.mappings`

package/docs/gateway/heartbeat.md

@@ -53,6 +53,7 @@ Example config:
   Do not infer or repeat old tasks from prior chats.
   If nothing needs attention, reply HEARTBEAT_OK.
   ```
+
 - The heartbeat prompt is sent **verbatim** as the user message. The system
   prompt includes a “Heartbeat” section and the run is flagged internally.
 - Active hours (`heartbeat.activeHours`) are checked in the configured timezone.

package/docs/help/faq.md

@@ -1,5 +1,5 @@
 ---
-summary: "Compact FAQ for Fased setup, models, channels, wallets, tasks, and troubleshooting."
+summary: "Compact FAQ for Fased setup, models, chat apps, wallets, tasks, and troubleshooting."
 read_when:
   - Answering common setup, install, onboarding, or support questions
   - Triaging user-reported issues before deeper debugging
@@ -30,12 +30,12 @@ fased logs --follow
 Then open the owner page for the thing that failed:
 
 - Agent > Models for model/provider issues.
-- Agent > Channels for chat routes.
+- Agent > Channels for chat app routes.
 - Agent > Services for external APIs.
 - Agent > Skills and Agent > Tools for capability issues.
-- Agent > Memory for memory/QMD/session-memory state.
+- Agent > Memory for saved context, archive, and session-memory state.
 - Agent > Tasks for saved task definitions and runs.
-- Wallets, Mining, or Fased Network for crypto/operator state.
+- Wallets, Mining, or Fased Network for crypto and network state.
 
 ## I'm Stuck - What's The Fastest Way To Get Unstuck?
 

package/docs/help/index.md

@@ -9,9 +9,9 @@ title: "Help"
 # Help
 
 Use Help when something is broken, unclear, or hard to inspect. Normal setup
-still starts in the selected Agent: Models, Channels, Services, Skills, Tools,
-Memory, Tasks, Wallets, Mining, and Fased Network each have their own owner
-page.
+still starts in the selected Agent: Models, Channels (chat apps), Services,
+Skills, Tools, Memory, Tasks, Wallets, Mining, and Fased Network each have
+their own focused page.
 
 ## Fast path
 
@@ -33,7 +33,7 @@ flowchart TD
 
 <CardGroup cols={2}>
   <Card title="Troubleshooting" icon="wrench" href="/help/troubleshooting">
-    Symptom-first checks for no replies, gateway issues, channels, tasks, nodes, browser, wallet, mining, and Fased Network.
+    Symptom-first checks for no replies, gateway issues, chat apps, tasks, nodes, browser, wallet, mining, and Fased Network.
   </Card>
   <Card title="Diagnostics" icon="activity" href="/diagnostics/index">
     Where to use Logs, Usage, Advanced > Debug, Advanced > Nodes, diagnostic flags, and structured diagnostics.

package/docs/help/testing.md

@@ -351,24 +351,28 @@ FASED_LIVE_CLI_BACKEND=1 \
 Narrow, explicit allowlists are fastest and least flaky:
 
 - Single model, direct (no gateway):
+
   ```bash
   FASED_LIVE_MODELS="<provider/model>" \
     pnpm test:live src/agents/models.profiles.live.test.ts
   ```
 
 - Single model, gateway smoke:
+
   ```bash
   FASED_LIVE_GATEWAY_MODELS="<provider/model>" \
     pnpm test:live src/gateway/gateway-models.profiles.live.test.ts
   ```
 
 - Tool calling across several providers you actively support:
+
   ```bash
   FASED_LIVE_GATEWAY_MODELS="<provider/model>,<provider/model>" \
     pnpm test:live src/gateway/gateway-models.profiles.live.test.ts
   ```
 
 - Google focus (Gemini API key + Gemini CLI):
+
   ```bash
   FASED_LIVE_GATEWAY_MODELS="google/<model>" \
     pnpm test:live src/gateway/gateway-models.profiles.live.test.ts
@@ -449,6 +453,7 @@ If you rely on env keys exported in `~/.profile`, run local tests after
     BYTEPLUS_LIVE_TEST=1 \
     pnpm test:live src/agents/byteplus.live.test.ts
   ```
+
 - Optional model override: `BYTEPLUS_CODING_MODEL=<model-id>`
 
 ## Docker runners (optional “works in Linux” checks)

package/docs/images/screenshots/polished/README.md

@@ -0,0 +1,16 @@
+# Polished Walkthrough Screenshots
+
+These images are generated from the real screenshots in:
+
+- `/images/screenshots/local/`
+- `/images/screenshots/remote/`
+- `/images/screenshots/web/`
+
+They are framed for the beginner walkthrough so readers can see the important
+step without decoding tiny raw terminal or dashboard captures.
+
+Regenerate from the repository root:
+
+```bash
+bash docs/ops/marketing/template/assets/operator-school/screenshots/render-polished-screenshots.sh
+```

package/docs/index.md

@@ -1,5 +1,5 @@
 ---
-summary: "Fased is a user-run agent with a browser dashboard, channels, plugins, wallets, and optional Satcoin mining."
+summary: "Run your own agent for tasks, wallets, services, and SAT mining."
 read_when:
   - Introducing Fased to newcomers
 title: "Fased"
@@ -7,7 +7,11 @@ title: "Fased"
 
 # Fased
 
-**A user-run agent for tasks, channels, wallets, and mining.**
+**Run Agent. Mine SAT. Build Trust.**
+
+Fased Agent is the agent you run yourself. Start with tasks and the browser
+dashboard. Add wallets, services, Fased Network, and Satcoin mining when the
+work is ready for them.
 
 Start by choosing one of two setup profiles:
 
@@ -18,53 +22,48 @@ Start by choosing one of two setup profiles:
   too. Alpine, Arch, macOS, and FreeBSD are local/dev targets until their
   hosted hardening paths are validated separately.
 
-After the Gateway and browser dashboard are working, add channels, services,
-wallet features, Fased Network, or Satcoin mining only where you need them.
-
-Fased Agent gives you sessions, tools, memory, channels, plugins, and safety
-controls in the selected setup profile.
+After the Gateway and browser dashboard are working, add only what you need:
+wallets, services, Fased Network, or Satcoin mining.
 
-**Gateway + agent + channels + optional wallet, network, and mining paths.**
+**Gateway + dashboard + agent + wallets + services + mining when ready.**
 
 <Columns>
   <Card title="Get Started" href="/start/getting-started" icon="rocket">
-    Choose Local or VPS Hosting and bring up the Gateway.
+    Choose Local or VPS Hosting and bring up the agent.
   </Card>
   <Card title="Run the Wizard" href="/start/wizard" icon="sparkles">
-    Guided setup with `fased onboard` and pairing flows.
+    Guided setup with `fased onboard`.
   </Card>
   <Card title="Open the Control UI" href="/web/control-ui" icon="layout-dashboard">
-    Launch the browser dashboard for chat, config, and sessions.
+    Launch the browser dashboard and start working.
   </Card>
 </Columns>
 
 ## What is Fased?
 
-Fased is a **user-run agent**. You can use it immediately through the browser
-dashboard, then add channels, services, plugins, wallet features, Fased Network,
-and Satcoin mining as your setup grows.
+Fased is an **agent workbench you run yourself**. Use it first through the
+browser dashboard, then connect services, wallet features, Fased Network, and
+Satcoin mining as your setup grows.
 
-**Who is it for?** Developers, operators, and power users who want an agent they
-can message from the browser or chat apps, with local setup and clear safety
-boundaries.
+**Who is it for?** Developers, builders, and power users who want an agent they
+can run from their own computer or VPS.
 
 **What makes it different?**
 
-- **User-run agent**: choose Local for this computer or VPS Hosting for an always-on server
-- **Browser-first setup**: start in the Control UI before adding chat channels
-- **Skills and plugins**: agents can run useful workflows across tools and services
-- **Wallet features when enabled**: reviewed sends, receive links, receipts, and audit
-- **Fased Network**: public handles, routing, service discovery, and reviewed offers
-- **Optional Satcoin path**: mining can build public mining history
-- **Clear add-on paths**: wallets, Fased Network, Satcoin mining, and Marketplace stay separate from first chat
-
-The product shape is simple: start with the base agent, then add the advanced
-paths only when they have a specific job.
-
-- **Self-hosted**: runs on your own computer or your own VPS
-- **Multi-channel**: one Gateway serves WhatsApp, Telegram, Discord, and more simultaneously
-- **Agent-native**: built for coding agents with tool use, sessions, memory, and multi-agent routing
-- **Wallet-ready when enabled**: wallet actions can use limits, approvals, and audit
+- **Runs under your control**: choose Local for this computer or VPS Hosting for an always-on server
+- **Browser-first setup**: start in the Control UI
+- **Tasks and tools**: run useful work across services and plugins
+- **Wallets when enabled**: use wallet roles, reviewed sends, receive links, and payment history
+- **Fased Network**: make services easier to find and trust
+- **Satcoin mining**: mine SAT and build mining proof
+
+The product shape is simple: run the agent first, then add mining and network
+work when they have a specific job.
+
+- **Runs on your machine**: use your own computer or your own VPS
+- **Chat app ready**: connect WhatsApp, Telegram, Discord, and more when needed
+- **Built for agent work**: tasks, tools, memory, sessions, and multi-agent routing
+- **Wallet-ready when enabled**: wallet actions can use wallet roles and protected signing
 - **Network-ready when enabled**: Fased Network and Satcoin mining live beside the base agent
 - **Open source**: MIT licensed with preserved upstream and third-party notices
 
@@ -76,7 +75,7 @@ Hosting. If you manage Node yourself, use Node 24, or Node 22.14+ with
 
 ```mermaid
 flowchart TD
-  entry["Channels / Control UI"] --> gateway["Gateway"]
+  entry["Control UI / chat apps"] --> gateway["Gateway"]
   gateway --> agent["Fased Agent"]
   agent --> tools["Tools + skills"]
   agent --> wallets["Optional wallet use"]
@@ -85,25 +84,26 @@ flowchart TD
 
   classDef entry fill:#120605,stroke:#ff5a36,color:#ffffff;
   classDef core fill:#071018,stroke:#12cfff,color:#ffffff;
-  classDef operator fill:#20120a,stroke:#ffb020,color:#ffffff;
+  classDef addon fill:#20120a,stroke:#ffb020,color:#ffffff;
   class entry entry;
   class gateway,agent core;
-  class tools,wallets,network,mining operator;
+  class tools,wallets,network,mining addon;
 ```
 
-The Gateway keeps sessions, routing, channels, and agent behavior in one place.
+The Gateway keeps sessions, routing, chat app connections, and agent behavior in
+one place.
 
 ## Key capabilities
 
 <Columns>
-  <Card title="Multi-channel gateway" icon="network">
+  <Card title="Chat app gateway" icon="network">
     Add WhatsApp, Telegram, Discord, iMessage, and more when you want remote chat surfaces.
   </Card>
-  <Card title="User-run agent" icon="cpu">
-    Sessions, tools, memory, plugins, and safety controls in one setup profile.
+  <Card title="Agent you run" icon="cpu">
+    Sessions, tasks, tools, memory, and plugins in one setup profile.
   </Card>
-  <Card title="Plugin channels" icon="plug">
-    Add Mattermost and more with extension packages.
+  <Card title="Plugin integrations" icon="plug">
+    Add Mattermost and other integrations with extension packages.
   </Card>
   <Card title="Multi-agent routing" icon="route">
     Isolated sessions per agent, workspace, or sender.
@@ -210,14 +210,14 @@ Example:
   <Card title="Wallets, Fased Network, and SAT" href="/start/fased" icon="shield">
     Add wallets, network participation, and mining after first-run setup.
   </Card>
-  <Card title="Operator glossary" href="/start/operator-glossary" icon="book-open">
-    Learn the shared wallet, mining, Fased Network, bond, and operator terms.
+  <Card title="Fased glossary" href="/start/operator-glossary" icon="book-open">
+    Learn the shared wallet, mining, Fased Network, and bond terms.
   </Card>
   <Card title="Remote access" href="/gateway/remote" icon="globe">
     SSH and tailnet access patterns.
   </Card>
-  <Card title="Channels" href="/channels/telegram" icon="message-square">
-    Channel-specific setup for WhatsApp, Telegram, Discord, and more.
+  <Card title="Chat apps" href="/channels/telegram" icon="message-square">
+    Setup guides for WhatsApp, Telegram, Discord, and more.
   </Card>
   <Card title="Nodes" href="/nodes" icon="smartphone">
     iOS and Android nodes with pairing and Canvas.
@@ -231,7 +231,7 @@ Example:
 
 <Columns>
   <Card title="Full feature list" href="/concepts/features" icon="list">
-    Complete channel, routing, and media capabilities.
+    Complete chat app, routing, and media capabilities.
   </Card>
   <Card title="Multi-agent routing" href="/concepts/multi-agent" icon="route">
     Workspace isolation and per-agent sessions.
@@ -249,6 +249,6 @@ Example:
     Project origin and current attribution policy.
   </Card>
   <Card title="Roadmap" href="/reference/roadmap" icon="map">
-    What comes after the current wallet, Fased Network, and operator tranche.
+    What comes after the current wallet, Fased Network, and trust features.
   </Card>
 </Columns>