Skip to content

refactor(domain): rename generation to orchestrator, add domain bound… - #76

Open
xiaocheny214 wants to merge 1 commit into
1024XEngineer:mainfrom
xiaocheny214:refactor/domain-rename-orchestrator
Open

refactor(domain): rename generation to orchestrator, add domain bound…#76
xiaocheny214 wants to merge 1 commit into
1024XEngineer:mainfrom
xiaocheny214:refactor/domain-rename-orchestrator

Conversation

@xiaocheny214

Copy link
Copy Markdown
Contributor

…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

…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
@vercel

vercel Bot commented Jul 31, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
windup Ignored Ignored Preview Jul 31, 2026 4:26am

@fennoai fennoai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found two documentation inconsistencies that should be corrected before merging.

"stroke": "#89659e"
},
{
"id": "generation",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[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。

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants