docs: add initial roadshow presentation outline#515
Conversation
There was a problem hiding this comment.
Reviewed the added presentation outline across code quality, performance, security, and documentation accuracy. Two documentation issues are worth tightening before others build on this deck; no performance or security concerns in the added content.
|
|
||
| 七、产品原则:为什么这么设计 | ||
|
|
||
| 八、核心用户路径:用户如何开始、系统如何判断、结果如何沉淀。 |
There was a problem hiding this comment.
The outline for the "core user path" currently compresses the product flow into "user starts -> system judges -> result settles," which drops several parts of the repository’s canonical main chain: task creation/update, local-service orchestration, risk/authorization handling, and formal delivery via delivery_result / artifact / citation. Because this deck is meant to align later content, omitting those stages will push the presentation toward an inaccurate product story.
|
|
||
|
|
||
|
|
||
| 架构分工ppt |
There was a problem hiding this comment.
架构分工ppt appears as a standalone placeholder rather than a numbered section or note, so the deck structure becomes ambiguous here. Readers cannot tell whether this is part of the same presentation, a second deck, or an editing reminder, which makes the outline harder to extend consistently.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Prepare the presentation outline for the roadshow deck.
This PR focuses on organizing the presentation structure and aligning the high-level storyline for the PPT, so the team can continue filling in detailed content and visuals on top of a clearer narrative frame.
Changes
Impact
Notes