Core concept
Dynamic workflow
TradingCodex does not route a company name through a preset research template. Head Manager reads the request, answers narrow trusted questions directly, and uses only the specialist work the evidence needs.
Start with a natural mandate #
Use $tcx-workflow for an investment research request. State the outcome, time horizon, important questions, and exclusions in ordinary language. Explicit exclusions such as “No valuation,” “No order,” or “No trading” remain binding through the run.
Example request
$tcx-workflow
Analyze MSFT as a medium-term quality compounder. Include contrary evidence and invalidation conditions. No order.If the request itself is unclear or sensitive, use $tcx-plan in one task to establish the goal, horizon, permitted actions, approval posture, and stop conditions. Bring the resulting mandate to a new $tcx-workflow task; a plan is not a preselected team or server-side workflow.
Choose the first useful wave #
Fresh research begins one lightweight analysis run, then selects the smallest useful set of role profiles. Narrow live-web reconnaissance may resolve the subject and source landscape, but its results remain planning leads; conclusion-relevant facts must be reacquired by an evidence producer. A simple company-facts question may need only fundamental work; a near-term market question may use macro, technical, and news work; a recommendation usually needs independent challenge.
| Role | Question it owns |
|---|---|
| Fundamental | Business, financials, filings, and economics. |
| Technical | Price, trend, momentum, volatility, liquidity, and market structure. |
| News / Macro | Disclosures and chronology; rates, policy, FX, commodities, and transmission. |
| Instrument / Valuation | Instrument mechanics; ranges, scenarios, sensitivities, and evidence gaps. |
| Portfolio / Risk | Portfolio fit, concentration, downside, restrictions, and readiness. |
| Judgment review | An independent challenge of evidence, conflicts, and confidence. |
Head Manager prefers an exact profile and gives every child a compact bounded brief. It can follow up with the same owner for a correction. If a profile is unavailable, a generic child may receive the same research-only scope and no-secret/no-order boundaries. There is no execution subagent.
Reassess from evidence #
Search snippets remain leads until an evidence producer opens the primary record. Save an authenticated artifact when a result supports a decision, reuse, audit, or another role; a narrow bounded answer need not create one. Long runs update when workflow state materially changes or after about a minute without a visible update. A wait timeout alone is not progress, and private reasoning remains hidden.
- Begin when needed. Seal lightweight run provenance and selected optional context.
- Orient. Derive role questions and source leads, never claims, from planning reconnaissance.
- Investigate. Dispatch genuinely independent specialist questions in parallel.
- Correct or extend. Follow up with the owner, add a distinct role, request judgment review, or stop.
- Answer or synthesize. Return the bounded answer directly or create a run-local synthesis from accepted inputs.
There is no server-selected lane, saved team, fixed task queue, or mandatory DAG. The workflow can become smaller, larger, or stop as the evidence warrants.
What dynamic does not mean #
trading-research and the same evidence, secret, policy, broker, and no-order boundaries. Model choice, a skill, or a child cannot create approval or execution authority.- Head Manager may search to plan the workflow, but it does not turn raw reconnaissance into analyst evidence or synthesis claims.
- Current attributable evidence remains the basis for factual claims, even when a Strategy, Brain, or Decision Memory suggests another interpretation.
- A workflow produces evidence and decision support. It does not submit, cancel, approve, or place a broker order.