tradingcodex 2.1.2__tar.gz → 2.1.3__tar.gz

{tradingcodex-2.1.2 → tradingcodex-2.1.3}/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 ## Unreleased
 
+## 2.1.3 - 2026-07-25
+
+- Reduce always-loaded Head Manager and shared source-routing guidance, move
+  optional context and domain rules to their owning workflow resources, remove
+  producer-only dataset tools from the Head Manager, and stop additional
+  research when its expected decision value no longer justifies its cost.
+- Refresh README onboarding around the dynamic research team, reusable
+  knowledge, and skill entrypoints, and recommend `gpt-5.6-sol` with `high` or
+  `xhigh` reasoning for full Head Manager research workflows.
+- Let research answers choose a natural presentation while explaining material
+  results in sufficient detail, and offer a deep explanation from completed
+  research when the user's initial request is best answered concisely.
+
 ## 2.1.2 - 2026-07-24
 
 - Treat ASCII skill-name case and normalized whitespace layout as presentation

tradingcodex-2.1.3/PKG-INFO

@@ -0,0 +1,235 @@
+Metadata-Version: 2.4
+Name: tradingcodex
+Version: 2.1.3
+Summary: Local-first investment operating system for Codex-native research and service-gated execution.
+Author: TradingCodex Authors
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/monarchjuno/tradingcodex
+Project-URL: Documentation, https://github.com/monarchjuno/tradingcodex/blob/main/docs/README.md
+Project-URL: Repository, https://github.com/monarchjuno/tradingcodex.git
+Project-URL: Issues, https://github.com/monarchjuno/tradingcodex/issues
+Keywords: trading,django,codex,mcp,portfolio,research
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 5.2
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Office/Business :: Financial :: Investment
+Requires-Python: <3.15,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: django<5.3,>=5.2
+Requires-Dist: django-ninja<2,>=1.4
+Requires-Dist: markdown-it-py<5,>=3
+Requires-Dist: nh3<0.4,>=0.3
+Requires-Dist: packaging>=24
+Requires-Dist: pydantic>=2
+Requires-Dist: pyarrow==25.0.0
+Requires-Dist: PyYAML>=6
+Requires-Dist: whitenoise<7,>=6.12
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Dynamic: license-file
+
+<h1 align="center">TradingCodex: An Evolving Multi-Agent Investment Team for Codex</h1>
+
+
+<p align="center">
+  <img src="assets/tradingcodex-banner-v3.png" alt="TradingCodex brings market context into a Codex-native investment workflow" width="100%">
+</p>
+
+<div align="center">
+  <a href="https://pypi.org/project/tradingcodex/"><img alt="PyPI" src="https://img.shields.io/pypi/v/tradingcodex?label=PyPI"></a>
+  <a href="LICENSE"><img alt="License" src="https://img.shields.io/badge/license-Apache--2.0-blue"></a>
+  <img alt="Python" src="https://img.shields.io/badge/python-3.11--3.14-3776AB?logo=python&amp;logoColor=white">
+  <img alt="Django" src="https://img.shields.io/badge/Django-5.2-092E20?logo=django&amp;logoColor=white">
+</div>
+
+<p align="center">
+  <a href="#dynamics">Dynamics</a> ·
+  <a href="#statics">Statics</a> ·
+  <a href="#install">Install</a> ·
+  <a href="https://monarchjuno.github.io/tradingcodex/">User Guide</a>
+</p>
+
+TradingCodex brings an evolving investment team into native Codex. Ask a
+question in ordinary language; the right agents collaborate, challenge the
+evidence, and leave behind reusable context for the next decision.
+
+It is research-first, local-first, and paper-first. A research answer never
+becomes a broker action on its own.
+
+## Dynamics
+
+### The team changes with the question
+
+TradingCodex does not send every ticker through the same checklist. Head
+Manager reads the mandate, chooses the smallest useful group of agents, runs
+independent work in parallel when useful, and revises the team when accepted
+evidence exposes a new gap or conflict.
+
+<p align="center">
+  <img src="assets/tradingcodex-dynamics.svg" alt="Head Manager dynamically coordinates nine investment specialist agents in a research loop" width="100%">
+</p>
+
+### The agents
+
+| Agent | What it brings to the team |
+| --- | --- |
+| **Fundamental Analyst** | Business model, financials, filings, and economics. |
+| **Technical Analyst** | Price, trend, momentum, volume, volatility, and liquidity. |
+| **News Analyst** | Disclosures, news, chronology, and narrative change. |
+| **Macro Analyst** | Rates, FX, commodities, policy, and macro transmission. |
+| **Instrument Analyst** | ETF, index, options, crypto, and market-structure mechanics. |
+| **Valuation Analyst** | Ranges, scenarios, sensitivities, and valuation gaps. |
+| **Portfolio Manager** | Portfolio fit, sizing, concentration, and readiness. |
+| **Risk Manager** | Downside, restrictions, risk checks, and approval readiness. |
+| **Judgment Reviewer** | Independent challenge of evidence, conflicts, and confidence. |
+
+### The workflow is a loop
+
+```text
+question
+  -> Head Manager
+  -> smallest useful specialist wave
+  -> accepted evidence and artifacts
+  -> follow up / add a role / request review / synthesize / stop
+  -> next question or decision
+```
+
+The next agent is chosen by the next useful question, not by a preset research
+DAG. A narrow question can stay direct. A high-consequence recommendation can
+expand to independent portfolio, risk, and judgment review. There is no
+execution agent.
+
+## Statics
+
+### The context that stays with you
+
+The current workflow is dynamic. The useful work it produces is static,
+readable, and reusable: files and memory that make the next analysis better
+without hiding the evidence inside a chat or silently changing system rules.
+
+<p align="center">
+  <img src="assets/tradingcodex-statics.svg" alt="TradingCodex stores research memory, Wiki, Brain, and Decision Memory as reusable workspace context" width="100%">
+</p>
+
+| Static layer | What remains after the run |
+| --- | --- |
+| **Research Memory** | Source Snapshots, Datasets, reports, forecasts, decisions, calculations, provenance, and evidence gaps. |
+| **Knowledge Wiki** | Reusable company, product, technology, industry, and value-chain background. Wiki content is context, not current evidence. |
+| **Investment Brain** | Inquiry principles, causal frames, falsifiers, limits, and abstention rules for a selected analysis. |
+| **Decision Memory** | Prior judgments, outcomes, postmortems, lessons, and explicit improvement records for future review. |
+| **Strategy** | Reusable user-owned decision rules that can shape later research without granting execution authority. |
+
+The workspace stays inspectable and versionable:
+
+```text
+trading/
+  research/       # snapshots, datasets, artifacts, calculations
+  reports/        # research reports and handoffs
+  forecasts/      # forward-looking judgments
+  decisions/      # decision context and review history
+wikis/            # local and active Wiki knowledge
+investment-brains/  # user-owned inquiry frameworks
+```
+
+Knowledge, Brain, Strategy, and Decision Memory remain distinct. A Wiki does
+not become proof, a Brain does not choose agents, and an improvement record does
+not silently rewrite prompts, skills, policy, or execution gates.
+
+## Install
+
+For normal use, attach TradingCodex to the folder where you want research to
+live. Do not clone this source repository into that workspace.
+
+You need Git, `uvx`, and an installed, authenticated `codex` CLI.
+
+On macOS/Linux:
+
+```bash
+cd /path/to/an/empty-workspace
+uvx --refresh --from tradingcodex tcx attach . && ./tcx doctor
+./tcx service ensure
+```
+
+On native Windows PowerShell:
+
+```powershell
+cd C:\path\to\an\empty-workspace
+uvx --refresh --from tradingcodex tcx attach .
+.\tcx.cmd doctor
+.\tcx.cmd service ensure
+```
+
+After installation, fully restart Codex, reopen and trust the workspace, and
+trust every TradingCodex hook when Codex prompts you. If hooks are presented
+one at a time, approve each project hook before starting a new task. The viewer
+URL is printed by `./tcx service status`; the release default is
+`http://127.0.0.1:48267/`. End users do not need Node, npm, or a separate
+frontend server.
+
+The Head Manager inherits the active Codex model and reasoning setting. For
+full research workflows, we recommend `gpt-5.6-sol` with `high` or `xhigh`
+reasoning.
+
+### Start with skills
+
+Start with the skill that matches the work. Each example is a prompt you can
+paste into a new Codex task; the [full skill directory](https://monarchjuno.github.io/tradingcodex/skills.html)
+has exact invocation rules, boundaries, and deeper examples.
+
+| Skill | Use it for | Example |
+| --- | --- | --- |
+| [$tcx-plan](https://monarchjuno.github.io/tradingcodex/skill-plan.html) | Frame the outcome, scope, constraints, and stop conditions. | `Clarify a 3-year MSFT quality-compounder mandate. No order.` |
+| [$tcx-workflow](https://monarchjuno.github.io/tradingcodex/skill-workflow.html) | Run dynamic research with the smallest useful team. | `Analyze MSFT as a medium-term quality compounder. Include contrary evidence. No order.` |
+| [$tcx-memory](https://monarchjuno.github.io/tradingcodex/skill-memory.html) | Replay prior judgment and test whether lessons still hold. | `Review the last MSFT thesis against what was known then.` |
+| [$tcx-wiki](https://monarchjuno.github.io/tradingcodex/skill-wiki.html) | Keep reusable company and industry context separate from live evidence. | `Put stable semiconductor value-chain facts from the latest Artifact into the Wiki.` |
+| [$tcx-brain](https://monarchjuno.github.io/tradingcodex/skill-brain.html) | Shape inquiry with user-owned heuristics, falsifiers, and limits. | `Create a cautious quality-compounder inquiry framework.` |
+| [$tcx-strategy](https://monarchjuno.github.io/tradingcodex/skill-strategy.html) | Turn decision rules into a reusable, reviewable method. | `Define entry, sizing, and invalidation rules for quality compounders.` |
+
+Use the viewer to inspect the resulting Episodes, Library, Wiki, and System
+posture. It is read-only; use Codex to continue, narrow, or stop the work.
+
+## The guardrail
+
+Research, Wiki, Brain, Strategy, memory, and automation do not imply broker
+authority. Provider connection, ticket drafting, checks, approval, and final
+action remain separate checkpoints. Paper is built in; live providers require
+their own installation, policy approval, explicit confirmation, sync, and audit
+gates.
+
+Raw credentials never belong in prompts, workspace files, reports, API/MCP
+responses, artifacts, or audit data.
+
+## Learn more
+
+- [Dynamic workflow](https://monarchjuno.github.io/tradingcodex/dynamic-workflow.html)
+  — evidence-driven agent selection, reassessment, and stopping.
+- [Knowledge Wiki](https://monarchjuno.github.io/tradingcodex/skill-wiki.html)
+  — reusable background knowledge and explicit write boundaries.
+- [Investment Brain](https://monarchjuno.github.io/tradingcodex/skill-brain.html)
+  — inquiry and interpretation frameworks.
+- [Improve](https://monarchjuno.github.io/tradingcodex/improve.html) —
+  Decision Memory, postmortems, lessons, and controlled evolution.
+- [Installation](installation.md) — updates, runtime homes, service startup,
+  and recovery.
+- [Safety, policy, and execution](docs/safety-policy-and-execution.md) —
+  permissions, approvals, brokers, secrets, and final-action boundaries.
+- [Documentation index](docs/README.md) — the complete product reference.
+
+## Developing TradingCodex
+
+This repository is product source, not a user workspace. Start with
+[CONTRIBUTING.md](CONTRIBUTING.md), then follow the validation route in
+[docs/validation-and-test-plan.md](docs/validation-and-test-plan.md).
+
+## License
+
+TradingCodex is an Apache-2.0 open-core project. See [LICENSE](LICENSE),
+[NOTICE](NOTICE), and [TRADEMARKS.md](TRADEMARKS.md).

tradingcodex-2.1.3/README.md

@@ -0,0 +1,197 @@
+<h1 align="center">TradingCodex: An Evolving Multi-Agent Investment Team for Codex</h1>
+
+
+<p align="center">
+  <img src="assets/tradingcodex-banner-v3.png" alt="TradingCodex brings market context into a Codex-native investment workflow" width="100%">
+</p>
+
+<div align="center">
+  <a href="https://pypi.org/project/tradingcodex/"><img alt="PyPI" src="https://img.shields.io/pypi/v/tradingcodex?label=PyPI"></a>
+  <a href="LICENSE"><img alt="License" src="https://img.shields.io/badge/license-Apache--2.0-blue"></a>
+  <img alt="Python" src="https://img.shields.io/badge/python-3.11--3.14-3776AB?logo=python&amp;logoColor=white">
+  <img alt="Django" src="https://img.shields.io/badge/Django-5.2-092E20?logo=django&amp;logoColor=white">
+</div>
+
+<p align="center">
+  <a href="#dynamics">Dynamics</a> ·
+  <a href="#statics">Statics</a> ·
+  <a href="#install">Install</a> ·
+  <a href="https://monarchjuno.github.io/tradingcodex/">User Guide</a>
+</p>
+
+TradingCodex brings an evolving investment team into native Codex. Ask a
+question in ordinary language; the right agents collaborate, challenge the
+evidence, and leave behind reusable context for the next decision.
+
+It is research-first, local-first, and paper-first. A research answer never
+becomes a broker action on its own.
+
+## Dynamics
+
+### The team changes with the question
+
+TradingCodex does not send every ticker through the same checklist. Head
+Manager reads the mandate, chooses the smallest useful group of agents, runs
+independent work in parallel when useful, and revises the team when accepted
+evidence exposes a new gap or conflict.
+
+<p align="center">
+  <img src="assets/tradingcodex-dynamics.svg" alt="Head Manager dynamically coordinates nine investment specialist agents in a research loop" width="100%">
+</p>
+
+### The agents
+
+| Agent | What it brings to the team |
+| --- | --- |
+| **Fundamental Analyst** | Business model, financials, filings, and economics. |
+| **Technical Analyst** | Price, trend, momentum, volume, volatility, and liquidity. |
+| **News Analyst** | Disclosures, news, chronology, and narrative change. |
+| **Macro Analyst** | Rates, FX, commodities, policy, and macro transmission. |
+| **Instrument Analyst** | ETF, index, options, crypto, and market-structure mechanics. |
+| **Valuation Analyst** | Ranges, scenarios, sensitivities, and valuation gaps. |
+| **Portfolio Manager** | Portfolio fit, sizing, concentration, and readiness. |
+| **Risk Manager** | Downside, restrictions, risk checks, and approval readiness. |
+| **Judgment Reviewer** | Independent challenge of evidence, conflicts, and confidence. |
+
+### The workflow is a loop
+
+```text
+question
+  -> Head Manager
+  -> smallest useful specialist wave
+  -> accepted evidence and artifacts
+  -> follow up / add a role / request review / synthesize / stop
+  -> next question or decision
+```
+
+The next agent is chosen by the next useful question, not by a preset research
+DAG. A narrow question can stay direct. A high-consequence recommendation can
+expand to independent portfolio, risk, and judgment review. There is no
+execution agent.
+
+## Statics
+
+### The context that stays with you
+
+The current workflow is dynamic. The useful work it produces is static,
+readable, and reusable: files and memory that make the next analysis better
+without hiding the evidence inside a chat or silently changing system rules.
+
+<p align="center">
+  <img src="assets/tradingcodex-statics.svg" alt="TradingCodex stores research memory, Wiki, Brain, and Decision Memory as reusable workspace context" width="100%">
+</p>
+
+| Static layer | What remains after the run |
+| --- | --- |
+| **Research Memory** | Source Snapshots, Datasets, reports, forecasts, decisions, calculations, provenance, and evidence gaps. |
+| **Knowledge Wiki** | Reusable company, product, technology, industry, and value-chain background. Wiki content is context, not current evidence. |
+| **Investment Brain** | Inquiry principles, causal frames, falsifiers, limits, and abstention rules for a selected analysis. |
+| **Decision Memory** | Prior judgments, outcomes, postmortems, lessons, and explicit improvement records for future review. |
+| **Strategy** | Reusable user-owned decision rules that can shape later research without granting execution authority. |
+
+The workspace stays inspectable and versionable:
+
+```text
+trading/
+  research/       # snapshots, datasets, artifacts, calculations
+  reports/        # research reports and handoffs
+  forecasts/      # forward-looking judgments
+  decisions/      # decision context and review history
+wikis/            # local and active Wiki knowledge
+investment-brains/  # user-owned inquiry frameworks
+```
+
+Knowledge, Brain, Strategy, and Decision Memory remain distinct. A Wiki does
+not become proof, a Brain does not choose agents, and an improvement record does
+not silently rewrite prompts, skills, policy, or execution gates.
+
+## Install
+
+For normal use, attach TradingCodex to the folder where you want research to
+live. Do not clone this source repository into that workspace.
+
+You need Git, `uvx`, and an installed, authenticated `codex` CLI.
+
+On macOS/Linux:
+
+```bash
+cd /path/to/an/empty-workspace
+uvx --refresh --from tradingcodex tcx attach . && ./tcx doctor
+./tcx service ensure
+```
+
+On native Windows PowerShell:
+
+```powershell
+cd C:\path\to\an\empty-workspace
+uvx --refresh --from tradingcodex tcx attach .
+.\tcx.cmd doctor
+.\tcx.cmd service ensure
+```
+
+After installation, fully restart Codex, reopen and trust the workspace, and
+trust every TradingCodex hook when Codex prompts you. If hooks are presented
+one at a time, approve each project hook before starting a new task. The viewer
+URL is printed by `./tcx service status`; the release default is
+`http://127.0.0.1:48267/`. End users do not need Node, npm, or a separate
+frontend server.
+
+The Head Manager inherits the active Codex model and reasoning setting. For
+full research workflows, we recommend `gpt-5.6-sol` with `high` or `xhigh`
+reasoning.
+
+### Start with skills
+
+Start with the skill that matches the work. Each example is a prompt you can
+paste into a new Codex task; the [full skill directory](https://monarchjuno.github.io/tradingcodex/skills.html)
+has exact invocation rules, boundaries, and deeper examples.
+
+| Skill | Use it for | Example |
+| --- | --- | --- |
+| [$tcx-plan](https://monarchjuno.github.io/tradingcodex/skill-plan.html) | Frame the outcome, scope, constraints, and stop conditions. | `Clarify a 3-year MSFT quality-compounder mandate. No order.` |
+| [$tcx-workflow](https://monarchjuno.github.io/tradingcodex/skill-workflow.html) | Run dynamic research with the smallest useful team. | `Analyze MSFT as a medium-term quality compounder. Include contrary evidence. No order.` |
+| [$tcx-memory](https://monarchjuno.github.io/tradingcodex/skill-memory.html) | Replay prior judgment and test whether lessons still hold. | `Review the last MSFT thesis against what was known then.` |
+| [$tcx-wiki](https://monarchjuno.github.io/tradingcodex/skill-wiki.html) | Keep reusable company and industry context separate from live evidence. | `Put stable semiconductor value-chain facts from the latest Artifact into the Wiki.` |
+| [$tcx-brain](https://monarchjuno.github.io/tradingcodex/skill-brain.html) | Shape inquiry with user-owned heuristics, falsifiers, and limits. | `Create a cautious quality-compounder inquiry framework.` |
+| [$tcx-strategy](https://monarchjuno.github.io/tradingcodex/skill-strategy.html) | Turn decision rules into a reusable, reviewable method. | `Define entry, sizing, and invalidation rules for quality compounders.` |
+
+Use the viewer to inspect the resulting Episodes, Library, Wiki, and System
+posture. It is read-only; use Codex to continue, narrow, or stop the work.
+
+## The guardrail
+
+Research, Wiki, Brain, Strategy, memory, and automation do not imply broker
+authority. Provider connection, ticket drafting, checks, approval, and final
+action remain separate checkpoints. Paper is built in; live providers require
+their own installation, policy approval, explicit confirmation, sync, and audit
+gates.
+
+Raw credentials never belong in prompts, workspace files, reports, API/MCP
+responses, artifacts, or audit data.
+
+## Learn more
+
+- [Dynamic workflow](https://monarchjuno.github.io/tradingcodex/dynamic-workflow.html)
+  — evidence-driven agent selection, reassessment, and stopping.
+- [Knowledge Wiki](https://monarchjuno.github.io/tradingcodex/skill-wiki.html)
+  — reusable background knowledge and explicit write boundaries.
+- [Investment Brain](https://monarchjuno.github.io/tradingcodex/skill-brain.html)
+  — inquiry and interpretation frameworks.
+- [Improve](https://monarchjuno.github.io/tradingcodex/improve.html) —
+  Decision Memory, postmortems, lessons, and controlled evolution.
+- [Installation](installation.md) — updates, runtime homes, service startup,
+  and recovery.
+- [Safety, policy, and execution](docs/safety-policy-and-execution.md) —
+  permissions, approvals, brokers, secrets, and final-action boundaries.
+- [Documentation index](docs/README.md) — the complete product reference.
+
+## Developing TradingCodex
+
+This repository is product source, not a user workspace. Start with
+[CONTRIBUTING.md](CONTRIBUTING.md), then follow the validation route in
+[docs/validation-and-test-plan.md](docs/validation-and-test-plan.md).
+
+## License
+
+TradingCodex is an Apache-2.0 open-core project. See [LICENSE](LICENSE),
+[NOTICE](NOTICE), and [TRADEMARKS.md](TRADEMARKS.md).

tradingcodex-2.1.3/assets/tradingcodex-dynamics.svg

@@ -0,0 +1,109 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1400 840" role="img" aria-labelledby="title desc">
+  <title id="title">TradingCodex dynamic multi-agent workflow</title>
+  <desc id="desc">Head Manager receives a user question, selects a useful subset from nine individual agents, collects evidence, and loops back to reassess the next step.</desc>
+  <style>
+    .title { font-family: Arial, sans-serif; font-size: 36px; font-weight: 700; }
+    .subtitle { font-family: Arial, sans-serif; font-size: 19px; font-weight: 400; }
+    .label { font-family: Arial, sans-serif; font-size: 13px; font-weight: 700; letter-spacing: 1.4px; }
+    .box-title { font-family: Arial, sans-serif; font-size: 23px; font-weight: 700; }
+    .role { font-family: Arial, sans-serif; font-size: 17px; font-weight: 700; }
+    .body { font-family: Arial, sans-serif; font-size: 15px; font-weight: 400; }
+    .small { font-family: Arial, sans-serif; font-size: 14px; font-weight: 400; }
+    .footer { font-family: Arial, sans-serif; font-size: 18px; font-weight: 700; }
+  </style>
+
+  <rect width="1400" height="840" rx="28" fill="#0b1627"/>
+  <path d="M0 135 H1400 M0 300 H1400 M0 465 H1400 M0 630 H1400" stroke="#b5cfff" stroke-opacity="0.05"/>
+  <path d="M90 0 V840 M440 0 V840 M790 0 V840 M1140 0 V840" stroke="#b5cfff" stroke-opacity="0.05"/>
+
+  <text x="70" y="72" fill="#f4f8ff" class="title">Dynamics: the team changes with the question</text>
+  <text x="70" y="108" fill="#afc1d8" class="subtitle">Head Manager selects the smallest useful set of agents, then lets evidence choose what happens next.</text>
+
+  <!-- Connectors are deliberately drawn before the cards so no line crosses a box. -->
+  <g fill="none" stroke="#68ddff" stroke-width="3" stroke-opacity="0.75">
+    <path d="M330 190 H485"/>
+    <path d="M700 250 V292"/>
+    <path d="M255 292 H1145" stroke-dasharray="8 10"/>
+    <path d="M255 292 V322"/>
+    <path d="M700 292 V322"/>
+    <path d="M1145 292 V322"/>
+    <path d="M255 386 V397 M700 386 V397 M1145 386 V397"/>
+    <path d="M255 397 H1145" stroke-dasharray="8 10"/>
+    <path d="M255 397 V408 M700 397 V408 M1145 397 V408"/>
+    <path d="M255 472 V483 M700 472 V483 M1145 472 V483"/>
+    <path d="M255 483 H1145" stroke-dasharray="8 10"/>
+    <path d="M255 483 V494 M700 483 V494 M1145 483 V494"/>
+  </g>
+
+  <g fill="none" stroke="#66d9bf" stroke-width="3" stroke-opacity="0.8">
+    <path d="M255 558 V610 M700 558 V610 M1145 558 V610"/>
+    <path d="M255 610 H1145"/>
+    <path d="M600 610 V660"/>
+    <path d="M840 705 H900" stroke="#b493ff" stroke-dasharray="8 8"/>
+    <path d="M888 698 L900 705 L888 712" stroke="#b493ff"/>
+  </g>
+
+  <g fill="none" stroke="#b493ff" stroke-width="3" stroke-opacity="0.85" stroke-dasharray="9 8">
+    <path d="M1300 705 H1375 V120 H700 V128"/>
+    <path d="M692 116 L700 128 L708 116" stroke-dasharray="none"/>
+  </g>
+
+  <g>
+    <rect x="70" y="145" width="260" height="90" rx="18" fill="#142a40" stroke="#66d9bf" stroke-width="2"/>
+    <text x="96" y="176" fill="#73e2d0" class="label">START</text>
+    <text x="96" y="208" fill="#f4f8ff" class="box-title">User question</text>
+    <text x="96" y="228" fill="#c0d0e3" class="small">outcome, scope, constraints</text>
+
+    <rect x="485" y="130" width="430" height="120" rx="22" fill="#1f4162" stroke="#68ddff" stroke-width="2"/>
+    <text x="520" y="166" fill="#8fe8ff" class="label">COORDINATOR</text>
+    <text x="520" y="205" fill="#f4f8ff" class="box-title">Head Manager</text>
+    <text x="520" y="232" fill="#c8d7ee" class="body">interpret -> select -> reassess -> synthesize</text>
+
+  </g>
+
+  <g>
+    <rect x="60" y="322" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="84" y="351" fill="#f4f8ff" class="role">Fundamental Analyst</text>
+    <text x="84" y="373" fill="#c0d0e3" class="small">business, financials, filings</text>
+    <rect x="505" y="322" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="529" y="351" fill="#f4f8ff" class="role">Technical Analyst</text>
+    <text x="529" y="373" fill="#c0d0e3" class="small">price, trend, volatility, liquidity</text>
+    <rect x="950" y="322" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="974" y="351" fill="#f4f8ff" class="role">News Analyst</text>
+    <text x="974" y="373" fill="#c0d0e3" class="small">disclosures, chronology, narrative</text>
+
+    <rect x="60" y="408" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="84" y="437" fill="#f4f8ff" class="role">Macro Analyst</text>
+    <text x="84" y="459" fill="#c0d0e3" class="small">rates, FX, policy transmission</text>
+    <rect x="505" y="408" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="529" y="437" fill="#f4f8ff" class="role">Instrument Analyst</text>
+    <text x="529" y="459" fill="#c0d0e3" class="small">ETF, options, crypto mechanics</text>
+    <rect x="950" y="408" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="974" y="437" fill="#f4f8ff" class="role">Valuation Analyst</text>
+    <text x="974" y="459" fill="#c0d0e3" class="small">ranges, scenarios, sensitivities</text>
+
+    <rect x="60" y="494" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="84" y="523" fill="#f4f8ff" class="role">Portfolio Manager</text>
+    <text x="84" y="545" fill="#c0d0e3" class="small">fit, sizing, concentration</text>
+    <rect x="505" y="494" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="529" y="523" fill="#f4f8ff" class="role">Risk Manager</text>
+    <text x="529" y="545" fill="#c0d0e3" class="small">downside, restrictions, readiness</text>
+    <rect x="950" y="494" width="390" height="64" rx="16" fill="#14253c" stroke="#56dfff" stroke-width="1.5"/>
+    <text x="974" y="523" fill="#f4f8ff" class="role">Judgment Reviewer</text>
+    <text x="974" y="545" fill="#c0d0e3" class="small">independent challenge, conflicts</text>
+  </g>
+
+  <g>
+    <rect x="360" y="670" width="480" height="90" rx="20" fill="#142b40" stroke="#66d9bf" stroke-width="2"/>
+    <text x="395" y="704" fill="#73e2d0" class="label">SHARED OUTPUT</text>
+    <text x="395" y="735" fill="#f4f8ff" class="box-title">Accepted evidence + artifacts</text>
+    <text x="395" y="753" fill="#c0d0e3" class="small">snapshots, datasets, reports, forecasts</text>
+
+    <rect x="900" y="670" width="400" height="90" rx="20" fill="#25203a" stroke="#b493ff" stroke-width="2"/>
+    <text x="935" y="704" fill="#c4a9ff" class="label">LOOP BACK</text>
+    <text x="935" y="735" fill="#f4f8ff" class="box-title">Reassess -&gt; Head Manager</text>
+    <text x="935" y="753" fill="#d5c8ed" class="small">follow up / add / review / stop</text>
+  </g>
+
+  <text x="70" y="805" fill="#f5e8f2" class="footer">No fixed team. No preset DAG. The next useful question chooses the next useful agent.</text>
+</svg>

tradingcodex-2.1.3/assets/tradingcodex-statics.svg

@@ -0,0 +1,54 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1400 680" role="img" aria-labelledby="title desc">
+  <title id="title">TradingCodex static memory and context</title>
+  <desc id="desc">Research Memory, Knowledge Wiki, Investment Brain, and Decision Memory remain as reusable context for future investment work.</desc>
+  <style>
+    .title { font-family: Arial, sans-serif; font-size: 36px; font-weight: 700; }
+    .subtitle { font-family: Arial, sans-serif; font-size: 19px; font-weight: 400; }
+    .card-title { font-family: Arial, sans-serif; font-size: 23px; font-weight: 700; }
+    .body { font-family: Arial, sans-serif; font-size: 17px; font-weight: 400; }
+    .label { font-family: Arial, sans-serif; font-size: 13px; font-weight: 700; letter-spacing: 1.4px; }
+  </style>
+
+  <rect width="1400" height="680" rx="28" fill="#0b1627"/>
+  <path d="M0 135 H1400 M0 340 H1400 M0 545 H1400" stroke="#b5cfff" stroke-opacity="0.05"/>
+  <path d="M110 0 V680 M460 0 V680 M810 0 V680 M1160 0 V680" stroke="#b5cfff" stroke-opacity="0.05"/>
+
+  <text x="70" y="72" fill="#f4f8ff" class="title">Statics: the context that stays with you</text>
+  <text x="70" y="108" fill="#afc1d8" class="subtitle">The current run is dynamic. Useful memory remains readable, reusable, and yours.</text>
+
+  <g>
+    <rect x="54" y="155" width="610" height="205" rx="22" fill="#0e1c2e" stroke="#56dfff" stroke-width="2"/>
+    <circle cx="96" cy="202" r="17" fill="#56dfff"/>
+    <text x="130" y="210" fill="#f4f8ff" class="card-title">Research Memory</text>
+    <text x="96" y="255" fill="#c0d0e3" class="body">Snapshots, datasets, reports, forecasts, decisions,</text>
+    <text x="96" y="282" fill="#c0d0e3" class="body">calculations, provenance, and source/as-of posture.</text>
+    <text x="96" y="327" fill="#73e2d0" class="label">EVIDENCE THAT SURVIVES THE CHAT</text>
+  </g>
+
+  <g>
+    <rect x="736" y="155" width="610" height="205" rx="22" fill="#0e1c2e" stroke="#b493ff" stroke-width="2"/>
+    <circle cx="778" cy="202" r="17" fill="#b493ff"/>
+    <text x="812" y="210" fill="#f4f8ff" class="card-title">Knowledge Wiki</text>
+    <text x="778" y="255" fill="#c0d0e3" class="body">Reusable company, industry, product, technology,</text>
+    <text x="778" y="282" fill="#c0d0e3" class="body">and value-chain background.</text>
+    <text x="778" y="327" fill="#73e2d0" class="label">BACKGROUND, NOT PROOF</text>
+  </g>
+
+  <g>
+    <rect x="54" y="405" width="610" height="205" rx="22" fill="#0e1c2e" stroke="#66d9bf" stroke-width="2"/>
+    <circle cx="96" cy="452" r="17" fill="#66d9bf"/>
+    <text x="130" y="460" fill="#f4f8ff" class="card-title">Investment Brain</text>
+    <text x="96" y="505" fill="#c0d0e3" class="body">Inquiry principles, causal frames, falsifiers, limits,</text>
+    <text x="96" y="532" fill="#c0d0e3" class="body">and abstention rules for a selected run.</text>
+    <text x="96" y="577" fill="#73e2d0" class="label">HOW TO THINK, NOT WHAT TO CLAIM</text>
+  </g>
+
+  <g>
+    <rect x="736" y="405" width="610" height="205" rx="22" fill="#0e1c2e" stroke="#ffd27c" stroke-width="2"/>
+    <circle cx="778" cy="452" r="17" fill="#ffd27c"/>
+    <text x="812" y="460" fill="#f4f8ff" class="card-title">Decision Memory</text>
+    <text x="778" y="505" fill="#c0d0e3" class="body">Past judgments, forecasts, postmortems, lessons,</text>
+    <text x="778" y="532" fill="#c0d0e3" class="body">and explicit improvement review.</text>
+    <text x="778" y="577" fill="#73e2d0" class="label">HUMAN-CONTROLLED REVIEW</text>
+  </g>
+</svg>

{tradingcodex-2.1.2 → tradingcodex-2.1.3}/docs/data-sources-and-openbb.md

@@ -23,6 +23,9 @@ This is a short operating procedure, not a service-side source-rating system or
 a guarantee about a third party. A role names the provider where possible, does
 not repeat an unchanged request to the same source, and keeps a partial result
 while asking the next source only for the missing field, identifier, or period.
+It continues only when another obtainable source has a credible path to
+changing the conclusion, confidence, or readiness and its expected decision
+value justifies the added work.
 TradingCodex does not install, classify, proxy, approve, or audit a user-owned
 capability. The normal research safety boundaries still apply: never expose a
 secret or mix research retrieval with account, order, or other mutation work.
@@ -71,14 +74,11 @@ epoch values are converted once; neither is repaired by inventing a timezone.
 A material missing slice that remains obtainable is fetched from the next
 relevant source or returned to its live owner before an evidence-gap abstention.
 
-The procedure adds point-in-time context only when structured or historical
-evidence matters to a conclusion. It preserves issuer identity and
-instrument/venue, unit/currency/timezone, raw-versus-adjusted price policy,
-filing timing/period/amendment posture, and macro first-release or vintage
-posture versus a current revision. It also makes as-of/known-at/freshness,
-empty/partial/stale/authentication/entitlement/rate-limit warnings, material
-conflicts, and remaining coverage gaps visible. Narrow facts do not carry a
-full evidence checklist.
+The common gate owns source choice, freshness, time ambiguity, bounded
+verification, and provenance. The active role skill owns domain-specific
+filing, market-data, corporate-action, instrument, and macro-vintage
+requirements. Together they preserve only the point-in-time context needed for
+the conclusion; narrow facts do not carry a full evidence checklist.
 
 ## Evidence records