Constraint: Keep payment documentation in existing formal docs rather than creating a parallel guide.\nRejected: Treating biz_payment_record as verified production tables | Current evidence only supports target/prototype semantics.\nConfidence: high\nScope-risk: narrow\nDirective: Do not move payment fact ownership into REV004; REV004 should reference REV003/SYS009 payment facts only.\nTested: make validate-file on main touched docs; make check-ai-governance; git diff --check.\nNot-tested: Full export/render pipeline.
02_Detailed_Design 详细设计入口
目录用途
docs/design/02_Detailed_Design/ 用于维护系统详细设计、模块流程、规则约束与实施指导内容。
权威文档
01_Detailed_Design.md(主文档):详细设计单一真源
关联文档
02_Module_Traceability_Index.md:模块追溯索引(模块-接口-数据域快速定位)03_CA_Esignature_Supplement.md:报装 CA 电子签章专项补充11_UP_Detailed.md:统一平台模块正文12_REV_Detailed.md:营收业务模块正文13_CS_Detailed.md:客户服务模块正文14_METER_Detailed.md:表务模块正文15_INST_Detailed.md:报装与签章模块正文
上游对齐基线
- 总体层模块枚举与承接关系以
../01_Overview/05_Module_Inventory.md作为核对入口; - 当架构图中的模块名称与当前详设正文命名不完全一致时,应优先补充“映射说明”,而不是直接新建平行详设文件。
维护原则
- 详细设计应与概要设计、数据库设计、接口设计保持一致
- 高风险变更(模块拆分、编号体系、流程调整)需先评估影响面
- 变更后需同步更新任务台账与进度记录
- 历史并行稿已迁入
docs/design/04_Appendix/Archive/03_Design_Docs/