refactor(domain): rename generation to orchestrator, add domain bound… - #76
refactor(domain): rename generation to orchestrator, add domain bound…#76xiaocheny214 wants to merge 1 commit into
Conversation
…ary docs - Rename server/generation/ to server/orchestrator/ (任务调度) - Update all import references (web/api/generation.py keeps its name) - Update module-split.md with 4-domain structure (foundation/workflow/pipeline/result) - Add domain boundary explanations and rationale - Update product-domains.svg with color coding and domain annotations - Remove unimplemented modules from documentation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
| "stroke": "#89659e" | ||
| }, | ||
| { | ||
| "id": "generation", |
There was a problem hiding this comment.
[P2] Keep the diagram source synchronized with the rendered SVG
This source still defines the node as generation, while the committed product-domains.svg renders the renamed node as orchestrator (and similarly uses preview instead of this source’s playtest). The JSON and SVG therefore describe different domain graphs; regenerate or update both artifacts so future edits do not reintroduce the old names.
| @@ -0,0 +1,205 @@ | |||
| # 后端模块拆分 | |||
|
|
|||
| > 当前阶段:MVP 已实现 project / media / character / orchestrator / ai_engine。 | |||
There was a problem hiding this comment.
[P1] Do not mark the orchestrator as implemented yet
The new module map says the MVP has implemented orchestrator and lists its generation APIs as available, but web/api/generation.py still has TODOs and every submit/query endpoint raises BizException("接口待实现"). This makes the current-state documentation inaccurate for consumers relying on it; either implement the endpoints in this change or describe them as planned/scaffolded.
…ary docs