dexterm-cli 0.1.7 → 0.2.1

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-real-mode-your-strategy-s-trades-to-your.md

@@ -0,0 +1,31 @@
+---
+id: docs-live-trading-real-mode-your-strategy-s-trades-to-your
+title: Live trading › Real mode: your strategy's trades to your executor (0.2.0, experimental)
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: Real mode: your strategy's trades to your executor (0.2.0, experimental)
+anchor: real-mode-your-strategy-s-trades-to-your-executor-0-2-0-experimental
+url: https://dexterm.xyz/docs/live-trading#real-mode-your-strategy-s-trades-to-your-executor-0-2-0-experimental
+tags:
+  - docs
+  - live-trading
+  - real
+  - mode
+  - strategy
+  - trades
+  - executor
+  - experimental
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+In real mode (https://dexterm.xyz/docs/real-mode) a strategy you armed on your own terminal sends every buy and sell it decides to your executor as a LIVE TRADE FIRE signal: a local webhook, a command, a stream file or MCP (a bot cannot read another bot's messages), with a copy in your Telegram chat. Your executor holds the wallet and acts on it; dexterm still holds no key and signs nothing. Hard caps, a kill switch (`dexterm autotrade signal kill`) and receipts of what your executor did are all on your machine. Experimental; not financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-the-short-version.md

@@ -24,7 +24,7 @@ sources:
 date: 2026-10-16
 ---
 
-> **0.1.7, experimental:** dexterm never holds a key and never signs; live trading happens in the Telegram trading bot of your choice; dexterm 0.1.7 sends alerts and signals to your own bot and does not place orders in it yet; automated order forwarding is next (0.1.8). This path has not been exercised end to end on mainnet yet; testing continues.
+> **0.2.0, experimental:** dexterm never holds a key and never signs. Live trades happen in the executor you choose (a Telegram trading bot behind your own relay, or any script): in real mode (https://dexterm.xyz/docs/real-mode) your strategy sends it a signal for each trade, and it acts by its own rules. Not financial advice.
 
 - **dexterm never holds a key and never signs a transaction.** It has no trading wallet, no signer and no place to keep a private key. It builds no transaction and sends none.
 - **Live trading happens in a Telegram trading bot of your choice.** That bot holds its own wallet and places the orders. You pick it, you fund it, and its rules and fees are its own.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-using-a-trading-bot-with-dexterm.md

@@ -29,5 +29,3 @@ date: 2026-10-16
 2. Set up dexterm's own bot for your chat: `dexterm telegram setup`, then `dexterm telegram pair`. See Telegram (https://dexterm.xyz/docs/telegram). This is a separate bot that only talks to you.
 3. Run a strategy on paper (`dexterm autotrade run <id> --paper`). Its alerts arrive in your chat.
 4. When you want to act on one, do it in your trading bot.
-
-dexterm has not been tested with any particular trading bot.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-what-dexterm-does-not-do.md

@@ -24,7 +24,7 @@ sources:
 date: 2026-10-16
 ---
 
-- It does not place an order in your trading bot for you. In this version you act in the bot yourself.
+- It does not place an order in your trading bot for you. In real mode (https://dexterm.xyz/docs/real-mode) it sends your executor a signal; your executor places the order, by its own rules.
 - It does not hold, import, create, decrypt or ask for a private key or seed phrase. Anything that asks you for one is not dexterm.
 - It does not sign or send a transaction. `dexterm wallet link` only proves which wallet is yours with a signed **message** in Phantom; dexterm keeps the public key to show your address. It never asks Phantom to sign a transaction.
 - It does not know what your trading bot did. Positions, fills and P/L in dexterm are paper.

package/dist/packages/mcp/assets/kb/docs/docs-narratives-how-coins-are-grouped.md

@@ -0,0 +1,39 @@
+---
+id: docs-narratives-how-coins-are-grouped
+title: Memes and narratives (experimental) › How coins are grouped
+kind: docs
+page: narratives
+page_title: Memes and narratives (experimental)
+heading: How coins are grouped
+anchor: how-coins-are-grouped
+url: https://dexterm.xyz/docs/narratives#how-coins-are-grouped
+tags:
+  - docs
+  - narratives
+  - coins
+  - are
+  - grouped
+  - memes
+  - experimental
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/narratives.md
+date: 2026-10-16
+---
+
+1. **Normalise** the name and ticker (and the description or social handles when the data layer has them): leetspeak
+   (`Z0RP`), repeated letters (`ZOOOORP`), camelCase (`ZorpWifHat`), emoji (🐸 → frog), glued tickers split against a
+   vocabulary learned from other names (`BABYZORP` → baby + zorp), and copy-cat affixes (`BABY`, `MINI`, `2.0`, `INU`,
+   `AI`) kept as weak words so "Baby X" lands next to X.
+2. **Embed** each coin with a local model. The default is built in: a hashed vector of the meme words, their letter
+   trigrams and the lexicon themes (dogs, politics, ai-agents, holiday-seasonal, …). An optional small open model,
+   all-MiniLM-L6-v2 on CPU through transformers.js, or any local Ollama embedding model, adds meaning links such as
+   kitty to cat (`DEXTERM_NARRATIVE_EMBEDDER=minilm` or `ollama`).
+3. **Cluster** incrementally in first-seen order. A coin joins the closest narrative it shares a meme word with (or, with
+   a semantic model, a currently hot one) if it is close enough to that narrative's centre and to the coin that started
+   it. Otherwise it starts a new narrative. Ids are stable (`nar_…`) and narratives never merge or split afterwards.
+   The label is the most common word or two-word phrase.

package/dist/packages/mcp/assets/kb/docs/docs-narratives-limits.md

@@ -0,0 +1,29 @@
+---
+id: docs-narratives-limits
+title: Memes and narratives (experimental) › Limits
+kind: docs
+page: narratives
+page_title: Memes and narratives (experimental)
+heading: Limits
+anchor: limits
+url: https://dexterm.xyz/docs/narratives#limits
+tags:
+  - docs
+  - narratives
+  - limits
+  - memes
+  - experimental
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/narratives.md
+date: 2026-10-16
+---
+
+- Name-based: themes that live only on X or Telegram are missed until a coin's name carries them.
+- Volume is each source's rolling window at the coin's newest sample; a coin not sampled for 6 h counts as zero.
+- Two themes that converge later stay two rows (ids never change).
+- The first build of the table reads the last 26 h of recorded history: tens of seconds on a large database (the screen stays live meanwhile).

package/dist/packages/mcp/assets/kb/docs/docs-narratives-what-is-measured.md

@@ -0,0 +1,44 @@
+---
+id: docs-narratives-what-is-measured
+title: Memes and narratives (experimental) › What is measured
+kind: docs
+page: narratives
+page_title: Memes and narratives (experimental)
+heading: What is measured
+anchor: what-is-measured
+url: https://dexterm.xyz/docs/narratives#what-is-measured
+tags:
+  - docs
+  - narratives
+  - measured
+  - memes
+  - experimental
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/narratives.md
+date: 2026-10-16
+---
+
+Per narrative and window (5 m, 1 h, 6 h, 24 h): coins seen, new coins and the new-coin rate, the narrative's share of all
+tracked volume, unique traders (1 h, Jupiter) and their growth, the top runner (sellable pool of at least 10k USD) and its drawdown
+from its peak, how often the same meme word was relaunched in the last hour, and a 0-100 **traction score** (1 h volume
+growth, spawn rate, repeated-name velocity, share of new-coin volume, breadth). Rank 1 is the highest score.
+**Cross-coin holder overlap is not recorded, so it is not part of the score** (it shows as null, never estimated).
+
+**Lifecycle**, first rule that matches:
+
+| state | rule |
+|---|---|
+| dead | no member sampled in 6 h, or 1 h volume under 1k USD with no new coin in 6 h |
+| spark | the first coin is under 1 h old |
+| ignition | 1 h volume ≥ 5k USD and ≥ 2× the 1 h volume an hour ago, with a new coin in the hour or unique traders +50% |
+| fading | 1 h volume ≤ 40% of its 24 h high, or ≤ 60% of an hour ago |
+| peak | otherwise: hot, near its 24 h high, growing under 2× |
+
+**Copy-cat saturation** (`*` in the table): at least 5 coins, at least 3 of them new in 6 h, and the coins after the 3
+oldest together hold under 25% of the narrative's 1 h volume. The copies are launching, but they are not getting the
+volume.

package/dist/packages/mcp/assets/kb/docs/docs-narratives-what-testing-showed.md

@@ -0,0 +1,43 @@
+---
+id: docs-narratives-what-testing-showed
+title: Memes and narratives (experimental) › What testing showed
+kind: docs
+page: narratives
+page_title: Memes and narratives (experimental)
+heading: What testing showed
+anchor: what-testing-showed
+url: https://dexterm.xyz/docs/narratives#what-testing-showed
+tags:
+  - docs
+  - narratives
+  - testing
+  - showed
+  - memes
+  - experimental
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/narratives.md
+date: 2026-10-16
+---
+
+We replayed 11 days of dexterm's recorded history (219,730 coins) through the tracker in time order, reading each
+coin's narrative at the first moment a scanner could act on it (point in time: nothing recorded after that moment),
+and tested it on days that were held back until the end, the same way as dexterm's other entry research.
+
+- **It is a useful map of what is running, not an edge.** On the held-back days, adding the narrative to a coin's own
+  numbers did not help tell apart the coins that later tripled (ranking quality fell slightly, by 0.022 (95% interval -0.059 to +0.008)) or the ones that drained
+  (fell by 0.033 (-0.052 to -0.015)).
+- **None of the narrative gates we fixed in advance improved paper results** when added to the existing entry rules:
+  joining an igniting narrative early, skipping the 5th or later copy of a saturated narrative, and skipping fading or
+  dead narratives. In the 22 combinations of these gates and rules with at least 20 paper entries, none raised the average result per entry and three lowered it. (One more gate, added after looking at the earlier days, is reported apart; its 5 combinations moved nothing either way.) Every gate also skipped some of the coins that went on to run.
+- **What it does describe:** a coin that is part of a narrative (two or more coins) drained within 6 hours about twice as often as a coin on its own (about 50% against 27% on the held-back days), and also tripled a little more often. Copy-cat waves are where both the runs and the drains happen. The lifecycle states themselves did not sort the outcomes: the share that later tripled was 4% to 6% in every state.
+- In a hand-graded sample of 100 narratives, 70 were coherent (one meme and its copies, or one theme) and the
+  label named the theme in 87. The usual mistakes: the same ticker reused for an unrelated coin, and a shared
+  generic word.
+
+Every number above comes with its sample size and a 95% interval in the study; the narratives table is a way to see
+what is running, and the numbers say it should not be read as a reason to trade.

package/dist/packages/mcp/assets/kb/docs/docs-narratives-where-to-find-it.md

@@ -0,0 +1,37 @@
+---
+id: docs-narratives-where-to-find-it
+title: Memes and narratives (experimental) › Where to find it
+kind: docs
+page: narratives
+page_title: Memes and narratives (experimental)
+heading: Where to find it
+anchor: where-to-find-it
+url: https://dexterm.xyz/docs/narratives#where-to-find-it
+tags:
+  - docs
+  - narratives
+  - where
+  - find
+  - memes
+  - experimental
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/narratives.md
+date: 2026-10-16
+---
+
+- The `N` screen opens the narrative board. Press `n` to switch between the theme board and the **NARRATIVES**
+  heat table. `enter` drills into a narrative's member coins; `esc` goes back to the table.
+- The token screen shows a **Narrative** row once the tracker has been built (open `N` then `n` first), for example
+  `ZORP · lifecycle: ignition · rank 3 · #2 of 9`.
+- `dexterm narratives` prints the heat table. `dexterm narratives detail ID` shows one narrative, `dexterm narratives of
+  MINT` shows the narrative of one coin, and `dexterm narratives export --out FILE` writes the JSON
+  (`dexterm-narratives/1`) that a strategy tracker page reads. `--at ISO` replays up to a past time.
+- MCP tools for your analyst or your own agent: `narratives_top`, `narrative_detail`, `narrative_of` (observe tier,
+  read-only). Coin names come back wrapped as untrusted data.
+- Watch rules: the field `narrative_rank` and the tags `narrative:ignition` / `narrative:saturated`, so a rule can fire
+  "when the coin's narrative ignites".

package/dist/packages/mcp/assets/kb/docs/docs-narratives.md

@@ -0,0 +1,29 @@
+---
+id: docs-narratives
+title: Memes and narratives (experimental)
+kind: docs
+page: narratives
+page_title: Memes and narratives (experimental)
+url: https://dexterm.xyz/docs/narratives
+tags:
+  - docs
+  - narratives
+  - memes
+  - experimental
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/narratives.md
+date: 2026-10-16
+---
+
+Groups coins by the theme their name and ticker carry, and measures each theme's heat per window. Measured heat, not advice.
+
+A memecoin does not need a real project to run. It moves on a theme: a ticker pun, an animal, a celebrity, an AI-agent
+craze, a holiday, or simply being a copy of a coin that just ran. The narratives tracker groups coins by that theme and
+measures how hot each one is right now. It is **experimental**, **keyless** and **local**. It adds no network requests,
+because it reads the history recorder, and it never calls a model. Everything it shows is **measured heat from recorded
+market data, not advice and not a prediction**.

package/dist/packages/mcp/assets/kb/docs/docs-overlay-before-you-start.md

@@ -0,0 +1,33 @@
+---
+id: docs-overlay-before-you-start
+title: Streamer overlay (OBS) › Before you start
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: Before you start
+anchor: before-you-start
+url: https://dexterm.xyz/docs/overlay#before-you-start
+tags:
+  - docs
+  - overlay
+  - before
+  - start
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+You need an agent session to watch. Pick one:
+
+- **An agent connected over MCP** (Claude Code, Cursor, Codex, …): run the app with `dexterm --spectate-mcp`. Your terminal follows the agent and opens the read-only spectator stream. See follow over MCP (https://dexterm.xyz/docs/spectator#follow-over-mcp-in-the-running-terminal).
+- **An agent on the loopback bus**: `dexterm agent serve --spectate`. See bring your own agent (https://dexterm.xyz/docs/agents).
+- **No agent, a dry run or a rehearsal**: a saved session with `--replay FILE` (record one with `dexterm agent serve --record FILE`). Every scene then carries a yellow **SAMPLE DATA · REPLAY** tag.
+
+The overlay finds the live stream on its own (the same `spectator.json` that `dexterm spectate --info` reads), waits for it if it is not up yet, and reconnects when it restarts.

package/dist/packages/mcp/assets/kb/docs/docs-overlay-limits.md

@@ -0,0 +1,30 @@
+---
+id: docs-overlay-limits
+title: Streamer overlay (OBS) › Limits
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: Limits
+anchor: limits
+url: https://dexterm.xyz/docs/overlay#limits
+tags:
+  - docs
+  - overlay
+  - limits
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+- **The scenes show what the agent did.** If the agent never reads holders, the holder bar stays "not read yet"; if it never runs a LARP check, there is no LARP line. Live signals appear only while your terminal follows the agent (`--spectate-mcp`) and has that coin's data.
+- **One coin at a time.** The coin card follows the coin the agent touched last; the PnL card follows the agent's newest paper fill.
+- **A reload needs a fresh URL** (see the OBS steps). This is the single-use ticket working as designed.
+- **The stream starts with the last 200 events** when the overlay connects, then follows live.
+- **Not financial advice.** The verdict, LARP evidence and signals are risk information, never a recommendation; paper results are simulated.

package/dist/packages/mcp/assets/kb/docs/docs-overlay-options.md

@@ -0,0 +1,36 @@
+---
+id: docs-overlay-options
+title: Streamer overlay (OBS) › Options
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: Options
+anchor: options
+url: https://dexterm.xyz/docs/overlay#options
+tags:
+  - docs
+  - overlay
+  - options
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+| Option | What it does |
+|---|---|
+| `--scene NAME` | `activity`, `coin`, `pnl` or `all`; repeat it for several. Default: the three scenes |
+| `--theme NAME` | `cyberspace` (phosphor green, the app's default look), `ice` (electric cyan) or `neon` (magenta). Default `cyberspace` |
+| `--replay FILE` | Play a saved spectator session instead of the live stream. Every scene says SAMPLE DATA |
+| `--speed N` | Replay speed (default 1); gaps between calls are capped at 5 s |
+| `--loop` | Replay again from the start; the final scenes hold for 10 s first |
+| `--ledger TRADE_ID` | The PnL scene shows one round trip from your own trade ledger (https://dexterm.xyz/docs/paper-trading#the-trade-ledger) (`dexterm ledger trades` lists the ids) instead of the agent's paper fills. `--sol-usd N` for a USD-booked trade |
+| `--port N` | A fixed loopback port (1024 to 65535) instead of a random one |
+| `--ticket-ttl MIN` | Minutes an unused URL stays valid (default 10) |
+| `--json` | Print the scene URLs as JSON |

package/dist/packages/mcp/assets/kb/docs/docs-overlay-security-model.md

@@ -0,0 +1,36 @@
+---
+id: docs-overlay-security-model
+title: Streamer overlay (OBS) › Security model
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: Security model
+anchor: security-model
+url: https://dexterm.xyz/docs/overlay#security-model
+tags:
+  - docs
+  - overlay
+  - security
+  - model
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+The overlay uses the same model as the popup windows (https://dexterm.xyz/docs/popup-chart):
+
+- **Loopback only.** The page server listens on `127.0.0.1` (a random port unless `--port`) and refuses any connection that is not from this machine.
+- **Single-use ticket, then a one-time token.** A URL carries a random 32-byte ticket that buys exactly one page load. That page holds a second, one-time token (valid 30 seconds) for its WebSocket. A spent or expired ticket, a ticket for another scene, or a forged token gets an empty 404.
+- **Host and Origin checks.** Every request must say `Host: 127.0.0.1:<port>` (so a DNS-rebinding page cannot reach it), and the WebSocket must come from the overlay's own origin. No CORS header is ever sent. Refused probes are printed in the overlay's terminal, without the ticket.
+- **No inbound control.** The socket only pushes scene data. Whatever a page sends is counted and dropped, never parsed or acted on; the overlay has nothing it could control.
+- **A locked-down page.** Its script and styles are inline under a per-page nonce; the content security policy allows no remote content, no fonts, no frames and no other connections. The page builds its text with `textContent` only (agent and coin text are untrusted), and the only image is the PnL card, sent over the socket.
+- **No new network.** The overlay talks to the spectator stream on loopback and reads your ledger file. It fetches nothing from the internet.
+
+The URL is printed in your own terminal so you can paste it; treat it like the popup URLs: it is loopback-only and single-use, but don't post a screenshot of a fresh one.

package/dist/packages/mcp/assets/kb/docs/docs-overlay-set-it-up-in-obs-step-by-step.md

@@ -0,0 +1,49 @@
+---
+id: docs-overlay-set-it-up-in-obs-step-by-step
+title: Streamer overlay (OBS) › Set it up in OBS, step by step
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: Set it up in OBS, step by step
+anchor: set-it-up-in-obs-step-by-step
+url: https://dexterm.xyz/docs/overlay#set-it-up-in-obs-step-by-step
+tags:
+  - docs
+  - overlay
+  - set
+  - obs
+  - step
+  - streamer
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+1. Start the session you want to show (see above).
+2. In a second terminal, run:
+
+   ```sh
+   $ dexterm overlay --theme cyberspace
+   dexterm overlay · theme cyberspace · each URL works once, for 10 min
+     activity  http://127.0.0.1:53133/overlay/activity?p=…
+     coin      http://127.0.0.1:53133/overlay/coin?p=…
+     pnl       http://127.0.0.1:53133/overlay/pnl?p=…
+   ```
+
+   Leave it running for as long as you stream. `q` (or ctrl+c) stops it.
+3. In OBS, in your scene's **Sources** panel, click **+** and choose **Browser**. Name it (for example "dexterm coin") and click **OK**.
+4. In the properties window:
+   - **URL**: paste one of the printed URLs (the whole line after the scene name).
+   - **Width / Height**: `1240` × `420` for `coin` or `activity`, `1240` × `760` for `pnl`, `1600` × `1300` for `all`. Resize the source on the canvas afterwards; the scenes scale.
+   - Leave **Use custom frame rate** off.
+   - Leave **Custom CSS** as OBS fills it in (it keeps the background transparent) or empty.
+   - Untick **Shutdown source when not visible** and **Refresh browser when scene becomes active**: either one reloads the page, and a reload needs a fresh URL (see below).
+5. Click **OK**. The panel appears over your stream with a transparent background. Repeat steps 3 to 5 for the other scenes.
+6. To check the setup without a live agent, run `dexterm overlay --replay session.jsonl --loop` and watch the scenes fill in with the SAMPLE DATA tag on.
+
+**Each URL works once.** It is a single-use ticket: OBS's first load spends it, and the page then holds its own one-time connection. If OBS reloads the page, or you paste the URL into a second source, the page stays empty. Press **n** in the overlay's terminal for a fresh set of URLs and paste the new one into the source. URLs that are never loaded expire after 10 minutes (`--ticket-ttl MIN` changes that, 1 to 240). When you restart `dexterm overlay`, its port changes too, so paste fresh URLs then; `--port N` keeps the port fixed (the tickets still change).

package/dist/packages/mcp/assets/kb/docs/docs-overlay-the-pnl-scene-paper-and-live.md

@@ -0,0 +1,34 @@
+---
+id: docs-overlay-the-pnl-scene-paper-and-live
+title: Streamer overlay (OBS) › The PnL scene: PAPER and LIVE
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: The PnL scene: PAPER and LIVE
+anchor: the-pnl-scene-paper-and-live
+url: https://dexterm.xyz/docs/overlay#the-pnl-scene-paper-and-live
+tags:
+  - docs
+  - overlay
+  - pnl
+  - scene
+  - paper
+  - live
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+The card is the PnL card (https://dexterm.xyz/docs/paper-trading#pnl-cards) renderer itself, so its stamp, frame colour, stamp strip, provenance block, data ages and "not financial advice" footer are drawn exactly as on a saved card and cannot be turned off.
+
+- **The agent's trades are PAPER.** An agent can only paper-trade in dexterm, so a card built from the stream is always stamped **PAPER · SIMULATED TRADE · NO REAL FUNDS**, and the scene header says PAPER · SIMULATED. An open position is marked at the newest price the stream carried (converted to SOL at the rate the agent's own fill implies) or, without a later price, at the last fill; the card prints which, and how old the mark is.
+- **Your own ledger trades are PAPER or LIVE by wallet mode.** With `--ledger TRADE_ID` the stamp follows the trade's wallet mode: paper is PAPER, devnet is **LIVE · DEVNET** (test funds, not real money) and live is **LIVE · WALLET-SIGNED**, on the card and in the scene header alike. The LIVE note counts the trade's wallet-signed transactions. A real-mode row gets no card (dexterm only modelled that fill; your executor's receipt is the record). The ledger is a local file, read again every 30 seconds.
+- **Size is a band and the wallet never shows.** The mint is shortened and transaction signatures are left off the overlay card.
+- **A replay is SAMPLE DATA.** With `--replay`, a yellow SAMPLE DATA band sits across the top of the card, above the card's own stamp.

package/dist/packages/mcp/assets/kb/docs/docs-overlay-the-three-scenes.md

@@ -0,0 +1,35 @@
+---
+id: docs-overlay-the-three-scenes
+title: Streamer overlay (OBS) › The three scenes
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: The three scenes
+anchor: the-three-scenes
+url: https://dexterm.xyz/docs/overlay#the-three-scenes
+tags:
+  - docs
+  - overlay
+  - three
+  - scenes
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+| Scene | What it shows | Where the data comes from |
+|---|---|---|
+| `activity` | The agent's last calls: when, the agent, the tool, a one-line summary, and how old that call's data was | Every call the spectator stream carries |
+| `coin` | The coin the agent is on: ticker and shortened mint, price, the deterministic verdict with the rug heuristic, the LARP evidence flags, a top-10 holder bar with the holder count, and the live holder/rug signals, each with its age | The results of the agent's own `get_token`, `get_holders`, `get_dossier`, `analyze_token` and `larp_check` calls, plus the signals your terminal fires for that coin while it follows the agent |
+| `pnl` | The PnL card, drawn by the same renderer as the `H` key (PnL cards (https://dexterm.xyz/docs/paper-trading#pnl-cards)) | The agent's PAPER fills on the coin, or one trade from your own ledger with `--ledger` |
+
+`--scene all` puts the three scenes in one Browser source (two columns, the PnL card underneath) if you would rather crop one source than place three.
+
+Every scene shows how old its data is (`data age 12s`, and `… old` next to each figure). The scene's age chip turns yellow once its newest figure is over two minutes old. The LARP line says "evidence, not a verdict", and every page ends with "read-only · addresses redacted · not financial advice".

package/dist/packages/mcp/assets/kb/docs/docs-overlay-what-is-redacted.md

@@ -0,0 +1,31 @@
+---
+id: docs-overlay-what-is-redacted
+title: Streamer overlay (OBS) › What is redacted
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+heading: What is redacted
+anchor: what-is-redacted
+url: https://dexterm.xyz/docs/overlay#what-is-redacted
+tags:
+  - docs
+  - overlay
+  - redacted
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+Redaction is always on, and the overlay applies it itself, whatever its source already did:
+
+- Every wallet or mint address becomes its first and last four characters (`Fixt…AAAA`), in every field: tool names, summaries, agent names, LARP evidence, signal text.
+- Key material (long base58 or hex runs) becomes `[key]`.
+- Anything the spectator stream marks sensitive is shown as `[sensitive]`, and sensitive-named fields are dropped before they reach a scene.
+- A coin, fill or ticket whose mint is not in the shortened shape is dropped, not shown.

package/dist/packages/mcp/assets/kb/docs/docs-overlay.md

@@ -0,0 +1,25 @@
+---
+id: docs-overlay
+title: Streamer overlay (OBS)
+kind: docs
+page: overlay
+page_title: Streamer overlay (OBS)
+url: https://dexterm.xyz/docs/overlay
+tags:
+  - docs
+  - overlay
+  - streamer
+  - obs
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/overlay.md
+date: 2026-10-16
+---
+
+Put an agent session on your stream. dexterm overlay serves three transparent scenes for an OBS Browser source (agent activity, the coin card, the PAPER or LIVE PnL card) on 127.0.0.1, fed by the read-only spectator stream or a saved replay. Covers the OBS setup step by step, the three themes, what is redacted, the security model, the SAMPLE DATA tag and the limits.
+
+`dexterm overlay` turns the spectator view (https://dexterm.xyz/docs/spectator) into scenes you can drop into OBS as a **Browser source**: the agent's recent calls, the coin it is on, and its PnL card, over a transparent background. It watches; it never acts. Nothing on an overlay page can pause, trade, arm, size, sign or raise a cap, and the page sends nothing back to dexterm.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading.md

@@ -26,6 +26,6 @@ The PAPER ticket, the simulated wallet, the confirm gate, order plans on paper,
 
 Trading in dexterm is **PAPER by default**: a simulated wallet priced from live, keyless Jupiter quotes. Nothing is signed, no key is held, no transaction is sent, and the paper code imports no wallet or signing library of any kind. Every ticket and positions frame says so in a banner that is never hidden.
 
-dexterm has no live trading path of its own: it holds no key, has no trading wallet and builds or sends no transaction. Live trading happens in a Telegram trading bot of your choice; see Live trading (https://dexterm.xyz/docs/live-trading).
+dexterm has no live trading path of its own: it holds no key, has no trading wallet and builds or sends no transaction. Live trading happens in a Telegram trading bot of your choice; see Live trading (https://dexterm.xyz/docs/live-trading). Real mode is experimental; signals to your own executor; dexterm never holds a key; not financial advice (see Real mode (https://dexterm.xyz/docs/real-mode)).
 
 PAPER positions on sample data