@fased/fased 0.1.13 → 0.1.14

package/docs/start/bond-operator-economy.md

@@ -1,28 +1,28 @@
 ---
-summary: "How SAT mining, bond, payments, and operator status fit together."
+summary: "How SAT mining, bond, payments, and public trust roles fit together."
 read_when:
-  - You want one clear model for mining, bond, payments, and operator status
-  - You need the operator meaning of the Bond Operator and staking blocks
-title: "SAT Bond Operator Overview"
-sidebarTitle: "Bond operator"
+  - You want one clear model for mining, bond, payments, and trust roles
+  - You need the meaning of the Bond and staking blocks
+title: "SAT Bond Overview"
+sidebarTitle: "Bond"
 ---
 
-# SAT Bond Operator Overview
+# SAT Bond Overview
 
-This page is the clean operator model for the current SAT network stack.
+This page is the clean bond model for the current SAT network stack.
 
 Use it when you need one explanation of:
 
 - mining
 - bond
 - payment
-- operator status
+- public trust roles
 - what is already active
 - what is still gated behind later activation
 
 ## How this connects to the rest of Fased
 
-Read the operator stack in this order:
+Read the stack in this order:
 
 1. [Wallet](/plugins/crypto/wallet-page)
    Funds and secures the payment, mining, and bond-related wallets.
@@ -30,8 +30,8 @@ Read the operator stack in this order:
    Earns or stages SAT on the mining wallet.
 3. [Fased Network](/start/federation)
    Uses payment and bond posture to decide public network participation.
-4. Bond operator status
-   Adds bonded capabilities and reviewed service layers on top of that base runtime.
+4. Stronger bond status
+   Adds bonded capabilities and reviewed service layers on top of that agent setup.
 
 That is why this page does not replace Wallet, Mining, or Fased Network. It explains how those layers fit together economically.
 
@@ -40,16 +40,16 @@ That is why this page does not replace Wallet, Mining, or Fased Network. It expl
 The product split is:
 
 1. `Mining`
-   Mine or hold `SAT` through the mining runtime.
+   Mine or hold `SAT` through the mining app.
 2. `Bond`
-   Lock `SAT` to qualify for the bonded operator lane and narrow Fased Network capabilities.
+   Lock `SAT` to qualify for a stronger bond lane and narrow Fased Network capabilities.
 3. `Bond staking`
-   Active operator-bond lane where qualified locked `SAT` can accrue a
+   Active bond-distributor lane where qualified locked `SAT` can accrue a
    proportional claimable amount from staking-lane SAT when distribution is
    enabled.
 4. `Agent wallet`
    Handles real work on the normal payment rail, typically stable assets such as `USDC`.
-5. `Operator status`
+5. `Trust status`
    Later accounting, reserve, reconciliation, and fee logic on top of bonded service work.
 
 The important boundary is:
@@ -58,13 +58,13 @@ The important boundary is:
 - bond does not replace the Agent wallet payment rail
 - bond staking is not mining; it is a locked-SAT distributor lane
 - staking amounts are variable and depend on protocol activity, eligible bond weight, and distributor accounting
-- operator status does not mint SAT from mining emissions
+- trust status does not mint SAT from mining emissions
 
-For the shared short definitions, see [Operator glossary](/start/operator-glossary).
+For the shared short definitions, see [Fased glossary](/start/operator-glossary).
 
 ## What bond means in practice
 
-A bonded operator is a self-hosted runtime that:
+A stronger bonded setup is a self-hosted agent setup that:
 
 - proves control of a Vault wallet assigned to SAT bond
 - holds an active on-chain bond position
@@ -77,7 +77,7 @@ Current first-layer capability labels are:
 - `directory.priority.basic`
 - `routing.capacity.basic`
 
-Current operator lanes built on top of that are:
+Current stronger lanes built on top of that are:
 
 - public seller lane
 - routing-capacity lane
@@ -90,31 +90,31 @@ So today, bond mainly means:
 - publish public offers
 - improve discovery posture
 - qualify for stronger public routing or hosted reachability checks
-- become eligible for later operator service roles such as verifier or reviewer
+- become eligible for later service roles such as verifier or reviewer
 
-## Operator-bond staking
+## Bond staking
 
