The five-layer architecture
Each layer has a strict role. They do not collapse into each other. This separation is what makes "AI operates the company; AI cannot authorize capital" enforceable rather than aspirational.
Trading Brain by ARIA is evidence-linked, outcome-proven, user-operable trading intelligence. It preserves sources, claims, shadow decisions, no-actions, outcomes, scoreboards, operations, support, and review posture so a professional user can inspect what the system knows, what it still cannot prove, and where human authority is required.
Each layer has a strict role. They do not collapse into each other. This separation is what makes "AI operates the company; AI cannot authorize capital" enforceable rather than aspirational.
Trading Brain is what a trading intelligence product looks like when professional trust surfaces are first-class. The system does not only generate candidates; it also exposes data freshness, credited sources, evidence gaps, outcome feedback, support issues, and known operational degradation.
The system can run research, monitor topics, collect evidence, generate candidates, write shadow decisions, replay portfolios, label outcomes, update scoreboards, generate evolution candidates, build promotion review packets, write CEO briefs, and produce code through Codex or Claude Code — all without your involvement. What it cannot do: submit a broker order, draft an execution, approve a trade, promote a strategy into production, mutate config, or expand risk budget.
That boundary is enforced in code, in tests, in CI gates, in post-deploy smoke checks, and in the Trust & Operations surface. It is not a tagline.
Trading Brain's design choices come from a small set of principles. Every product decision is checked against whether it improves proof, operability, and boundary discipline.
Process quality is necessary; measured trading and replay results are the proof; feedback into the next cycle is the flywheel. A high-confidence answer with weak provenance or no measured outcome is treated as unproven.
Promotion review must expose credited sources, corroborating evidence, evidence gaps, scoreboard support, and why the system cannot auto-promote.
The system can research, replay, score, and propose. It cannot submit, approve, promote, or mutate runtime live state. LIVE-mode submissions require typed confirmation. Halt is one click and reversible.
From source data to claim, candidate, shadow decision, outcome, scoreboard, and promotion packet, each step is auditable. "AI thinks this is a buy" without an evidence chain is treated as noise, not a signal.
Runtime truth, durable lessons, operating notebook, and orchestration are separate by design. Live state never lives in Obsidian. Lessons never get conflated with today's PnL. The architecture enforces the boundary.
Incidents, support tickets, notification traceability, freshness gaps, and safe repair evidence are part of maturity. A system that cannot explain degradation is not product-ready.
This is the loop ARIA runs every day. Each step has artifacts. Each artifact is auditable. You decide where to interrupt, override, or approve.
Scheduled research generates topic signals from market structure, earnings, filings, news, and source tracking. Topic signals feed a deterministic candidate generator. Output: backtest_candidates.generated.yaml.
Each candidate gets a shadow decision committed to a ledger before any draft. Forward returns at fixed horizons (1d / 3d / 5d / 10d / 20d) label each outcome. Outputs: shadow_decisions.jsonl, signal_outcomes.jsonl.
Outcomes aggregate into strategy and product-maturity scoreboards: outcome proof, calibration, expectancy, evidence quality, learning-loop completeness, operability, support readiness, and authority discipline. Hard vetoes block any score. Output: strategy_scoreboard.json.
When a candidate clears walk-forward across multiple users, sample-size gates, and hard vetoes, a human-readable review packet is generated. Output: evolution_candidates.jsonl, promotion_reports/YYYY-MM-DD.md.
You read the packet, the evidence chain, and the failure modes. You approve, reject, or send back. LIVE submissions require typed confirmation. Promotion requires explicit human action — never automated.
Real fills get post-trade reviews. Durable lessons are written to TrustMem (only generalizable patterns, not today's PnL). Tomorrow's loop starts with sharper priors.
Trading Brain is built for a narrow user. The architecture and discipline make it a poor fit if you want a "trading bot" or a black-box signal stream.
You care about calibration, evidence, and walk-forward gates more than headline returns. You want the loop to be auditable end to end.
Your universe of attention is AI compute, optical, memory, semis, power, cooling. A focused universe helps; a 24-name screener does not.
You believe AI should not authorize capital deployment. The boundary built into Trading Brain's architecture matches your operating principle.
You have seen what "AI trading" usually looks like. You want proof, hard vetoes, evidence chains, and an explicit human gate before you trust anything.
Beta access starts in paper mode. Sign in with Telegram QR or username/password. Read the evidence chain on every signal. Halt is one click. Live promotion requires typed confirmation. Decide whether Trading Brain's discipline matches your own — then decide what to promote.