Problem or Motivation
The public Roadmap table in README.md (+ 4 translations) shows three items as not-yet-shipped, but main already contains their core implementations. This can mislead external contributors into thinking the main work hasn't begun, and can cause duplicate work on items that are already in.
| Roadmap item |
README status (README.md:1169-1174) |
Actual main status |
| Research Autopilot |
Next |
Phase 1/2/3 merged — run_research_autopilot / generate_backtest_config / scaffold_signal_engine / link_autopilot_backtest all live (#260, #267) |
| Data Bridge |
Planned |
Local CSV/Parquet/DuckDB loader merged (#252) |
| Research Delivery |
Planned |
Scheduled-research job model + executor + CRUD + dispatch merged (#272, #278, #288) — only multi-channel outbound delivery is missing |
Evidence (commits on main):
1b71b13 feat(autopilot): scaffold signal engine + auto-link backtest metrics (Phase 3) (#267)
a97af71 feat(loaders): add local data loader for CSV/Parquet/DuckDB files (#252)
e6f4656 feat(scheduled-research): add executor that fires due jobs on schedule (#278)
Proposed Solution
Update the Roadmap table across all 5 READMEs to reflect shipped status — e.g.:
- Research Autopilot →
Phase 1-3 shipped (closed-loop orchestrator pending)
- Data Bridge →
Local loader shipped (SQL connectors planned)
- Research Delivery →
Scheduler + executor shipped (multi-channel delivery in progress)
Alternatives Considered
- Leave as-is and rely on the News section: works, but the Roadmap is the table people check for "where are we", and it currently contradicts News.
Contribution
I'm willing to submit a PR updating all 5 README variants (en/zh/ja/ko/ar) if maintainers agree on the wording. Asking first since Roadmap wording is a product statement — happy to use whatever status labels you prefer.
Area: Documentation
Problem or Motivation
The public Roadmap table in
README.md(+ 4 translations) shows three items as not-yet-shipped, butmainalready contains their core implementations. This can mislead external contributors into thinking the main work hasn't begun, and can cause duplicate work on items that are already in.README.md:1169-1174)mainstatusNextrun_research_autopilot/generate_backtest_config/scaffold_signal_engine/link_autopilot_backtestall live (#260, #267)PlannedPlannedEvidence (commits on
main):1b71b13 feat(autopilot): scaffold signal engine + auto-link backtest metrics (Phase 3) (#267)a97af71 feat(loaders): add local data loader for CSV/Parquet/DuckDB files (#252)e6f4656 feat(scheduled-research): add executor that fires due jobs on schedule (#278)Proposed Solution
Update the Roadmap table across all 5 READMEs to reflect shipped status — e.g.:
Phase 1-3 shipped (closed-loop orchestrator pending)Local loader shipped (SQL connectors planned)Scheduler + executor shipped (multi-channel delivery in progress)Alternatives Considered
Contribution
I'm willing to submit a PR updating all 5 README variants (en/zh/ja/ko/ar) if maintainers agree on the wording. Asking first since Roadmap wording is a product statement — happy to use whatever status labels you prefer.
Area: Documentation