dexterm-cli 0.1.7 → 0.2.1

package/dist/packages/mcp/assets/kb/docs/docs-autotrade-what-it-is-paper-self-directed.md

@@ -22,7 +22,7 @@ sources:
 date: 2026-10-16
 ---
 
-Autotrade (paper) is a strategy file plus an engine that replays it. You write the rules: which coins count as candidates, how a position is sized, how it is exited, and how much loss is allowed. The engine applies exactly those rules, and every size is clamped by them. It runs on **paper** by default: there is no key, wallet or signer anywhere in a strategy, and a paper run never signs or sends anything. A strategy that says `"mode": "live"` validates with a warning and runs only with `dexterm autotrade run --live`, through the live signer (https://dexterm.xyz/docs/live-trading) and its caps (experimental, can lose all the funds in the trading wallet).
+Autotrade (paper) is a strategy file plus an engine that replays it. You write the rules: which coins count as candidates, how a position is sized, how it is exited, and how much loss is allowed. The engine applies exactly those rules, and every size is clamped by them. It runs on **paper** by default: there is no key, wallet or signer anywhere in a strategy, and a paper run never signs or sends anything. A strategy you switch to **real** yourself, on your own terminal, runs the same way and also sends each trade to your own executor as a signal: see real mode (https://dexterm.xyz/docs/real-mode) (experimental; dexterm still holds no key and signs nothing). A strategy that says `"mode": "live"` (the removed local signer) validates with a warning and never runs.
 
 It is self-directed: your strategies, on your machine, with your own recorded history. Nobody runs a strategy for you, and a preset is an example, not a recommendation.
 
@@ -38,6 +38,13 @@ What ships today, covered below:
 - What it costs (https://dexterm.xyz/docs/autotrade#what-it-costs-claude-usage-per-session): the Claude usage of a session, measured.
 - What it will not do (https://dexterm.xyz/docs/autotrade#what-it-will-not-do): live money, copy-trading automation, managing anyone else's money.
 
+The rest of the automated trading suite has its own pages:
+
+- Build a strategy by chat (https://dexterm.xyz/docs/build-a-strategy-by-chat): the ladder from a chat proposal to a backtest, a paper forward test on live data, always on and, only if you choose, real, one rung at a time on evidence.
+- The always-on service (https://dexterm.xyz/docs/autotrade#the-always-on-service): your listed strategies keep running from login and come back after a crash.
+- Real mode (https://dexterm.xyz/docs/real-mode) (experimental): a strategy you arm on your own terminal sends each trade as a signal to your own executor; dexterm never holds a key.
+- Going real, safely (https://dexterm.xyz/docs/going-real): your own limits for every number, the executor kit, executor health and the digest.
+
 On your phone: your own Telegram bot (https://dexterm.xyz/docs/telegram) sends the entries, exits, PnL cards and halts, takes `/pause` and `/kill`, and can make every entry wait for your tap (`entry.decide: "agent+approve"`).
 
-Still to come, documented here when it lands: a background service that keeps the runner going without a terminal, and the runner filling through the paper desk (https://dexterm.xyz/docs/autotrade#exits-and-wakes) with the exit monitor as its own process.
+Still to come, documented here when it lands: the runner filling through the paper desk (https://dexterm.xyz/docs/autotrade#exits-and-wakes) with the exit monitor as its own process.

package/dist/packages/mcp/assets/kb/docs/docs-autotrade-what-it-will-not-do.md

@@ -22,7 +22,7 @@ sources:
 date: 2026-10-16
 ---
 
-- **Live money.** A run never signs and never sends a transaction: `--live` and a strategy in live mode are refused, and the runner holds no key. Live trading happens in a Telegram trading bot of your choice, outside dexterm (see Live trading (https://dexterm.xyz/docs/live-trading)).
+- **Live money.** A run never signs and never sends a transaction: `--live` and a strategy in live mode are refused, and the runner holds no key. Live trading happens in a Telegram trading bot (or script) of your choice, outside dexterm (see Live trading (https://dexterm.xyz/docs/live-trading)); in real mode (https://dexterm.xyz/docs/real-mode) dexterm sends that executor a signal for each trade and it decides.
 - **Copy-trading automation.** It does not copy anyone's trades.
 - **Managing anyone else's money.** It runs your strategies on your machine, with your own Claude login and your own paper book. Nobody runs a strategy for you: there are no hosted runners, no pooled accounts, no fee on its trades and no strategy marketplace.
 - **Decide outside your rules.** Your agent chooses only inside the bounds you wrote. It cannot raise a size, block an exit, lift a stop or apply a strategy change; you apply a change with a key.

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

@@ -19,4 +19,6 @@ sources:
 date: 2026-10-16
 ---
 
-Strategies you write or copy from presets, validated in one file, and backtests on your own recorded history with a held-out check. Paper only, self-directed, not financial advice.
+Strategies you write or copy from presets, validated in one file, and backtests on your own recorded history with a held-out check. Paper by default, self-directed, not financial advice.
+
+a backtest and its held-out sweep on the Q screen (PAPER, a small recorded fixture tape)

package/dist/packages/mcp/assets/kb/docs/docs-beginners-before-any-experimental-trading.md

@@ -28,6 +28,6 @@ sources:
 date: 2026-10-16
 ---
 
-Stop here until you are comfortable reading the app. Trading in dexterm is PAPER simulation, which uses pretend funds, and the keypress gate (a required physical key press) is on by default. dexterm signs nothing and sends no transaction; live trading happens in a Telegram trading bot of your choice, outside dexterm. No analyst, voice, or connected program can trade.
+Stop here until you are comfortable reading the app. Trading in dexterm is PAPER simulation by default, which uses pretend funds, and the keypress gate (a required physical key press) is on by default. dexterm signs nothing and sends no transaction. Real mode is experimental; signals to your own executor; dexterm never holds a key; not financial advice. No analyst, voice, or connected program can trade or turn real mode on.
 
-Never enter a seed phrase, private key, password, API key, or authentication token. Read the paper trading guide (https://dexterm.xyz/docs/paper-trading) and live trading (https://dexterm.xyz/docs/live-trading) before considering anything beyond the read-only walkthrough.
+Never enter a seed phrase, private key, password, API key, or authentication token. Read the paper trading guide (https://dexterm.xyz/docs/paper-trading), real mode (https://dexterm.xyz/docs/real-mode) and live trading (https://dexterm.xyz/docs/live-trading) before considering anything beyond the read-only walkthrough.

package/dist/packages/mcp/assets/kb/docs/docs-beginners-copy-and-paste-without-surprises.md

@@ -34,6 +34,5 @@ Copy only the text inside a code box. Do not copy a leading `$`; it represents t
 |---|---|---|
 | macOS Terminal | Command-C | Command-V |
 | Linux terminal | Ctrl-Shift-C | Ctrl-Shift-V |
-| Windows Terminal | Ctrl-Shift-C | Ctrl-Shift-V |
 
 Right-click and choose **Paste** if the shortcut does not work. A multi-line paste can run several commands, so this guide uses one command per box. Never paste a command you do not understand; read the sentence above it first.

package/dist/packages/mcp/assets/kb/docs/docs-beginners-if-dexterm-says-command-not-found.md

@@ -31,6 +31,6 @@ sources:
 date: 2026-10-16
 ---
 
-Close and reopen the terminal first. Then run `npm prefix -g` to see npm's global install folder. On macOS/Linux, npm's executable folder must be on your PATH; the installer output normally tells you the exact line for your setup. Do not paste a PATH fix from a stranger. On Windows, rerun the Node.js installer and keep its “Add to PATH” option enabled, then reopen Windows Terminal.
+Close and reopen the terminal first. Then run `npm prefix -g` to see npm's global install folder. On macOS/Linux, npm's executable folder must be on your PATH; the installer output normally tells you the exact line for your setup. Do not paste a PATH fix from a stranger.
 
-You can confirm whether the shell can find dexterm with `command -v dexterm` on macOS/Linux or `Get-Command dexterm` in PowerShell.
+You can confirm whether the shell can find dexterm with `command -v dexterm`.

package/dist/packages/mcp/assets/kb/docs/docs-beginners-reopen-dexterm-later.md

@@ -27,7 +27,7 @@ sources:
 date: 2026-10-16
 ---
 
-Open Terminal, a Linux terminal, or PowerShell again and run:
+Open Terminal or a Linux terminal again and run:
 
 ```sh reopen dexterm
 dexterm

package/dist/packages/mcp/assets/kb/docs/docs-beginners-terminal-shell-prompt-command-output-and-path.md

@@ -30,8 +30,8 @@ sources:
 date: 2026-10-16
 ---
 
-- A **terminal** is a text window for giving your computer instructions. macOS calls its built-in app Terminal. Windows users should use PowerShell inside Windows Terminal. Linux includes a terminal app with the desktop.
-- A **shell** is the program inside that window that reads what you type. PowerShell is a shell; `zsh` and `bash` are common macOS and Linux shells. You do not need to learn which one you have.
+- A **terminal** is a text window for giving your computer instructions. macOS calls its built-in app Terminal. Linux includes a terminal app with the desktop. dexterm runs on macOS and Linux; Windows is not supported.
+- A **shell** is the program inside that window that reads what you type. `zsh` and `bash` are common macOS and Linux shells. You do not need to learn which one you have.
 - A **prompt** is the short text, often ending in `$` or `>`, that means the shell is ready. Do not type the prompt itself.
 - A **command** is one line you type after the prompt, such as `dexterm doctor`.
 - **Output** is the text the computer prints after a command. Output is an answer, not another command to copy blindly.

package/dist/packages/mcp/assets/kb/docs/docs-beginners-windows-expectations.md

@@ -26,4 +26,4 @@ sources:
 date: 2026-10-16
 ---
 
-Windows x64 is experimental: the full CI suite passed for 0.1.4, though some file-permission checks are skipped. File permissions rely on your Windows user profile; voice has no Windows speech engine; browser-opening actions show a URL instead; `doctor` may print a macOS/Linux repair command; and the npm-installed `claude.cmd` is not detected as a usable analyst binary. These limits do not change the key rule: dexterm never holds your wallet keys.
+dexterm supports macOS and Linux. Windows is not supported: private files rely on macOS and Linux file permissions, voice has no Windows engine, browser-opening actions and `doctor`'s repair commands assume macOS or Linux, and the npm-installed `claude.cmd` is not detected as a usable analyst binary. The supported platforms (https://dexterm.xyz/docs/getting-started#supported-platforms) table has the details.

package/dist/packages/mcp/assets/kb/docs/docs-beginners-windows.md

@@ -27,4 +27,4 @@ sources:
 date: 2026-10-16
 ---
 
-Open the Start menu, type **Windows Terminal**, and choose the **PowerShell** tab. Windows support is experimental and has not yet passed the project's test run; the known limits are listed under Windows expectations (https://dexterm.xyz/docs/beginners#windows-expectations).
+Windows is not supported. See Windows expectations (https://dexterm.xyz/docs/beginners#windows-expectations).

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-1-ask-for-a-strategy.md

@@ -0,0 +1,27 @@
+---
+id: docs-build-a-strategy-by-chat-1-ask-for-a-strategy
+title: Build a strategy by chat › 1. Ask for a strategy
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: 1. Ask for a strategy
+anchor: 1-ask-for-a-strategy
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#1-ask-for-a-strategy
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - ask
+  - strategy
+  - build
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+Open the analyst and say what you want, for example: "build me a strategy that buys young pairs on a 5-minute push, takes the cost back at 2x and lets the rest ride". The analyst works only through typed tools: it reads the presets, then **proposes** a new strategy (a copy of a preset with its changes) and any edits after that. Each proposal arrives on the `Q` screen as a card with the fields that change, the validation result and TIGHTER, NEUTRAL or LOOSER; `o` opens it, `y` applies it (a looser edit needs a second `y`), `n` dismisses it. Nothing exists until you apply it, and a new strategy always starts on paper. Your mode, bankroll, model budget and exit-liquidity floor stay yours: the analyst cannot change them. See changing a strategy by chat (https://dexterm.xyz/docs/autotrade#change-a-strategy-by-chat).

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-2-backtest-it-held-out-split.md

@@ -0,0 +1,31 @@
+---
+id: docs-build-a-strategy-by-chat-2-backtest-it-held-out-split
+title: Build a strategy by chat › 2. Backtest it (held-out split)
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: 2. Backtest it (held-out split)
+anchor: 2-backtest-it-held-out-split
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#2-backtest-it-held-out-split
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - backtest
+  - held-out
+  - split
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+`dexterm autotrade backtest <id>` (or `b` on the `Q` screen's journey view, or asking the analyst, which calls `strategy_backtest`) runs the strategy on your recorded history, then runs it again on each half of a **held-out split**: the newest 30% of coins, which nothing was ever tuned on, against the rest. The result is recorded as the strategy's backtest evidence.
+
+The evidence rule is strict: gain wording is allowed only with **at least 20 trades in both halves and a held-out net above 0**. Below that the report says "too few trades to claim anything", and the analyst is told to quote the trade counts and nothing more. A backtest is modelled fills on recorded snapshots, not a prediction; its data limits (https://dexterm.xyz/docs/autotrade#backtests-and-their-limits) are printed with it.

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-3-forward-test-it-on-live-data.md

@@ -0,0 +1,44 @@
+---
+id: docs-build-a-strategy-by-chat-3-forward-test-it-on-live-data
+title: Build a strategy by chat › 3. Forward-test it on live data (paper)
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: 3. Forward-test it on live data (paper)
+anchor: 3-forward-test-it-on-live-data-paper
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#3-forward-test-it-on-live-data-paper
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - forward-test
+  - live
+  - data
+  - paper
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+A forward test runs the same version on the **live** tape, on paper, with its own bankroll and its own run file, for a window you choose:
+
+```
+dexterm autotrade forward start <id> --hours 24          # or --trades 30, or both (whichever comes first)
+dexterm autotrade forward status [<id>]
+dexterm autotrade forward stop <id>
+dexterm autotrade forward report <id> [--json]
+```
+
+- It starts in the background and runs next to the always-on service (it does not take the runner's lock). `--foreground` keeps it in your terminal; `--bankroll-usd N` sets its paper bankroll (default: the strategy's own).
+- The strategy is frozen at the version it started with. A forward test of a strategy in real mode runs its paper twin: it never sends a signal.
+- At the end of its window it sells everything at the next tick (so its numbers are closed numbers), writes its report and records the result. The panic switch stops it like any run.
+- The analyst can start and stop one too (`strategy_forward_start`, `strategy_forward_stop`), after a backtest, for at most 72 hours or 200 trades, with the strategy's own bankroll. On the `Q` screen's journey view, `F` starts a 24-hour test and `X` stops it.
+- Only a test that ran its **whole window on live data** counts as the forward-tested rung. A test stopped early, run on a replay (`--replay` is a smoke run) or whose process died is shown, never counted.
+- A strategy that needs a chat approval for every entry cannot be forward-tested: no tap reaches a forward test. Model sessions of an agent strategy run on your own engine within the strategy's budgets, as in any run.

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-4-promote-it-to-always-on-paper.md

@@ -0,0 +1,36 @@
+---
+id: docs-build-a-strategy-by-chat-4-promote-it-to-always-on-paper
+title: Build a strategy by chat › 4. Promote it to always-on (paper)
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: 4. Promote it to always-on (paper)
+anchor: 4-promote-it-to-always-on-paper
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#4-promote-it-to-always-on-paper
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - promote
+  - always-on
+  - paper
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+When the forward test is done, the analyst can **propose** the promotion (`strategy_promote_propose`) or you can ask for it yourself:
+
+```
+dexterm autotrade promote <id> --to always-on
+dexterm autotrade promote list | show <pp-id> | apply <pp-id> | dismiss <pp-id>
+```
+
+Every promotion shows an evidence card first: the ladder, the backtest, the forward test and the comparison. Applying it needs your `y` on your own terminal (a pipe, a flag or an agent cannot give it), or `A` then `y` on the `Q` screen's journey view. The strategy then joins `autotrade.json` as a paper member, next to your other entries, and the always-on service runs it from its next start (`dexterm autotrade service status`).

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-5-real-only-if-you-choose.md

@@ -0,0 +1,36 @@
+---
+id: docs-build-a-strategy-by-chat-5-real-only-if-you-choose
+title: Build a strategy by chat › 5. Real, only if you choose
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: 5. Real, only if you choose
+anchor: 5-real-only-if-you-choose
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#5-real-only-if-you-choose
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - real
+  - only
+  - choose
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+Real mode sends each of the strategy's trades as a LIVE TRADE FIRE signal to your own executor; dexterm still holds no key and signs nothing. On this ladder it is the last rung and it is entirely yours:
+
+1. Set your own limits: `dexterm autotrade limits set perTradeSol=X dailySol=Y buysPerDay=N maxOpenPositions=N` and any of the others (Going real, safely (https://dexterm.xyz/docs/going-real#your-limits)); `signal caps set` sets the same four. A promotion to real refuses until you have.
+2. Set up a channel your executor reads (`dexterm autotrade signal channels ...`).
+3. Have the evidence: a completed forward test of these exact rules with at least 10 closed paper trades (your limit `minForwardTrades`) and a backtest on record. Below that the promotion refuses and says what is missing.
+4. `dexterm autotrade promote <id> --to real` (or `promote apply <pp-id>` for one the analyst proposed) hands over to `dexterm autotrade signal arm <id>`: the evidence panel, now with the journey line and the held-out verdict, then a typed phrase with a one-time code.
+
+The analyst can propose real (never below the evidence floor), never apply it, set a cap, choose a bankroll, lower the floor or arm anything. Arming directly with `signal arm` when a rung is missing, or below the evidence floor, refuses unless you type the OVERRIDE phrase it shows on your own terminal; the override is journaled. A real strategy runs in the foreground with `dexterm autotrade run <id> --real`; in 0.2.0 the always-on service runs paper strategies only, so stop the service while a real run is on (one runner per computer). See real mode (https://dexterm.xyz/docs/real-mode).

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-the-ladder.md

@@ -0,0 +1,41 @@
+---
+id: docs-build-a-strategy-by-chat-the-ladder
+title: Build a strategy by chat › The ladder
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: The ladder
+anchor: the-ladder
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#the-ladder
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - ladder
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+A strategy you build climbs one ladder, one rung at a time:
+
+**draft → backtested → forward-tested → always-on (paper) → real**
+
+| rung | what it needs | who does it |
+|---|---|---|
+| draft | a strategy that validates | the analyst proposes it, you apply it with a key |
+| backtested | a backtest on your recorded history, with the held-out split | you or the analyst |
+| forward-tested | a forward test that ran its whole window on live data, on paper | you or the analyst starts it; it runs by itself |
+| always-on | a member of `autotrade.json`, run by the always-on service (https://dexterm.xyz/docs/autotrade#the-always-on-service) on paper | the analyst can propose it; only you apply it |
+| real | real mode armed on your own terminal, with caps you set, above the evidence floor: a completed forward test with at least 10 closed paper trades and a backtest | only you, with a typed phrase (real mode (https://dexterm.xyz/docs/real-mode)) |
+
+Every rung counts evidence measured on the strategy's **exact rules**. Renaming it, rewording its description or arming it for real keeps its evidence; changing any rule (an entry filter, a size, an exit, a limit) starts the ladder again from draft. No rung can be skipped, and `dexterm autotrade journey <id>` (or `J` on the `Q` screen) always shows where a strategy stands and what the next rung needs.
+
+the journey view (J on the Q screen): one rung at a time, the forward test set beside its backtest (PAPER)

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-the-report.md

@@ -0,0 +1,31 @@
+---
+id: docs-build-a-strategy-by-chat-the-report
+title: Build a strategy by chat › 3. Forward-test it on live data (paper) › The report
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: The report
+anchor: the-report
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#the-report
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - report
+  - forward-test
+  - live
+  - data
+  - paper
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+`forward report` sets the forward test next to the backtest of the **same rules**, column by column: trades, win rate with its 95% interval, net, max drawdown, rug rate, and the fill cost against the mid price (with the drift from the backtest). It flags a forward win rate outside the backtest's interval, a deeper drawdown and more rugs than the history showed. Under 20 closed forward trades it says plainly that the sample is too small to claim anything, and it allows gain wording only when the backtest passes the evidence rule **and** the forward test made money on 20 or more trades.

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat-what-the-analyst-knows.md

@@ -0,0 +1,30 @@
+---
+id: docs-build-a-strategy-by-chat-what-the-analyst-knows
+title: Build a strategy by chat › What the analyst knows
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+heading: What the analyst knows
+anchor: what-the-analyst-knows
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat#what-the-analyst-knows
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - analyst
+  - knows
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+The analyst's tools for this: `strategy_journey` (the ladder for one strategy), `strategy_backtest` (with the held-out split), `strategy_forward_start`, `strategy_forward_stop`, `strategy_forward_report` and `strategy_promote_propose`. It is told the whole ladder, refuses to skip a rung, and reports numbers with their trade counts and the verdict lines as they are. An observe-only scan session gets none of the starting, stopping or proposing tools.
+
+Paper by default; experimental; not financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-build-a-strategy-by-chat.md

@@ -0,0 +1,26 @@
+---
+id: docs-build-a-strategy-by-chat
+title: Build a strategy by chat
+kind: docs
+page: build-a-strategy-by-chat
+page_title: Build a strategy by chat
+url: https://dexterm.xyz/docs/build-a-strategy-by-chat
+tags:
+  - docs
+  - build-a-strategy-by-chat
+  - build
+  - strategy
+  - chat
+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/build-a-strategy-by-chat.md
+date: 2026-10-16
+---
+
+Ask the analyst for a strategy, then back-test it on your recorded history, forward-test it on live data on paper, and promote it one step at a time to the always-on service and, only if you choose, to real mode. Every step needs evidence; nothing is promoted by the model. Paper by default, not financial advice.
+
+a strategy the analyst proposed in chat, as a diff you apply with a key (PAPER)

package/dist/packages/mcp/assets/kb/docs/docs-classifier-hosted-jev-with-your-own-key.md

@@ -0,0 +1,34 @@
+---
+id: docs-classifier-hosted-jev-with-your-own-key
+title: Classification models › Hosted Jev with your own key
+kind: docs
+page: classifier
+page_title: Classification models
+heading: Hosted Jev with your own key
+anchor: hosted-jev-with-your-own-key
+url: https://dexterm.xyz/docs/classifier#hosted-jev-with-your-own-key
+tags:
+  - docs
+  - classifier
+  - hosted
+  - jev
+  - own
+  - key
+  - classification
+  - models
+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/classifier.md
+date: 2026-10-16
+---
+
+```
+dexterm classifier key set          paste your TypeSafe API key (hidden input; stored 0600 under ~/.dexterm/keys)
+dexterm classifier pick jev-hosted
+```
+
+dexterm never ships or shares a key. The key is sent only to `https://api.typesafe.ai`, never printed, and never stored in `classifier.json`. `TYPESAFE_API_KEY` in the environment works too. Each call counts tokens. Set your price per million input tokens in `~/.dexterm/classifier.json` (`jev.pricePerMTokUsd`) to see a cost in dollars; until you do, the cost shows as *unpriced*, never as $0. A daily call cap (`jev.maxCallsPerDay`, default 1,000) stops calls before they reach the network. A rate limit from the API is reported with its retry time.

package/dist/packages/mcp/assets/kb/docs/docs-classifier-how-they-measured-on-dexterm-s-own-history.md

@@ -0,0 +1,52 @@
+---
+id: docs-classifier-how-they-measured-on-dexterm-s-own-history
+title: Classification models › How they measured on dexterm's own history
+kind: docs
+page: classifier
+page_title: Classification models
+heading: How they measured on dexterm's own history
+anchor: how-they-measured-on-dexterm-s-own-history
+url: https://dexterm.xyz/docs/classifier#how-they-measured-on-dexterm-s-own-history
+tags:
+  - docs
+  - classifier
+  - they
+  - measured
+  - dexterm
+  - own
+  - history
+  - classification
+  - models
+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/classifier.md
+date: 2026-10-16
+---
+
+dexterm's benchmark (October 2026) asked each model about coins whose outcome we already know: 1,054 coins from the LARP eval set (rugged or dead within 72 hours?) and 1,800 coins from the recorder's history (drained within 6 hours?). The rules and the pick were fixed before the final held-out coins were scored, and those were scored once. AUROC says how well a model ranks the coins that went bad above the ones that did not: 0.5 is a coin flip, 1.0 is perfect.
+
+| model | where it ran | drained within 6 h (held-out) | bad within 72 h (held-out) | time per coin | cost |
+|---|---|---|---|---|---|
+| Built-in scores (default) | anywhere | 0.50 | 0.71 | under 1 ms | free |
+| Kev 0.8B (Q8) | Intel Mac mini CPU | 0.54 | 0.46 | 3-7 s | free |
+| Kev 4B (Q4) | desktop and Mac mini CPUs | 0.52 | 0.73 | 5-14 s | free |
+| Kev 9B (Q4) | RTX 4080 GPU | 0.53 | 0.79 | 0.06-0.2 s | free |
+| Claude haiku (comparison only) | Claude CLI | 0.62 | 0.86 | about 5 s | about $0.0009 |
+| Kev 27B, hosted Jev, open JEV | not measured | | | | |
+
+What this means:
+
+- **No model is good at this yet.** Predicting a coin's next six hours from what is known now is hard for everything we tried, including the built-in scores. Treat every estimate as one weak input, never as a verdict.
+- **Kev 0.8B ranks coins no better than chance** and gives almost the same number for every coin, so dexterm never suggests it.
+- **Kev 4B** is the model `dexterm classifier pull` suggests if you want a local model: it was the best Kev on the development coins. On the held-out coins it tied the built-in scores (no better, no worse), so the built-in scores stay the default.
+- **Claude (zero-shot) ranked best** on both questions, but it needs your Claude login, the network and a small cost per coin, so it is a comparison point, not a default.
+- **Kev 9B** (measured later, on a GPU) is fast, a fraction of a second per coin, but no better. On the development coins it trailed Kev 4B on the drain question. On the held-out coins it tied both the built-in scores and Kev 4B: its 0.79 on the LARP question and 0.53 on drain are within chance variation of theirs. So `kev-4b-q4` stays the suggestion, and the 9B model is there if you want to try it.
+- **Kev 27B and the open JEV models were not measured** (no file llama.cpp can run, or a GPU larger than 16 GB needed). They may do better; we do not know.
+- **Hosted Jev was not measured**: it needs a TypeSafe key, and dexterm's own tests run against a stand-in server only.
+- Kev was trained on general text decisions (intents, reviews, policies), not on memecoins. Its authors' accuracy figures are about those tasks, not this one.
+
+`dexterm classifier bench` times the model you picked on your own machine (seconds per coin and per 1,000 coins).

package/dist/packages/mcp/assets/kb/docs/docs-classifier-set-up-kev-on-your-own-machine.md

@@ -0,0 +1,39 @@
+---
+id: docs-classifier-set-up-kev-on-your-own-machine
+title: Classification models › Set up Kev on your own machine
+kind: docs
+page: classifier
+page_title: Classification models
+heading: Set up Kev on your own machine
+anchor: set-up-kev-on-your-own-machine
+url: https://dexterm.xyz/docs/classifier#set-up-kev-on-your-own-machine
+tags:
+  - docs
+  - classifier
+  - set
+  - kev
+  - own
+  - machine
+  - classification
+  - models
+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/classifier.md
+date: 2026-10-16
+---
+
+```
+1. dexterm classifier doctor               your RAM, CPU and GPU, and the model tier it recommends
+2. dexterm classifier pull kev-4b-q4       shows the size and the source, asks, checks the disk, verifies the sha256
+3. dexterm classifier pick kev-local kev-4b-q4
+4. dexterm classifier serve                runs llama-server on 127.0.0.1 (leave it open)
+5. dexterm classifier try                  one labelled estimate, to see it work
+```
+
+You need llama.cpp's `llama-server` from a build released on 2026-10-02 or later: that is when it gained the `/v1/systemone` endpoint decision models use. Put it on your `PATH`, or point `DEXTERM_LLAMA_SERVER` at it. Downloads come from the pinned revision of the model's Hugging Face repo and are checked against a sha256 before use. Once a model is downloaded, it works fully offline.
+
+If the picked model is not running, the built-in scores answer instead, and the answer says it is a fallback.

package/dist/packages/mcp/assets/kb/docs/docs-classifier-settings.md

@@ -0,0 +1,35 @@
+---
+id: docs-classifier-settings
+title: Classification models › Settings
+kind: docs
+page: classifier
+page_title: Classification models
+heading: Settings
+anchor: settings
+url: https://dexterm.xyz/docs/classifier#settings
+tags:
+  - docs
+  - classifier
+  - settings
+  - classification
+  - models
+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/classifier.md
+date: 2026-10-16
+---
+
+`~/.dexterm/classifier.json` (0600). Only `dexterm classifier` writes it.
+
+| key | what it does |
+|---|---|
+| `provider` | `heuristic` (default), `kev-local`, `jev-hosted`, `jev-open`, `claude`, `ollama-llm` |
+| `default` | the shipped recommendation for a local model |
+| `kev.endpoint`, `kev.model`, `kev.threads` | the local server (loopback only) and the model id |
+| `jev.endpoint`, `jev.model`, `jev.pricePerMTokUsd`, `jev.maxCallsPerDay` | hosted Jev |
+| `calibration` | optional Platt maps per model and question, fitted on labelled rows |
+| `fallback` | answer with the built-in scores when the provider is unreachable (default `true`) |

package/dist/packages/mcp/assets/kb/docs/docs-classifier-the-choices.md

@@ -0,0 +1,36 @@
+---
+id: docs-classifier-the-choices
+title: Classification models › The choices
+kind: docs
+page: classifier
+page_title: Classification models
+heading: The choices
+anchor: the-choices
+url: https://dexterm.xyz/docs/classifier#the-choices
+tags:
+  - docs
+  - classifier
+  - choices
+  - classification
+  - models
+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/classifier.md
+date: 2026-10-16
+---
+
+| provider | what it is | runs where | cost |
+|---|---|---|---|
+| `heuristic` | the built-in scores: the H1 rug score and the LARP link score | inside dexterm | $0, instant |
+| `kev-local` | Kev, an open decision model (Apache-2.0), run by llama.cpp | your machine | $0 per call after the download |
+| `jev-hosted` | Jev, TypeSafe's hosted flagship decision model | TypeSafe's API, with **your own** key | per call, on your TypeSafe account |
+| `jev-open` | the open JEV students (`autotrust/JEV-*`, Apache-2.0) on a vLLM server | your GPU server (24 GB or more) | $0 per call |
+| `claude`, `ollama-llm` | a chat model asked for probabilities (a comparison baseline) | your Claude CLI / your Ollama | your plan / $0 |
+
+A decision model reads the coin's facts once and scores every answer in one pass, without writing text. That is why it can be fast enough to score a whole screener.
+
+The default is `heuristic`: dexterm downloads nothing and calls nothing on first run.