-Operator-bond staking is the claimable SAT distribution layer above basic bond.
+Bond staking is the claimable SAT distribution layer above basic bond.
 
 The clean model is:
 
 ```text
-Mining       = capital + runtime + cycles
-Bond         = locked SAT + operator trust
+Mining       = capital + mining app + cycles
+Bond         = locked SAT + public trust
 Bond staking = eligible locked SAT + variable network-support distribution
 Fased roles  = seller lanes, verifier/dispute roles, anti-spam, routing priority
 ```
 
-Current starting policy:
+Current starting rules:
 
 | Layer                 | Starting rule                                         |
 | --------------------- | ----------------------------------------------------- |
 | Basic bond            | `25 SAT`                                              |
-| Operator/staking bond | `500 SAT`                                             |
+| Stronger/staking bond | `500 SAT`                                             |
 | Unlock delay          | `216,000` slots                                       |
 | Distribution          | SAT-only from the existing `5%` staking emission lane |
 
-The first-year operator/staking threshold is intentionally serious but not
+The first-year stronger/staking threshold is intentionally serious but not
 whale-only. It can mature later as mining gets harder, SAT distribution
 broadens, and liquidity improves; `1,000 SAT` is a later-network candidate, not
 the T0 default.
@@ -123,7 +123,7 @@ the T0 default.
 
 1. Move SAT to the Vault wallet selected for Fased Network bond.
 2. Open or increase the bond from the Fased Network page.
-3. Once the bond is active and at or above the operator threshold, it becomes staking-eligible.
+3. Once the bond is active and at or above the stronger-bond threshold, it becomes staking-eligible.
 4. The SAT distributor lane feeds the distributor through protocol housekeeping.
 5. The Bond Operator card shows:
    - Vault balance: free SAT/SOL still in the Vault wallet
@@ -137,7 +137,7 @@ to the Vault wallet if anything is available. There is no separate user-facing
 sync button in the normal flow.
 
 The claim is manual by design. Auto-claim can be added later only as an explicit
-wallet policy with a minimum claim threshold and fee cap, because automatic
+wallet rule with a minimum claim threshold and fee cap, because automatic
 claiming signs transactions and pays network fees in the background.
 
 ### Fased Network card meanings
@@ -148,7 +148,7 @@ claiming signs transactions and pays network fees in the background.
 | Seen          | last observed network status timestamp                       |
 | Vault balance | free SAT/SOL in the Vault wallet, not the locked bond amount |
 | Bond position | on-chain position PDA for locked SAT                         |
-| Bonded        | SAT locked as operator inventory                             |
+| Bonded        | SAT locked in this bond position                             |
 | Claimable     | this position's synced distributor SAT amount                |
 | Pool          | staking distributor vault balance before claims              |
 
@@ -162,11 +162,11 @@ The SAT distributor uses proportional index accounting:
 - each active bond has staking weight equal to its active bonded SAT;
 - new distributor SAT increases the distributor accounting index;
 - a bond position records its accounting debt and claimable amount when it syncs;
-- another operator claiming first does not take this position's synced share;
+- another bond claiming first does not take this position's synced share;
 - synced amounts remain claimable until claimed or until protocol state is changed by
   the owner through normal bond lifecycle actions.
 
-Unlocking a bond removes future staking weight, but the runtime syncs the
+Unlocking a bond removes future staking weight, but Fased syncs the
 position around bond lifecycle actions so already-accrued amounts are preserved
 for claim.
 
@@ -175,9 +175,9 @@ The UI can show the amount claimed by the current click and current Vault
 balance. A lifetime-claimed card would require wallet transfer indexing or a
 future protocol field.
 
-## What operator status adds
+## What trust status adds
 
-Operator status is the reviewed service layer on top of bonded operator work.
+Trust status is the reviewed service layer on top of bonded public work.
 
 The intended public-service lanes are:
 
@@ -194,36 +194,36 @@ The review flow is:
 3. review or dispute evidence stays attached to the selected offer flow
 4. reconciliation reports can compare expected and observed state
 
-Any automated release, penalty, or operator-credit policy remains a later
+Any automated release, penalty, or credit rule remains a later
 explicit rollout decision.
 
-## Threshold and tier policy
+## Threshold and tier rules
 
-Bond tier thresholds are protocol policy, not just a UI preference.
+Bond tier thresholds are protocol rules, not just a UI preference.
 
 In the current architecture they are decided by:
 
-- SAT bond policy itself
+- SAT bond rules themselves
 - the canonical on-chain bond state format
