simple_ai_trading

Use the pinned external CocoIndex Code MCP workflow for broad repository routing, then prove exact candidates with rg and direct file reads.

Bound repository context reads and semantic-search output without weakening source, test, or evidence verification.

Choose staged contract tests that catch partial AI-generated fixes across models, data, risk, execution ownership, and CLI/Windows parity.

Keep concise user docs and machine-readable model evidence synchronized with real behavior without losing provenance or caveats.

Apply four anti-error coding principles plus this repository's stricter financial-evidence, safety, and single-session rules.

Research the existing implementation, tests, primary technical sources, and financial rationale before adding trading code or dependencies.

Audit financial, data, model, and dependency claims for primary-source quality, dates, provenance, and reproducibility before implementation or publication.

Containerization rules for this repo — pinned base image, non-root user, read-only FS, explicit volumes for config and data.

Python patterns for this repo — pure-stdlib trading core, typed dataclasses, no hidden dependencies, deterministic I/O.

Security checklist for credential handling, request signing, artifact redaction, and order-path guards before any broad change lands.

Risk guardrails that must survive any CLI, strategy, or live-loop change — drawdown caps, daily trade caps, position sanity, leverage clamps.

Validate and debug terminal UI keyboard navigation bugs, frozen menus, modal focus issues, arrow-key handling, Settings/Funds/Strategy navigation, or cross-platform Windows/Linux TUI behavior. Use whenever Codex changes or investigates Textual terminal menus or user reports that a menu cannot move, select, scroll, or close.

Rules for environment-driven configuration — template-backed, typed, documented, never hard-coded.

Binance rate-limit etiquette, backoff rules, and paging caps that must be preserved by any network-touching change.

Practical rules for keeping API keys, PATs, and signed request material out of the repo, logs, and artifacts.

Red-green-refactor workflow adapted for a 100% branch-coverage trading CLI — narrow regression tests first, no coverage regressions.