151 lines
7.4 KiB
Markdown
151 lines
7.4 KiB
Markdown
# Implementation Plan: REV-006 催缴与通知事件设计收口
|
||
|
||
**Branch**: `006-reminder-event-design` | **Date**: 2026-03-18 | **Spec**: [/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/spec.md](/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/spec.md)
|
||
**Input**: Feature specification from `/specs/006-reminder-event-design/spec.md`
|
||
|
||
## Summary
|
||
|
||
本次计划聚焦 `REV-006` 的正式文档收口，而非直接编写 backend 业务代码。目标是在既有主文档中补齐催缴对象生成规则、`IF-REV-013` / `IF-EXT-008` 的职责边界、四态结果语义、历史查询与处置追溯口径，并同步治理台账，使后续研发可基于统一口径继续立项。
|
||
|
||
目标文档包括：
|
||
|
||
- `docs/design/02_Detailed_Design/12_REV_Detailed.md`
|
||
- `docs/design/03_Technical_Design/03_Interface_Design.md`
|
||
- `docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
- `docs/design/00_Management/01_Project_Progress.md`
|
||
- `docs/design/00_Management/03_Task_Checklist.md`
|
||
|
||
## Technical Context
|
||
|
||
**Primary Work Product**: Markdown 正式设计文档、治理台账与 Speckit 规划工件
|
||
**Source of Truth Documents**:
|
||
|
||
- `docs/design/02_Detailed_Design/12_REV_Detailed.md`
|
||
- `docs/design/03_Technical_Design/03_Interface_Design.md`
|
||
- `docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
- `docs/design/01_Overview/03_Summary_Design.md`
|
||
- `AGENTS.md`
|
||
|
||
**Reference Sources**:
|
||
|
||
- `docs/guides/BACKEND_CURRENT_STATUS.md`
|
||
- `docs/design/04_Appendix/Archive/02_Manuals/营收系统_用户操作手册.md`
|
||
- `docs/design/04_Appendix/Archive/03_Design_Docs/营业收费管理系统-概要设计说明书20250912.md`
|
||
|
||
**Validation Commands**:
|
||
|
||
- `make validate-file FILE=docs/design/02_Detailed_Design/12_REV_Detailed.md`
|
||
- `make validate-file FILE=docs/design/03_Technical_Design/03_Interface_Design.md`
|
||
- `make validate-file FILE=docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
- `make check-links`
|
||
- `make validate-mermaid`
|
||
|
||
**Target Scope**:
|
||
|
||
- 收口 `REV-006` 详细设计章节
|
||
- 收口 `IF-REV-013` 与 `IF-EXT-008` 承接口径
|
||
- 回写 `SYS002-REQ-011` 的状态判断、后续研发切入点与治理结论
|
||
- 规划 `01_Project_Progress.md` 与 `03_Task_Checklist.md` 的同步更新动作
|
||
|
||
**Project Type**: 文档治理仓库
|
||
**Constraints**:
|
||
|
||
- 不新增平行正式稿，只回写既有主文档或治理文档
|
||
- 不臆造 backend 已实现能力
|
||
- Archive 仅作为来源核对，不直接替代正式口径
|
||
- 编号、术语、相对路径、Mermaid 图与正文必须一致
|
||
- 正式系统名称统一为“福建水务营收系统”
|
||
|
||
**Scale/Scope**: 跨文档设计收口与治理同步，覆盖详设、接口、管理台账三类文档
|
||
|
||
## Constitution Check
|
||
|
||
*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
|
||
|
||
- [x] **主文档归属已确认**：本次改动只落在 `12_REV_Detailed.md`、`03_Interface_Design.md`、`15_SYS002_Requirement_Breakdown.md` 及管理台账，不新增平行正式稿。
|
||
- [x] **范围基线已确认**：`REV-006` 已同时出现在 `03_Summary_Design.md`、`12_REV_Detailed.md` 与 Archive 范围内，属于可直接推进的交集范围。
|
||
- [x] **Archive 使用方式合规**：Archive 仅作为旧系统催缴记录、停水记录、预存短信场景的来源核对，不直接作为正式文档替身。
|
||
- [x] **一致性影响已列出**：受影响项包括 `REV-006` 模块编号、`IF-REV-013` / `IF-EXT-008` 编号边界、四态状态集、催缴/停复水术语、历史查询口径与 Mermaid 流程图。
|
||
- [x] **校验与台账动作已规划**：已明确单文件校验、全仓链接校验、Mermaid 校验，并规划同步更新 `01_Project_Progress.md` 与 `03_Task_Checklist.md`。
|
||
|
||
## Project Structure
|
||
|
||
### Documentation (this feature)
|
||
|
||
```text
|
||
specs/006-reminder-event-design/
|
||
├── plan.md
|
||
├── research.md
|
||
├── data-model.md
|
||
├── quickstart.md
|
||
├── contracts/
|
||
│ ├── if-rev-013.md
|
||
│ └── if-ext-008.md
|
||
└── tasks.md
|
||
```
|
||
|
||
### Repository Touchpoints
|
||
|
||
```text
|
||
docs/design/
|
||
├── 00_Management/01_Project_Progress.md
|
||
├── 00_Management/03_Task_Checklist.md
|
||
├── 00_Management/15_SYS002_Requirement_Breakdown.md
|
||
├── 01_Overview/03_Summary_Design.md
|
||
├── 02_Detailed_Design/12_REV_Detailed.md
|
||
├── 03_Technical_Design/03_Interface_Design.md
|
||
└── 04_Appendix/Archive/
|
||
```
|
||
|
||
**Structure Decision**:
|
||
|
||
- `12_REV_Detailed.md`：承载 `REV-006` 的业务流程、规则、核心数据与落地边界
|
||
- `03_Interface_Design.md`：承载 `IF-REV-013` / `IF-EXT-008` 的业务接口定义与边界说明
|
||
- `15_SYS002_Requirement_Breakdown.md`：承载 `SYS002-REQ-011` 的实现判断、建议粒度与推进说明
|
||
- `01_Project_Progress.md`：登记本轮正式文档收口动作与验证结果
|
||
- `03_Task_Checklist.md`：登记 `REV-006` 相关治理任务的完成状态
|
||
|
||
## Phase 0: Outline & Research
|
||
|
||
### Research Inputs
|
||
|
||
- 既有 `REV-006` 章节是否已足够承载催缴对象生成、四态结果和联动边界
|
||
- `IF-REV-013` / `IF-EXT-008` 的职责拆分是否与 `SYS-002` / `SYS-010` 边界一致
|
||
- 当前 backend 未见实现骨架的结论，如何在正式文档与治理台账中保守表达
|
||
|
||
### Phase 0 Deliverable
|
||
|
||
- [/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/research.md](/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/research.md)
|
||
|
||
### Research Conclusion
|
||
|
||
- 无额外 `NEEDS CLARIFICATION` 留存。
|
||
- 计划阶段可直接以“文档先行、实现待立项”为结论进入设计与合同化表达。
|
||
|
||
## Phase 1: Design & Contracts
|
||
|
||
### Planned Artifacts
|
||
|
||
- [/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/data-model.md](/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/data-model.md)
|
||
- [/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/contracts/if-rev-013.md](/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/contracts/if-rev-013.md)
|
||
- [/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/contracts/if-ext-008.md](/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/contracts/if-ext-008.md)
|
||
- [/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md](/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md)
|
||
|
||
### Design Decisions
|
||
|
||
- 以“催缴候选对象 -> 催缴任务 -> 消息协同 -> 四态回写 -> 处置追溯”的业务链路组织文档，而非按旧系统页面零散堆砌。
|
||
- 历史催缴、停水、预存短信统一按“历史只读查询口径”承接，不额外承诺独立在线主表。
|
||
- 合同化产物只描述接口业务语义、字段边界和责任划分，不写成 backend API 已实现证明。
|
||
|
||
## Post-Design Constitution Check
|
||
|
||
- [x] **主文档归属保持不变**：Phase 1 产物用于规划与任务拆解，正式结论仍回流既有主文档。
|
||
- [x] **范围未外溢**：设计仍限定在 `REV-006` 催缴与通知收口，不扩展到停复水审批或独立消息中心建设。
|
||
- [x] **Archive 仍为引用源**：未把 Archive 内容直接升级为独立正式稿。
|
||
- [x] **一致性风险已收敛**：四态状态集、接口编号、协同边界和历史查询术语已统一。
|
||
- [x] **校验闭环已具备**：已有明确验证命令、管理台账更新点和后续 tasks 拆解基础。
|
||
|
||
## Complexity Tracking
|
||
|
||
本次计划无宪章违例项，无需额外豁免。
|