docs: add architecture overview with system diagrams - #62
Conversation
There was a problem hiding this comment.
The architecture document is useful as a target design, but several statements currently read as repository facts while the referenced implementation/configuration is not present. Please either add the missing artifacts or clearly label these items as planned/proposed.
| - 最终工作流能力如何从当前 Demo 演进; | ||
| - 哪些边界和依赖必须长期保持。 | ||
|
|
||
| 当前前端文档 `docs/frontend-architecture.md` 描述的是 **MS2 阶段的前端 FSD 架构**。其中 `WorkflowRun` 是前端用于组织页面推进状态的 Entity,不要求后端建立同名领域模块。前端 Demo 可以直接调用后端的项目、角色、生成、审核、资产和导出接口。 |
There was a problem hiding this comment.
[medium] This references docs/frontend-architecture.md, but that file does not exist on either this PR branch or main. Readers cannot follow the stated MS2 FSD/WorkflowRun context; please add the referenced document or change this to a planned/external reference.
|
|
||
| 源文件:[`backend-layers.json`](diagrams/backend-layers.json) | ||
|
|
||
| 后端采用 uv workspace monorepo,当前由四个独立包组成: |
There was a problem hiding this comment.
[medium] The wording says the repository currently consists of a four-package uv workspace monorepo, but this repository currently contains only README.md plus the new docs and has no workspace/package configuration. Please label this as the target structure until the packages are actually added.
| common | ||
| ``` | ||
|
|
||
| 当前已通过 `import-linter` 强制: |
There was a problem hiding this comment.
[high] This states that import-linter already enforces the dependency rules, but the repository has no Python project configuration, dependency, or lint contract implementing that check. Presenting this as enforced can give contributors false confidence; either add the check or mark it as planned.
变更范围
添加系统架构说明文档,偏向后端理解。