15 KiB
15 KiB
Tasks: SYS-009设计整合与实现对齐
Input: Design documents from /specs/007-sys009-design-align/
Prerequisites: plan.md (required), spec.md (required), research.md, data-model.md, contracts/, quickstart.md
Validation: Validation and evidence tasks are NOT optional. Every feature task set MUST include the applicable document validation, code validation, ledger-sync, and final-verdict tasks.
Organization: Tasks are grouped by user story so each slice can be completed, reviewed, and validated independently.
Format: [ID] [P?] [Story] Description
- [P]: Can run in parallel (different files, no dependencies)
- [Story]: Which user story this task belongs to (e.g., US1, US2, US3)
- Include exact file paths in descriptions
Path Conventions
- Formal workflow:
water-docs/ - Main documents:
docs/design/01_Overview/,docs/design/02_Detailed_Design/,docs/design/03_Technical_Design/ - Governance documents:
docs/design/00_Management/ - Feature artifacts:
specs/007-sys009-design-align/ - Backend modules:
water-backend/... - Frontend modules:
water-frontend/...
Phase 1: Scope, Baseline & Source Confirmation
Purpose: Confirm the source-of-truth set, repo boundary, required reading set, and code baselines before editing anything.
- T001 阅读
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/01_Project_Progress.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/02_Delivery_Standards.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/03_Task_Checklist.md - T002 阅读
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/01_Overview/03_Summary_Design.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/02_Detailed_Design/12_REV_Detailed.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/01_Database_Design.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/03_Interface_Design.md - T003 [P] 阅读
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/04_Writing_Guide.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/08_AI_Agent_Maintenance_SOP.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/10_AI_Retrieval_Whitelist.md、/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/11_Main_Doc_Chapter_Index.md - T004 Confirm target documents, target repos, user story priorities, and exact chapter targets from
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/spec.md - T005 Confirm governing source-of-truth documents, range intersection basis, external references, and validation commands from
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/plan.md - T006 [P] Record the stable repo baselines and key evidence anchors in
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/baseline.md - T007 [P] Confirm the formal alignment contract and verdict rules in
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/contracts/sys009-capability-alignment.mdand/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/contracts/sys009-status-verdicts.md
Phase 2: Shared Foundation
Purpose: Establish the shared alignment baseline for docs, code evidence, and verification outputs.
- T008 Normalize capability names, verdict vocabulary, and
REV-003/REV-008/SYS-009responsibility terms in/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/research.md - T009 [P] Prepare the implementation/evidence checklist and execution order in
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/quickstart.md - T010 [P] Prepare the final evidence output skeleton in
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md
Phase 3: User Story 1 - 整合正式设计口径 (Priority: P1) 🎯 MVP
Goal: 将外部 SYS-009 设计吸收进现有正式主文档，使正式评审不再依赖仓外资料。
Independent Test: 仅阅读 12_REV_Detailed.md、03_Interface_Design.md、03_Summary_Design.md，即可定位实时收费、签解约、送盘/回盘、状态查询、取消送盘、对账/结算的正式口径和章节入口。
Implementation for User Story 1
- T011 [US1] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/02_Detailed_Design/12_REV_Detailed.md，补齐REV-003实时收费与REV-008代扣/托收/送盘/回盘/对账/结算的正式业务边界 - T012 [US1] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/03_Interface_Design.md，补齐签约、解约、客户状态查询、送盘状态查询、取消送盘、回盘状态查询和对账文件规则 - T013 [US1] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/01_Overview/03_Summary_Design.md，同步SYS-009范围摘要和外部接口表的正式描述 - T014 [US1] 同步
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/contracts/sys009-capability-alignment.md中的正式落点结论，确保与主文档实际章节一致 - T015 [US1] 运行
make validate-file FILE=docs/design/02_Detailed_Design/12_REV_Detailed.md并将结果记录到/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md - T016 [US1] 运行
make validate-file FILE=docs/design/03_Technical_Design/03_Interface_Design.md和make validate-file FILE=docs/design/01_Overview/03_Summary_Design.md并将结果记录到/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md
Checkpoint: User Story 1 is independently reviewable with formal SYS-009 design integrated into the main documents.
Phase 4: User Story 2 - 对齐当前实现边界 (Priority: P2)
Goal: 将当前 backend 的真实成熟度结论回写到正式文档和证据工件，避免高估 SYS-009 完成度。
Independent Test: 对照正式文档与 final-verdict.md，评审人能够独立判断 PayCeb、BankWithholding、BankCollection、bk_* 表族和后台管理入口分别处于什么成熟度。
Implementation for User Story 2
- T017 [US2] 核对
/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/controller/app/payceb/PayCebController.java和/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/service/payceb/PayCebServiceImpl.java，确认实时收费查询/缴费/对账的成熟度结论 - T018 [P] [US2] 核对
/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/controller/app/bankwithholding/BankWithholdingController.java和/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/service/bankwithholding/BankWithholdingServiceImpl.java，确认代扣签解约与其余接口的成熟度结论 - T019 [P] [US2] 核对
/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/controller/app/bankcollection/BankCollectionController.java和/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/service/bankcollection/BankCollectionServiceImpl.java，确认托收平行链路的成熟度结论 - T020 [P] [US2] 核对
/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/docs/建表sql.sql与/Volumes/Dpan/github/water-workspace/water-backend/sw-business-bank/sw-business-bank-server/src/main/java/cn/com/emsoft/sw/bankbusiness/controller/admin/下后台管理入口，确认bk_*表族和资源管理层边界 - T021 [US2] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/01_Database_Design.md，补充bk_*表族“对象层齐备但业务编排仅部分实现”的边界说明 - T022 [US2] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/03_Interface_Design.md与/Volumes/Dpan/github/water-workspace/water-docs/docs/design/01_Overview/03_Summary_Design.md，将PayCeb、BankWithholding、BankCollection的真实成熟度回写为保守口径 - T023 [US2] 更新
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md与/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/contracts/sys009-status-verdicts.md，固化本轮实现边界结论 - T024 [US2] 运行
make validate-file FILE=docs/design/03_Technical_Design/01_Database_Design.md并将 backend 证据核对结果写入/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md - T025 [US2] 运行
make validate-file FILE=docs/design/03_Technical_Design/03_Interface_Design.md和make validate-file FILE=docs/design/01_Overview/03_Summary_Design.md并将结果记录到/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md
Checkpoint: User Story 2 is independently reviewable and all maturity statements are tied to concrete backend evidence.
Phase 5: User Story 3 - 形成可审计证据链 (Priority: P3)
Goal: 形成可复用的基线、验证、台账和交付摘要，使后续任务和验收可以直接沿用。
Independent Test: 仅检查 specs/007-sys009-design-align/ 和治理台账，即可确认本轮基线、修订范围、验证动作和剩余未闭环项。
Implementation for User Story 3
- T026 [US3] 更新
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/baseline.md，确认最终使用的 backend/frontend 基线和关键证据路径 - T027 [P] [US3] 更新
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/quickstart.md，使执行顺序、验证命令和回填位置与实际修订结果一致 - T028 [P] [US3] 更新
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/research.md与/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/data-model.md，确保研究结论和实体模型与最终正式口径一致 - T029 [US3] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/01_Project_Progress.md，记录本轮SYS-009设计整合与实现对齐变更摘要 - T030 [US3] 更新
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/03_Task_Checklist.md，回写本轮任务闭环状态和后续待办边界 - T031 [US3] 复核
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/01_Project_Progress.md与/Volumes/Dpan/github/water-workspace/water-docs/docs/design/00_Management/03_Task_Checklist.md的更新内容，并将治理同步结果记录到/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md - T032 [US3] 汇总已修改文件、校验结果、成熟度结论和剩余风险到
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md
Checkpoint: All planning evidence, governance records, and final conclusions are independently reviewable.
Final Phase: Verification & Closure
Purpose: Ensure repository-wide consistency, baseline traceability, and final verdict output.
- T033 [P] Re-check source-of-truth alignment across
/Volumes/Dpan/github/water-workspace/water-docs/docs/design/01_Overview/03_Summary_Design.md,/Volumes/Dpan/github/water-workspace/water-docs/docs/design/02_Detailed_Design/12_REV_Detailed.md,/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/01_Database_Design.md, and/Volumes/Dpan/github/water-workspace/water-docs/docs/design/03_Technical_Design/03_Interface_Design.md - T034 [P] Run
make check-linksandmake validate-mermaidand record the repository-wide results in/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md - T035 Re-check backend baseline SHAs, evidence citations, and governance sync results in
/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/baseline.mdand/Volumes/Dpan/github/water-workspace/water-docs/specs/007-sys009-design-align/final-verdict.md
Dependencies & Execution Order
Phase Dependencies
- Phase 1: Scope, Baseline & Source Confirmation: No dependencies; MUST finish before edits
- Phase 2: Shared Foundation: Depends on Phase 1 and MUST finish before user stories
- Phase 3: User Story 1: Depends on Phase 2; MVP slice
- Phase 4: User Story 2: Depends on Phase 3 because mature capability wording must align to the integrated formal design
- Phase 5: User Story 3: Depends on Phase 3 and Phase 4 because evidence and governance must reflect final doc/evidence state
- Final Phase: Depends on all selected user stories being complete
User Story Completion Order
US1 -> US2 -> US3
Within Each User Story
- Complete formal doc edits before validation
- Complete backend evidence inspection before maturity wording is finalized
- Complete governance updates after document and evidence conclusions stabilize
- Complete final verdict updates after validation and ledger sync are done
Parallel Opportunities
T003,T006, andT007can run in parallel after baseline readingT009andT010can run in parallel- In US2,
T018,T019, andT020can run in parallel because they inspect different capability slices - In US3,
T027andT028can run in parallel because they touch different feature artifacts - In the final phase,
T033andT034can run in parallel
Parallel Execution Examples
User Story 1
Run T015 after T011 completes
Run T016 after T012 and T013 complete
User Story 2
Run T018, T019, and T020 together
Run T021 and T022 after T017-T020 complete
Run T023-T025 after T021 and T022 complete
User Story 3
Run T027 and T028 together
Run T029 and T030 after T026-T028 complete
Run T031 after T029 and T030 complete
Run T032 after T031 complete
Implementation Strategy
MVP First
- Finish Phase 1 and Phase 2
- Deliver US1 only: 先完成正式设计整合，让主文档成为单一评审入口
- Validate US1 before moving to US2
Incremental Delivery
- US1: 正式设计口径收拢
- US2: 当前实现成熟度对齐
- US3: 证据链和治理台账闭环
Notes
- Every task preserves the single-source-of-truth model in
water-docs - Archive and external docs are used for verification and traceability, not direct formal replacement
water-backendonly provides implementation evidence in this round- Validation, evidence, and ledger tasks are mandatory and already included