4cf5c49274
- Update data model enums to match backend models - Update API reference auth requirements - Add dispute module references and warning blocks - Add 2026-05-24 audit remediation callout to Overview - Generate task breakdowns and audit artifacts - Add doc alignment report (.taskmaster/reports/)
36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
---
|
|
taskmaster_id: "5.6"
|
|
status: "pending"
|
|
priority: "high"
|
|
depends_on: ["4", "5"]
|
|
parent_id: "5"
|
|
source: "taskmaster"
|
|
generated_at: "2026-05-24T07:15:25.199Z"
|
|
---
|
|
|
|
# 5.6 - Expose escrow, delivery, dispute, and release actions safely
|
|
|
|
- [ ] 5.6 - Expose escrow, delivery, dispute, and release actions safely #taskmaster #priority/high #status/pending ⏫ 🆔 tm-5-6 ⛔ tm-4 ⛔ tm-5
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Taskmaster ID | 5.6 |
|
|
| Status | pending |
|
|
| Priority | high |
|
|
| Dependencies | 4, 5 |
|
|
| Parent | 5 - Deliver Telegram-native app, bot, and wallet experience |
|
|
|
|
## Description
|
|
|
|
Make Telegram actions useful for real escrow work while preserving backend state authority.
|
|
|
|
## Details
|
|
|
|
Telegram users can see current escrow state, next allowed actions, and blockers. Delivery confirmation, evidence upload, refund request, dispute open/respond, and release approval must route through backend precondition checks. High-risk actions require fresh confirmation and audit logging with Telegram context. Disputed or held funds cannot be released through Telegram shortcuts.
|
|
|
|
## Verification
|
|
|
|
See Telegram-native PRD acceptance criteria.
|