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/)
1.1 KiB
1.1 KiB
taskmaster_id, status, priority, depends_on, parent_id, source, generated_at
| taskmaster_id | status | priority | depends_on | parent_id | source | generated_at |
|---|---|---|---|---|---|---|
| 5.1 | in-progress | high | 5 | taskmaster | 2026-05-24T07:15:25.199Z |
5.1 - Define Telegram product surface and flow map
- 5.1 - Define Telegram product surface and flow map #taskmaster #priority/high #status/in-progress ⏫ 🆔 tm-5-1
Metadata
| Field | Value |
|---|---|
| Taskmaster ID | 5.1 |
| Status | in-progress |
| Priority | high |
| Dependencies | None |
| Parent | 5 - Deliver Telegram-native app, bot, and wallet experience |
Description
Document which Amanat workflows live in bot messages, which live in the Mini App, and which remain web/admin-only for first release.
Details
Map buyer, seller, admin/support, unauthenticated, linked-user, and unlinked-user journeys. Specify deep-link entry points for request details, offer review, payment, dispute, delivery evidence, and account linking. Separate first-release scope from later enhancements and map every Telegram action to backend API/state transitions.
Verification
See Telegram-native PRD acceptance criteria.