-- the runtime and Fased Network services that interpret bond amount and tier
+- Fased and Fased Network services that interpret bond amount and tier
 
-That means changing minimum or maximum bond posture requires coordinated policy
-and runtime changes.
+That means changing minimum or maximum bond posture requires coordinated rule
+and app changes.
 
 It requires a coordinated update across:
 
-- SAT bond policy and state interpretation
-- runtime consumers and UI defaults
+- SAT bond rules and state interpretation
+- Fased consumers and UI defaults
 - Fased Network verification and capability rules
 - public docs and rollout guidance
 
 If SAT price changes materially over time, the right long-term architecture is a
-versioned tier-policy surface instead of duplicated hard-coded thresholds in
+versioned tier-rule surface instead of duplicated hard-coded thresholds in
 multiple places.
 
 ## How the current system is split
 
-### SAT bond policy
+### SAT bond rules
 
 Owns:
 
@@ -234,14 +234,14 @@ Owns:
 
 On chain, this is split into:
 
-- bond tier policy PDA for thresholds, unlock delay, policy version, and update authority
-- bond position PDA for one operator's status, tier, amount, and unlock state
+- bond tier rules PDA for thresholds, unlock delay, version, and update authority
+- bond position PDA for one position's status, tier, amount, and unlock state
 - bond vault ATA owned by the bond position PDA, holding the locked SAT
 
-The selected Vault wallet pays transaction fees and provides the SAT being locked. Bond
-policy does not mint SAT and does not pay mining cycles.
+The selected Vault wallet pays transaction fees and provides the SAT being
+locked. Bond rules do not mint SAT and do not pay mining cycles.
 
-### Fased runtime
+### Fased
 
 Owns:
 
@@ -249,7 +249,7 @@ Owns:
 - onboarding and CLI bond controls
 - bond proof signing and submission
 - Fased Network UI and bonded-lane visibility
-- local operator status and read-only evidence surfaces
+- local trust status and read-only evidence surfaces
 
 ### Fased Network services
 
@@ -257,7 +257,7 @@ Owns:
 
 - bond challenge issuance and proof verification
 - derived scopes and quota bands
-- seller, routing, hosted-edge, directory, and artifact operator status
+- seller, routing, hosted-edge, directory, and artifact trust status
 - service evidence, review/dispute state, and reconciliation reports
 
 ## What is live today
@@ -273,7 +273,7 @@ The current tranche is already real in these areas:
 - hosted-edge lane
 - directory or indexer lane
 - artifact-availability lane
-- operator status storage and read-only reporting
+- trust status storage and read-only reporting
 
 ## What is still gated
 
@@ -283,9 +283,9 @@ The honest remaining gate is:
 
 - retained-history requirements must mature
 - evidence must be reviewed
-- only then can any automated fee, penalty, or operator-credit policy be considered
+- only then can any automated fee, penalty, or credit rule be considered
 
-Routing fees and penalty-style enforcement remain later-policy work.
+Routing fees and penalty-style enforcement remain later-rule work.
 
 ## Current Fased Network UI shape
 
@@ -308,7 +308,7 @@ The surfaces are:
 
 Important boundary:
 
-- Fased Network shows operator identity and bond posture
+- Fased Network shows public identity and bond posture
 - staking claim belongs with bond because it pays the selected Vault wallet
 - payment evidence, review, dispute, and offer evidence belong with Marketplace
   or a selected offer
@@ -326,24 +326,24 @@ For the dedicated guide, see [Offers and Marketplace](/start/offers-marketplace)
 
 The next cleanups worth doing are:
 
-1. unify bond threshold policy into one canonical source instead of relying on
+1. unify bond threshold rules into one canonical source instead of relying on
    duplicated consumer assumptions
 2. keep UI focused on lanes and capabilities instead of raw scope strings
-3. move any automated fee, release, or penalty policy behind explicit signed packets
+3. move any automated fee, release, or penalty rule behind explicit signed packets
 4. keep routing fees deferred until routing measurements are mature enough to justify them
 
 ## Practical summary
 
 - mine SAT to obtain or hold the asset through protocol participation
-- bond SAT to qualify for operator participation
+- bond SAT to qualify for stronger public participation
 - handle real orders on the normal payment rail
-- let operator status track explicit service evidence around bonded work
+- let trust status track explicit service evidence around bonded work
 
 That is the current product and architecture boundary.
 
 ## Related docs
 
