42 lines
2.0 KiB
Markdown
42 lines
2.0 KiB
Markdown
# BAT-016 Planning: Review decision persistence and reconciliation workbench
|
|
|
|
## Planning Status
|
|
- Status: draft
|
|
- Profile: standard
|
|
- Design Gate: yes
|
|
- Design Gate Rationale: REQ-020 changes persistence schema, application service contracts, MCP tools, Streamlit UI flow, and operating hub aggregation. A design document is required before implementation.
|
|
|
|
## Objective
|
|
Turn REQ-020 into a delivery plan that can be executed by delivery-runner with separated implementation and QC roles.
|
|
|
|
## Work Slices
|
|
1. Persistence foundation
|
|
- Add review decision and reconciliation session schema via additive/idempotent migration.
|
|
- Add repository/service helpers with validation DB coverage.
|
|
2. Application integration
|
|
- Connect cross-transfer review queue, reconciliation report, and uncategorized workbench to persisted decision/session state.
|
|
- Preserve existing response fields with additive extensions only.
|
|
3. Streamlit workbench
|
|
- Add minimal operator actions for record/update/hold/recheck/release.
|
|
- Reflect persisted state in dashboard/workbench counts.
|
|
4. Network MCP surface
|
|
- Add safe read/mutation tools for review decisions and reconciliation sessions.
|
|
- Exclude destructive delete/reset tools.
|
|
5. Baseline and verification
|
|
- Update data model, project structure, runtime flows.
|
|
- Add pytest, contract/smoke, Streamlit AppTest/HTTP smoke, and DB safety evidence.
|
|
|
|
## Acceptance Source
|
|
- REQ-020 Acceptance Criteria 1-10.
|
|
|
|
## Risks
|
|
- Source-of-truth ambiguity between current transaction/account state and persisted decision state.
|
|
- Session granularity mismatch across account-level reconciliation and item-level review decisions.
|
|
- Sensitive memo/payload over-storage.
|
|
- MCP/Streamlit contract drift.
|
|
|
|
## Handoff Readiness
|
|
- Ready for design drafting: yes.
|
|
- Ready for implementation: no; design must define schema, state transitions, and interface contracts first.
|
|
- Lead authority needed before delivery: no additional user decision is currently open; scope is approved in dcy-012 and REQ-020.
|