Implementation Phase Plans

1. Current Beads issue
2. Referenced phase document under docs/implementation/
3. Architecture plan under docs/plans/
4. Research report under docs/research-docs/

This repository uses docs/research-docs/ for research reports; docs/research/ is not present. Research reports provide rationale and useful constraints, but they do not add active implementation scope unless that scope is explicitly pulled into a phase document and Beads issue.

• Prefer small, reviewable PRs.
• Do not implement an entire architecture plan at once.
• Use Beads issues for execution tracking and dependency management.
• Keep durable architecture and phase detail in these docs, not in long Beads descriptions.
• Synthetic data must emit canonical market event types, not synthetic-only pipeline event types.
• Synthetic labels must remain separate from emitted market events.
• Smart-flow logic must distinguish facts, evidence, hypotheses, confidence, and abstention.
• Historical calibration is future work, not an MVP dependency.
• Early synthetic tests must not require Docker, ClickHouse, NATS, or Redis.
• Synthetic foundations should come before demos, UI controls, or live service work.

islandflow-9dz already tracks tuning synthetic smart-money scenario coverage. It is narrower than these phase plans and was already in progress before this split. Treat it as related context for docs/implementation/synthetic-market-data/03-scenarios-labels-expected-outputs.md, not as the phase-level tracker.