-- [Operator glossary](/start/operator-glossary)
+- [Fased glossary](/start/operator-glossary)
 - [Wallet](/plugins/crypto/wallet-page)
 - [Mining](/plugins/crypto/mining-page)
 - [Fased Network](/start/federation)

package/docs/start/control-ui-setup.md

@@ -2,7 +2,7 @@
 summary: "What setup belongs in onboarding, Control UI pages, Advanced Config, and CLI"
 read_when:
   - You finished onboarding and need to make the agent usable
-  - You are deciding where to add providers, skills, channels, services, hooks, or memory
+  - You are deciding where to add providers, skills, chat apps, services, hooks, or saved context
   - You are confused by overlap between Control UI pages and Advanced Config
 title: "Control UI Setup Model"
 sidebarTitle: "Control UI Setup"
@@ -36,7 +36,7 @@ The first browser setup pass should start from the selected Agent:
 
 <Steps>
   <Step title="/agents">
-    Create or select the Agent that will own chat, channel routes, tasks, and memory.
+    Create or select the Agent that will own chat, chat app routes, tasks, and saved context.
   </Step>
   <Step title="Agent > Models">
     Connect provider auth if needed, then choose primary, fallback, and task models.
@@ -51,7 +51,7 @@ The first browser setup pass should start from the selected Agent:
     Connect external APIs such as web/search, Gmail, Calendar, GitHub, or browser/media.
   </Step>
   <Step title="Agent > Memory">
-    Enable session-memory and review per-Agent archive/QMD state.
+    Enable saved session context and review per-Agent archive state.
   </Step>
   <Step title="Agent > Tasks">
     Create saved tasks, triggers, workflows, graphs, programs, and templates.
@@ -96,20 +96,20 @@ Then use the browser pages for product setup:
 
 <CardGroup cols={2}>
   <Card title="/agents">
-    Create or select an Agent and attach model, skills, services, channels,
-    memory, tasks, tools, sessions, and wallet policy.
+    Create or select an Agent and attach model, skills, services, chat apps,
+    saved context, tasks, tools, sessions, and wallet controls.
   </Card>
   <Card title="/extensions">
     Review runtime plugins, source trust, dependencies, scanner warnings, and advanced extension setup.
   </Card>
   <Card title="/usage">
-    Review local model usage by provider, model, Agent, session, task, channel, and source.
+    Review local model usage by provider, model, Agent, session, task, chat app, and source.
   </Card>
   <Card title="/notifications">
     Configure notification routing and recent in-app/external delivery.
   </Card>
   <Card title="/wallet">
-    Review wallet policy, approvals, balances, custody, and signer health.
+    Review wallet controls, approvals, balances, custody, and signer health.
   </Card>
   <Card title="/mining">
     Operate SAT mining readiness, capital, commit, recovery, and history.
@@ -135,19 +135,18 @@ with `/agents` when the Gateway is already online.
 
 ## Agent Means
 
-In the Control UI, an Agent is the routeable workspace identity you actually
-operate.
+In the Control UI, an Agent is the workspace profile you actually operate.
 
 It can have:
 
 - model and fallbacks
 - skills
 - services
-- channels
-- memory settings
+- chat apps
+- saved context settings
 - scheduled tasks
 - files and workspace context
-- wallet policy
+- wallet controls
 
 Examples:
 
@@ -156,19 +155,20 @@ Examples:
 - Mining Operator
 - Operations Reviewer
 
-Channels and scheduled tasks should route to a configured Agent. Subagents are
-different: they are internal runtime workers used during a task, not normal
-channel routing targets.
+Channels and scheduled tasks should route to a configured Agent. In the UI,
+Channels means chat app connections such as Telegram, Discord, and WhatsApp.
+Subagents are different: they are internal runtime workers used during a task,
+not normal chat routing targets.
 
 `Agent > Tasks` is the selected Agent's saved-work control surface. Create a
 **Task** for scheduled work first. Add Triggers, Workflows, Graphs, Programs,
 or Templates only when the run needs that structure.
 
 Run history can include scheduled runs plus records mirrored from webhooks,
-channels, subagents/ACP, CLI/system runs, media generation, wallet approvals,
+chat apps, subagents/ACP, CLI/system runs, media generation, wallet approvals,
 Marketplace, mining, and workflows. It is audit data, not the primary task list.
 Use the owning page for the actual domain operation: Wallets for signing,
