165 lines
11 KiB
Markdown
165 lines
11 KiB
Markdown
# Tasks: REV-006 催缴与通知事件设计收口
|
||
|
||
**Input**: Design documents from `/specs/006-reminder-event-design/`
|
||
**Prerequisites**: `plan.md` (required), `spec.md` (required), `research.md`, `data-model.md`, `contracts/`, `quickstart.md`
|
||
|
||
**Validation**: Validation tasks are NOT optional in this repository. Every document change task set includes applicable validation and ledger-sync tasks.
|
||
|
||
**Organization**: Tasks are grouped by user story so each document-maintenance 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 (`US1`, `US2`, `US3`)
|
||
- Every task names the exact file path to update or validate
|
||
|
||
## Phase 1: Setup
|
||
|
||
**Purpose**: Confirm the working boundary, source-of-truth set, and impacted files before editing formal documents.
|
||
|
||
- [x] T001 Confirm target files and impacted chapters in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/spec.md`
|
||
- [x] T002 Confirm source-of-truth and allowed references in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/plan.md` and `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/research.md`
|
||
- [x] T003 [P] Confirm entity and contract inputs in `/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`, and `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/contracts/if-ext-008.md`
|
||
- [x] T004 [P] Confirm governance sync targets in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md`, `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md`, and `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
|
||
---
|
||
|
||
## Phase 2: Foundational
|
||
|
||
**Purpose**: Establish the shared editing baseline that all user stories depend on.
|
||
|
||
- [x] T005 Normalize `REV-006`, `IF-REV-013`, `IF-EXT-008`, and four-state terminology alignment notes in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/plan.md`
|
||
- [x] T006 Identify exact `REV-006` anchors, Mermaid scope, and cross-reference touchpoints in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md` and `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md`
|
||
- [x] T007 Map governance evidence and current implementation conclusion for `SYS002-REQ-011` in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
|
||
---
|
||
|
||
## Phase 3: User Story 1 - 收口催缴任务生成规则 (Priority: P1) 🎯 MVP
|
||
|
||
**Goal**: 补齐 `REV-006` 在详细设计中的催缴对象生成、策略分组、频控边界、四态状态和历史只读承接口径。
|
||
|
||
**Independent Test**: 单独评审 `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md` 的 `REV-006` 章节，应能明确催缴对象来源、排除条件、四态状态、人工核查边界和停复水联动追溯关系。
|
||
|
||
### Implementation for User Story 1
|
||
|
||
- [x] T008 [US1] Update `REV-006` rules, candidate selection, frequency-control, and exclusion conditions in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md`
|
||
- [x] T009 [US1] Sync `Reminder Candidate`, `Reminder Task`, `Reminder Result`, and `Disposal Link` field coverage in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md` using `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/data-model.md`
|
||
- [x] T010 [US1] Align historical reminder, stop-water, and prestored-message read-only boundary wording in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md`
|
||
- [x] T011 [US1] Run `make validate-file FILE=docs/design/02_Detailed_Design/12_REV_Detailed.md` and record the result in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md`
|
||
- [x] T012 [US1] Run `make validate-mermaid` for `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md` flow updates and record the result in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md`
|
||
|
||
**Checkpoint**: User Story 1 is reviewable and validated independently.
|
||
|
||
---
|
||
|
||
## Phase 4: User Story 2 - 统一 IF-REV-013 与消息协同边界 (Priority: P2)
|
||
|
||
**Goal**: 在接口主文档中统一 `IF-REV-013` 与 `IF-EXT-008` 的职责分工、输入输出、四态回写和失败阻断语义。
|
||
|
||
**Independent Test**: 单独评审 `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md`，应能区分 `SYS-002` 的业务任务控制职责与 `SYS-010` 的渠道触达职责，并定位最小回写字段。
|
||
|
||
### Implementation for User Story 2
|
||
|
||
- [x] T013 [US2] Update `IF-REV-013` business boundary, request paths, and state semantics in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md`
|
||
- [x] T014 [US2] Update `IF-EXT-008` collaboration boundary, acceptance/callback semantics, and failure mapping in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md`
|
||
- [x] T015 [US2] [P] Sync minimum traceability fields and manual-verify/write-back semantics in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md` using `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/contracts/if-rev-013.md`
|
||
- [x] T016 [US2] Run `make validate-file FILE=docs/design/03_Technical_Design/03_Interface_Design.md` and record the result in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md`
|
||
- [x] T017 [US2] Run `make check-links` after interface document updates and record the result in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md`
|
||
|
||
**Checkpoint**: User Story 2 is reviewable and validated independently.
|
||
|
||
---
|
||
|
||
## Phase 5: User Story 3 - 形成治理与研发切入结论 (Priority: P3)
|
||
|
||
**Goal**: 在需求拆解和管理台账中沉淀 `REV-006` 的当前状态、最小研发切入点、文档收口动作和验证结论。
|
||
|
||
**Independent Test**: 单独评审 `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`、`/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md`、`/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md`，应能定位 `SYS002-REQ-011` 的“未见实现”判断、本轮文档收口和后续研发建议。
|
||
|
||
### Implementation for User Story 3
|
||
|
||
- [x] T018 [US3] Update `SYS002-REQ-011` implementation judgment, evidence wording, and next-step recommendation in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
- [x] T019 [US3] Update the REV-006 change record and validation summary in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md`
|
||
- [x] T020 [US3] Update the REV-006 governance completion items in `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md`
|
||
- [x] T021 [US3] Run `make validate-file FILE=docs/design/00_Management/15_SYS002_Requirement_Breakdown.md` and record the result in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md`
|
||
- [x] T022 [US3] Re-check that `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md` and `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md` reflect the same REV-006 closure status
|
||
|
||
**Checkpoint**: User Story 3 is reviewable and validated independently.
|
||
|
||
---
|
||
|
||
## Final Phase: Polish & Cross-Cutting Concerns
|
||
|
||
**Purpose**: Ensure repository-wide consistency after all story slices are complete.
|
||
|
||
- [x] T023 [P] Re-check `REV-006`, `IF-REV-013`, `IF-EXT-008`, and four-state terminology consistency across `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md`, `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md`, and `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md`
|
||
- [x] T024 [P] Re-check relative links, anchors, and Mermaid consistency across `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md`, `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md`, `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md`, and `/Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md`
|
||
- [x] T025 Prepare final delivery summary and remaining-risk note in `/Volumes/Dpan/github/fujian_water_biz_doc/specs/006-reminder-event-design/quickstart.md`
|
||
|
||
---
|
||
|
||
## Dependencies & Execution Order
|
||
|
||
### Phase Dependencies
|
||
|
||
- **Setup**: No dependencies; must finish before document edits
|
||
- **Foundational**: Depends on Setup and must finish before user story execution
|
||
- **US1**: Depends on Foundational and is the MVP slice
|
||
- **US2**: Depends on US1 terminology and boundary baseline
|
||
- **US3**: Depends on US1 and US2 conclusions so governance wording can reflect final design state
|
||
- **Final Phase**: Depends on all selected user stories being complete
|
||
|
||
### User Story Dependency Graph
|
||
|
||
```text
|
||
US1 -> US2 -> US3
|
||
\______________-> Final Phase
|
||
```
|
||
|
||
### Within Each User Story
|
||
|
||
- Update target document content before running validation
|
||
- Complete validation before marking governance sync as done
|
||
- Complete ledger sync before final cross-check
|
||
|
||
## Parallel Execution Examples
|
||
|
||
### US1
|
||
|
||
```text
|
||
T008 -> T009
|
||
T010 can run after T008 in parallel with T009
|
||
```
|
||
|
||
### US2
|
||
|
||
```text
|
||
T013 -> T014
|
||
T015 can run in parallel once T013 and T014 establish the final interface wording
|
||
```
|
||
|
||
### US3
|
||
|
||
```text
|
||
T019 and T020 can run in parallel after T018
|
||
```
|
||
|
||
## Implementation Strategy
|
||
|
||
### MVP First
|
||
|
||
先完成 US1，只收口 `12_REV_Detailed.md` 的 `REV-006` 规则与状态语义，形成最小可评审增量。
|
||
|
||
### Incremental Delivery
|
||
|
||
1. 用 US1 固化催缴对象、四态状态和历史只读边界。
|
||
2. 用 US2 固化 `IF-REV-013` / `IF-EXT-008` 的接口职责与回写语义。
|
||
3. 用 US3 回写治理台账和后续研发切入点。
|
||
4. 最后统一做跨文档一致性复核和交付摘要。
|
||
|
||
## Notes
|
||
|
||
- 所有任务均保持“主文档单一真源”原则，不新增平行正式稿。
|
||
- Archive 只用于核对来源，不作为正式结论直接输出。
|
||
- 本任务清单面向文档实施，不默认包含 backend 代码开发任务。
|