37 lines
2.0 KiB
Markdown
37 lines
2.0 KiB
Markdown
# BAT-016: Review decision persistence and reconciliation workbench
|
|
|
|
- Profile: standard
|
|
- Status: draft
|
|
- Included REQ: REQ-020
|
|
- Source Discovery: dcy-012
|
|
- Created At (KST): 2026-07-08 00:00 KST
|
|
|
|
## Objective
|
|
Deliver the approved REQ-020 scope for persisted review decisions, reconciliation sessions, Streamlit workbench actions, network MCP additive tools, operating hub indicators, and baseline documentation.
|
|
|
|
## Included Scope
|
|
- Additive/idempotent persistence for `review_decisions` and `reconciliation_sessions` or an equivalent structure.
|
|
- Application/service integration for cross-transfer review queue, reconciliation report, and uncategorized workbench.
|
|
- Streamlit workbench actions for decision create/update/hold/recheck/release.
|
|
- Network MCP tools for safe review decision/session read and mutation operations.
|
|
- Operating hub indicators for pending review, held/recheck, unreconciled accounts, last reconciliation close time, and uncategorized recommendation backlog.
|
|
- Baseline updates in `docs/data-model.md`, `docs/project-structure.md`, and `docs/runtime-flows.md`.
|
|
|
|
## Excluded Scope
|
|
- Additional HTTP transport redesign beyond the existing dcy-013 network MCP endpoint.
|
|
- Multi-user authorization and role-based approval workflows.
|
|
- Automatic scheduling, push notifications, and external messaging integrations.
|
|
- AI-based final decision automation.
|
|
- Raw financial evidence storage expansion or sensitive source payload retention.
|
|
- Destructive delete/reset MCP tools for review decisions or reconciliation sessions.
|
|
|
|
## Documents
|
|
- [planning.md](planning.md)
|
|
- [design.md](design.md)
|
|
- [implementation.md](implementation.md)
|
|
- [verification.md](verification.md)
|
|
|
|
## Harness Notes
|
|
- This batch is `standard` because REQ-020 changes persistence, interface surface, runtime flow, Streamlit UI, MCP tools, and baseline docs.
|
|
- After this batch scaffold is committed, lead should issue a kanban-backed `lead -> delivery-runner` kickoff on the shared development execution board.
|