-Marketplace for orders/disputes, Mining for mining control, Channels for
+Marketplace for orders/disputes, Mining for mining control, Channels for chat
 routes/delivery, and Services/Media for connector setup.
 
 ## Skills, Extensions, Channels, Services
@@ -182,8 +182,8 @@ configure, and allow it from `Agent > Skills`.
 
 **Extension**
 
-Runtime plugin code that can add tools, channels, hooks, schemas, commands, or
-UI panels. Review it in `/extensions`.
+Plugin code that can add tools, channels, hooks, schemas, commands, or UI
+panels. Review it in `/extensions`.
 
 **Channel**
 
@@ -197,7 +197,7 @@ browser/media, or a plugin-reported API. Connect it from `Agent > Services`.
 
 **Hook**
 
-Background automation around runtime events. Review hook packs in `/extensions`;
+Background automation around Fased events. Review hook packs in `/extensions`;
 Agent memory archive control lives in `Agent > Memory`.
 
 Skill setup is intentionally split by responsibility but exposed in one Agent
@@ -206,7 +206,7 @@ surface:
 - **Agent > Skills**: create workspace skills, review plugin-catalog installs, save
   skill config, fix dependencies, edit skill files, and allow/deny skills for
   that Agent.
-- **Agent > Tools**: allow or deny runtime tools exposed by core code, services,
+- **Agent > Tools**: allow or deny tools exposed by core code, services,
   channels, or extensions.
 - **Agent > Services**: connect API credentials a skill/tool depends on.
 - **Wallet > Skill Grants tab**: grant narrow Agent-wallet actions for reviewed
@@ -223,10 +223,10 @@ fallback, not the first-run path.
 task needs web search, GitHub, Gmail/Google Workspace, Firecrawl, model auth,
 channel delivery, or a configured skill, it should pause in `needs-access` and
 point back to the matching setup surface instead of repeatedly running. Access
-is still constrained by that Agent's Tools, Skills, wallet policy, and task
+is still constrained by that Agent's Tools, Skills, wallet controls, and task
 policy.
 
-## Memory
+## Memory (Saved Context)
 
 Memory has multiple pieces:
 

package/docs/start/fased.md

@@ -1,24 +1,24 @@
 ---
-summary: "Set up Fased Agent with channels, wallets, Fased Network, and Satcoin mining."
+summary: "Set up Fased Agent with tasks, tools, wallets, Fased Network, and Satcoin mining."
 read_when:
   - Onboarding a new assistant instance
   - Reviewing safety/permission implications
-  - Moving from first chat to a real operator setup
+  - Moving from first chat to a real agent setup
 title: "Fased Agent Setup"
 ---
 
 # Fased Agent Setup
 
-Fased Agent is the agent you run through one of two setup profiles:
+Fased Agent is the agent workbench you run through one of two setup profiles:
 
 - **Local** for your own computer. Use Terminal on macOS, WSL2 Ubuntu on
   Windows, or your Linux distro terminal.
 - **VPS Hosting** for an always-on server. Ubuntu LTS is the recommended first
   VPS target.
 
-Start with the Gateway and browser dashboard, then add models, skills,
-services, channels, wallets, Fased Network, or Satcoin mining only when they
-have a specific job.
+Start with the Gateway and browser dashboard, then add models, skills, services,
+chat apps, tasks, wallets, Fased Network, or Satcoin mining only when they have
+a specific job.
 
 Use this page after first boot to turn a working install into a real Agent
 setup.
@@ -30,8 +30,8 @@ setup.
   <Card title="Control UI Setup" href="/start/control-ui-setup" icon="layout-dashboard">
     See what belongs in onboarding, Agent setup, Services, Tasks, and Advanced Config.
   </Card>
-  <Card title="Operator Glossary" href="/start/operator-glossary" icon="book-open">
-    Learn the shared wallet, mining, bond, and Fased Network terms.
+  <Card title="Fased Glossary" href="/start/operator-glossary" icon="book-open">
+    Learn the shared wallet, mining, bond, and network terms.
   </Card>
 </Columns>
 
