Agentic Trader Docs

Agentic Trader Guide

Start here to install Agentic Trader, check readiness, run paper cycles, and review what happened.

What Agentic Trader is

Agentic Trader is a local-first trading research and paper-operation system. It combines market context, specialist analysis, memory/review evidence, broker state, and operator controls into one inspectable runtime.

The current V1 posture is deliberately cautious:

  • paper trading is the default
  • supported V1 active trading must pass approval and readiness gates
  • ungated real-money execution is blocked
  • readiness gates must be explicit
  • missing provider, broker, or model evidence must stay visible
  • every operator surface should describe the same runtime truth

Use this guide to understand what the system can do today, how to run it safely, and how to review a decision before trusting the next one.

Reading paths by operator task

First setup

  1. Read Getting Started.
  2. Run doctor, provider-diagnostics, and v1-readiness.
  3. Open the Ink control room or Web GUI only after the lower-layer checks agree.

Before a paper cycle

  1. Read Runtime And Operations.
  2. Check provider, model, broker, and runtime-mode readiness.
  3. Read Security Posture before exposing Web GUI or observer surfaces beyond localhost.
  4. Keep the run paper-first unless the broker, account, approval, risk, and kill-switch gates explicitly say otherwise.

Review what happened

  1. Read Memory And Review.
  2. Inspect the review snapshot, market context, broker state, logs, and evidence bundle.
  3. Treat missing or stale evidence as a real signal, not a cosmetic warning.

Troubleshoot a confusing state

  1. Read QA And Debugging.
  2. Compare CLI JSON, observer API, Rich/Ink/Web GUI status, and persisted records.
  3. Prefer runtime evidence over what a single UI banner appears to say.

Contributor path

If you are changing code, read these after the operator path:

  1. Architecture
  2. Agent Pipeline
  3. Operator Surfaces
  4. Frontend System

Core non-negotiables

  • Local-first remains the default operating posture.
  • Paper trading remains the safe default execution mode.
  • Silent fallbacks are not acceptable when they hide degraded truth.
  • CLI, Rich, Ink, observer API, and Web GUI should describe the same runtime state.
  • The docs app and the Web GUI are shells around the existing runtime, not replacements for it.

What this guide should explain

This docs site should answer operator questions first:

  • What can Agentic Trader do today?
  • Which mode am I in: training, local paper, external paper readiness, or blocked live?
  • What data did the system actually see?
  • Why did it approve, block, hold, or reject an action?
  • Where can I verify broker/account, runtime, memory, and review truth?

Contributor notes still belong here when they help maintain the system, but they should not replace product explanations or hide operational risk.

Contributor maintenance contract

If a change moves runtime behavior, product direction, operator workflow, or developer assumptions, update all of the following in the same branch:

  • the affected docs page
  • .ai/current-state.instructions.md
  • .ai/tasks.instructions.md
  • .ai/decisions.instructions.md

That keeps the docs site, repo memory, and implementation from drifting apart.

How was this page?
This GitHub Pages build prepares a browser-local feedback draft and a prefilled GitHub issue. Node-hosted local docs can still wire feedback into runtime logs later.

Stores a draft in this browser and gives you a GitHub issue link to submit when ready.

Getting Started

Install the local runtime, verify readiness, and open the control surfaces without hiding failures.

On this page

What Agentic Trader isReading paths by operator taskFirst setupBefore a paper cycleReview what happenedTroubleshoot a confusing stateContributor pathCore non-negotiablesWhat this guide should explainContributor maintenance contract