Operator GuideFumadocs + MDXLocal-first

Run paper trading from evidence you can inspect.

Agentic Trader is a local-first paper trading control room. These docs help an operator prepare the runtime, run strict paper cycles, inspect broker/account evidence, and understand why live execution stays blocked until explicitly approved.

Open the guideOpen quick start
Runtime-first
Model service, runtime state, broker state, and review surfaces should agree before we trust a cycle.
Guardrailed
Paper execution, strict LLM gating, provider visibility, and no silent runtime fallbacks remain non-negotiable.
Multi-surface
CLI, Rich, Ink, observer API, and Web GUI all ride the same contracts instead of maintaining UI-only truth.
Current V1 focus
The project is in hardening mode, not in “invent a parallel system” mode.
Optional app-managed Ollama supervision should extend the existing daemon and log surface.
`webgui` stays a thin local shell while `docs` becomes the canonical operator guide with contributor notes behind it.
Bootstrap, provider readiness, and QA evidence are all moving toward a more standardized onboarding path.
Setup
Get Started
Install the repo, run doctor, validate model readiness, and open the main operator surfaces.
Open section
System map
Architecture
Read package ownership, runtime boundaries, and why the repo refuses a parallel orchestration layer.
Open section
Operations
Runtime And Operations
Understand modes, supervision, logs, stop controls, and operator-visible runtime truth.
Open section
Signals
Data And Intelligence
See how market context, provider normalization, and feature bundles feed the agent graph.
Open section
Frontend
Frontend System
Keep `docs` and `webgui` aligned on the shared shadcn preset, local-first monospace typography, and modular file organization.
Open section
Continuity
Decision Evidence And Review
Inspect similar past runs, trade context, manager review, and evidence bundles without confusing product memory with contributor notes.
Open section
Validation
QA And Debugging
Use smoke QA, runtime evidence, and operator-truth checks before treating a change as shippable.
Open section
Setup track
Start with `README.md`, then validate the environment with `doctor`, local model readiness, and the docs quick start.
Architecture track
Use `dev-docs/code-map.md` plus the architecture docs to find the smallest owning module before editing.
Frontend track
`webgui` and `docs` share Next.js App Router, Tailwind v4, and shadcn primitives, but they should not invent a shared package prematurely.

The docs should stay close to the runtime truth, not become a second architecture.