@@ -39,7 +39,7 @@ setup.
 
 ```mermaid
 flowchart TB
-  entry["Channels / Control UI"] --> gateway["Gateway"]
+  entry["Control UI / chat apps"] --> gateway["Gateway"]
   gateway --> agent["Fased Agent + workspace"]
   agent --> tools["Tools + plugins"]
   agent --> wallets["Wallet use"]
@@ -48,10 +48,10 @@ flowchart TB
 
   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 recommended order is:
@@ -59,7 +59,7 @@ The recommended order is:
 1. make the install stable
 2. connect one trusted model
 3. send the first browser chat
-4. add skills, services, memory, channels, and tasks
+4. add skills, services, memory, chat apps, and tasks
 5. add wallets, Fased Network, or Satcoin mining only when the base agent is ready
 
 ## Conservative Defaults
@@ -68,7 +68,7 @@ Start conservative:
 
 - keep the Gateway private by default
 - use Tailscale for hosted/admin access
-- connect one trusted channel before adding public routes
+- connect one trusted chat app before adding public routes
 - keep wallet and mining workflows separate from normal chat
 - review skills and services before allowing them for an Agent
 
@@ -91,7 +91,7 @@ Then work from the selected Agent:
 | `Agent > Skills`   | Create, install, configure, review, and allow Agent skills          |
 | `Agent > Services` | Web/search, Gmail, Calendar, GitHub, browser/media, and custom APIs |
 | `Agent > Channels` | Chat app setup and routing to this Agent                            |
-| `Agent > Memory`   | Session-memory and archive state                                    |
+| `Agent > Memory`   | Saved session context and archive state                             |
 | `Agent > Tasks`    | Saved tasks, triggers, workflows, graphs, programs, and templates   |
 
 Dashboard is the launch/status board. Use `/agents` for real setup.
@@ -106,8 +106,8 @@ The default workspace is:
 
 Fased creates starter files such as `AGENTS.md`, `SOUL.md`, `TOOLS.md`,
 `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`, `MEMORY.md`, and `memory/` when the
-workspace is new. Treat this folder like the agent's operational memory and
-keep it private.
+workspace is new. Treat this folder like the agent's private working context
+and keep it private.
 
 Useful links:
 
@@ -117,15 +117,15 @@ Useful links:
 
 ## Wallet, Network, And Satcoin
 
-Fased works without wallets or Satcoin. Add wallets, Fased Network, or Satcoin modules
-only when they have a specific job:
+Fased works without wallets or Satcoin. Add wallets, Fased Network, or Satcoin
+modules only when they have a specific job:
 
-| Path           | When to use it                                                                      |
-| -------------- | ----------------------------------------------------------------------------------- |
-| Wallet use     | When the Agent needs reviewed sends, balances, receipts, or wallet-connected skills |
-| Fased Network  | When the Agent needs a public handle, route, offers, or operator history            |
-| Satcoin mining | When the Agent will mine, claim, and build public mining history                    |
-| Bond           | When bonded SAT should support a stronger operator role                             |
+| Path           | When to use it                                                                                           |
+| -------------- | -------------------------------------------------------------------------------------------------------- |
+| Wallet use     | When the Agent needs wallet roles, reviewed sends, balances, payment history, or wallet-connected skills |
+| Fased Network  | When the Agent needs a public handle, services, or trust                                                 |
+| Satcoin mining | When the Agent will mine, claim, and build mining history                                                |
+| Bond           | When held SAT should support a stronger trust role                                                       |
 
 Relevant pages:
 
@@ -133,20 +133,20 @@ Relevant pages:
 - [Fased Network](/start/federation)
 - [Mining](/plugins/crypto/mining-page)
 - [Advanced SAT mining](/plugins/crypto/mining-advanced)
-- [Bond operator overview](/start/bond-operator-economy)
+- [Bond overview](/start/bond-operator-economy)
 
-## Channels And Tasks
+## Chat Apps And Tasks
 
-Connect channels only after the browser chat works. Route each account, topic,
+Connect chat apps only after the browser chat works. Route each account, topic,
 or guild to a selected Agent from `Agent > Channels`.
 
-Use `Agent > Tasks` for saved work definitions. Run history is audit data; the
-owning domain page still controls the operation:
+Use `Agent > Tasks` for saved work definitions. Activity history helps you
+understand what happened; the owning domain page still controls the operation:
 
-- Mining controls stay in Mining
+- Mining setup stays in Mining
 - Wallet signing stays in Wallet
 - Marketplace orders stay in Marketplace
-- Channel routing stays in Channels
+- Chat app routing stays in Channels
 - Service auth stays in Services
 
 ## Operations Checks