Project Story

Plain-language context for why this system is built the way it is, separated from verified implementation facts.

Verified implementation facts

• The active source universe is fixed and small (OV-0001 through OV-0004) — enforced by data/manifests/production_approval.json, not left to free-text prompting.
• A prior source (OV-0005) was deliberately excluded from active runtime influence — see reports/release/ov0005_post_removal_verification_latest.md and src/validation/research_ensemble.py's SEMANTIC_REVIEW_BLOCKED_STRATEGY_IDS.
• The Tauri/Rust layer exists specifically to keep session credentials out of the React webview — redact_sensitive() in apps/desktop/src-tauri/src/main.rs strips session_id/csrf_token from every generic API response before it reaches JavaScript.
• Paper simulation and real execution are structurally separated: scripts/check_capital_execution_boundary.py scans src/capital, src/paper_execution, src/market_data, and services/ml-api for order/leverage/API-key patterns on every validation pass.
• Beginner and Advanced presentation modes exist as a deliberate design layer — see apps/desktop/src/displayMode.tsx and the TechnicalDetailsDisclosure component, which hides raw JSON by default.

Design interpretation (not directly verifiable from a single file)

The following are reasonable interpretations of the design intent, inferred from consistent patterns across many files, rather than a single documented "why" statement in the repository:

• Governance (source approval, semantic review, contradiction indexing) appears designed to prevent a researcher from ever citing an unapproved or contradicted source as evidence for a trading pattern.
• Reports are generated so that every dashboard claim is traceable to a file on disk, rather than an ephemeral in-memory computation.

Known limitations