[Roadmap] Portfolio research and execution roadmap

[brokermr810]

Goal

Build a reproducible path from dynamic universe selection through portfolio research, pair/spread modeling, execution, and auditable analytics.

This issue is the public index for the first roadmap theme. It describes direction, not a release-date promise. Implementation work belongs in scoped child issues and pull requests.

Workstreams

• [Roadmap] Dynamic universe and point-in-time stock screening #251 — Dynamic universe and point-in-time stock screening
• [Roadmap] Portfolio strategies and scheduled rebalancing #252 — Portfolio strategies and scheduled rebalancing
• [Roadmap] Pairs and spread trading foundation #253 — Pairs and spread trading foundation
• [Roadmap] Multi-leg order coordination and recovery #254 — Multi-leg order coordination and recovery
• [Roadmap] Pair-level positions, PnL, and analytics #255 — Pair-level positions, PnL, and analytics
• [Roadmap] External signals and point-in-time strategy gates #256 — External signals and auditable AI entry filters

Sequencing

1. Agree point-in-time universe and portfolio lifecycle contracts.
2. Define pair/spread identity and persistence.
3. Build durable multi-leg execution and recovery.
4. Add reconciled pair analytics and user interfaces.
5. Add external signal gates using the same point-in-time guarantees.

Contribution policy

• Discuss architecture in the relevant epic before opening a large pull request.
• Only scoped work marked Ready and help wanted should be implemented without another design round.
• Comment with the task you want to own and a short implementation plan.
• A maintainer confirms the scope and assigns the issue.
• Post a draft pull request or progress update within seven days after assignment. If no update is posted, the task may be released.
• Keep pull requests focused; do not implement an entire epic in one change.

See ROADMAP.md and CONTRIBUTING.md.

[brokermr810]

The public planning board is now live: QuantDinger Roadmap

Useful views:

• Roadmap timeline: QuantDinger Roadmap (view)
• Delivery board by stage: QuantDinger Roadmap (view)
• Ready for contributors: QuantDinger Roadmap (view)

The current epics are in RFC. Once an epic is split into reviewable tasks, maintainers can move those tasks to Ready and add help wanted so contributors can claim them.

[brokermr810]

The first scoped tasks are ready for contributors: #258 (point-in-time universe contract), #259 (pair/spread identity contract), and #260 (multi-leg execution state machine). Each task has a bounded RFC deliverable and claim instructions. They are visible in the Ready for contributors view.