Qiongli Roadmap Authority
This directory separates one program roadmap from live evidence and historical migration records.
The public GitHub Projects roadmap mirrors release Milestones and bounded Epic Issues for collaboration. It is a derived view, not another priority queue.
Current authority
- Qiongli 2 Research Harness Master Roadmap is the sole authority for product direction, ordering, milestones, and the current execution horizon.
- Qiongli Program Ledger v1 is the machine-readable authority for the six live task states, dependencies, and exact acceptance evidence. Its generated current program index is a review view, not the owner of next-work priority.
- Qiongli 2.0.0-alpha.3 Completion and Release Plan remains the execution authority for the Alpha 3 A5-A9 release gates.
- Qiongli 2.0.0-alpha.3 Acceptance Ledger remains the evidence authority for that release.
- Accepted files under
docs/architecture/decisions/remain architecture authority. A roadmap may sequence an ADR follow-up, but it does not silently rewrite an accepted decision.
One Trellis task selects a bounded work package from the current horizon. Daily development, PR, target build, and release each apply their own gate; none of those lanes changes product priority or implies the next lane passed.
Historical roadmaps
The dated Rust migration, unified-platform, Marketplace Lite, adaptive-subject, and UI migration roadmaps remain useful design and acceptance history. They no longer determine post-Alpha-3 priority when they conflict with the master roadmap above.
Historical completion must be established from an acceptance ledger, exact commit, or CI receipt. Unchecked Markdown boxes in an old plan are not an authoritative backlog.