docs: refresh taskmaster roadmap share
This commit is contained in:
Siavash Sameni
@@ -384,12 +384,12 @@
|
||||
<div>
|
||||
<p class="eyebrow">Amanat docs · Taskmaster</p>
|
||||
<h1>Roadmap</h1>
|
||||
<p class="lead">A public planning view generated from the docs-side Taskmaster queue. Track security remediation, payment architecture, refactor decisions, and completed documentation work from one place.</p>
|
||||
<p class="lead">A public planning view generated from the docs-side Taskmaster queue. Track security remediation, payment architecture, Telegram-native work, refactor decisions, and completed documentation work from one place.</p>
|
||||
</div>
|
||||
<aside class="stats">
|
||||
<div class="stat"><strong>4</strong><span>parent tasks</span></div>
|
||||
<div class="stat"><strong>26</strong><span>subtasks</span></div>
|
||||
<div class="stat"><strong>26</strong><span>pending items</span></div>
|
||||
<div class="stat"><strong>5</strong><span>parent tasks</span></div>
|
||||
<div class="stat"><strong>40</strong><span>subtasks</span></div>
|
||||
<div class="stat"><strong>41</strong><span>pending items</span></div>
|
||||
<div class="stat"><strong>4</strong><span>done items</span></div>
|
||||
</aside>
|
||||
</section>
|
||||
@@ -694,6 +694,121 @@
|
||||
</li></ul>
|
||||
</article>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<article class="task" data-status="pending" data-priority="high">
|
||||
<div class="task-head">
|
||||
<div>
|
||||
<p class="eyebrow">Task 5</p>
|
||||
<h2>Deliver Telegram-native app, bot, and wallet experience</h2>
|
||||
</div>
|
||||
<div class="badges"><span class="badge pending">pending</span><span class="badge priority-high">high</span></div>
|
||||
</div>
|
||||
<p class="desc">Create a Telegram bot plus Mini App surface so users can complete Amanat buyer, seller, escrow, chat, dispute, payment, release/refund, and support workflows from inside Telegram.</p>
|
||||
<details>
|
||||
<summary>Details and test strategy</summary>
|
||||
<p>Source PRD: .taskmaster/docs/prd-telegram-native-app-bot-wallet.md. Keep this as a separate delivery track from security remediation and Request Network migration. Identity, bot navigation, Mini App shell, and notifications can start behind flags; wallet/payment crediting and release/refund actions must use canonical backend authorization, provider adapter, funds ledger, escrow state machine, idempotency, and dispute holds.</p>
|
||||
<p><strong>Test strategy:</strong> Use Telegram sandbox and production bot separation, Mini App client matrix testing, provider/wallet payment fixtures, backend authorization and ledger invariant tests, webhook/callback replay tests, and staged rollout analytics before launch.</p>
|
||||
|
||||
</details>
|
||||
<h3>Subtasks (9)</h3>
|
||||
<ul class="subtasks">
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.1</span>
|
||||
<strong>Define Telegram product surface and flow map</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Document which Amanat workflows live in bot messages, which live in the Mini App, and which remain web/admin-only for first release.</p>
|
||||
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.2</span>
|
||||
<strong>Build Telegram identity linking and session model</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Implement secure account linking between Telegram users and Amanat accounts.</p>
|
||||
<p class="deps">Depends on: 5.1</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.3</span>
|
||||
<strong>Implement bot command and notification foundation</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Create the Telegram bot backend for commands, inline keyboards, callback queries, deep links, and outbound notifications.</p>
|
||||
<p class="deps">Depends on: 5.1, 5.2</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.4</span>
|
||||
<strong>Build Telegram Mini App shell for marketplace workflows</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Deliver the mobile-first Mini App that gives users the full Amanat workflow surface inside Telegram.</p>
|
||||
<p class="deps">Depends on: 5.1, 5.2</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.5</span>
|
||||
<strong>Add Telegram payment and wallet strategy</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Evaluate and implement safe payment entry points for Telegram-native users without weakening escrow accounting.</p>
|
||||
<p class="deps">Depends on: 5.2, 5.4</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.6</span>
|
||||
<strong>Expose escrow, delivery, dispute, and release actions safely</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Make Telegram actions useful for real escrow work while preserving backend state authority.</p>
|
||||
<p class="deps">Depends on: 5.4, 5.5</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.7</span>
|
||||
<strong>Add admin and support surface for Telegram-originated cases</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Give support/admin users visibility and controls for Telegram-originated users, payments, and bot events.</p>
|
||||
<p class="deps">Depends on: 5.2, 5.3, 5.5</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.8</span>
|
||||
<strong>Add security, compliance, and abuse controls for Telegram</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Threat-model the Telegram surface and add controls before launch.</p>
|
||||
<p class="deps">Depends on: 5.2, 5.3, 5.5, 5.6</p>
|
||||
</li>
|
||||
<li class="subtask" data-status="pending" data-priority="high">
|
||||
<div class="subtask-top">
|
||||
<span class="sub-id">5.9</span>
|
||||
<strong>Prepare QA, rollout, analytics, and launch operations</strong>
|
||||
<span class="badge pending">pending</span>
|
||||
<span class="badge priority-high">high</span>
|
||||
</div>
|
||||
<p>Prepare the Telegram app and bot for controlled release.</p>
|
||||
<p class="deps">Depends on: 5.3, 5.4, 5.5, 5.6, 5.7, 5.8</p>
|
||||
</li>
|
||||
</ul>
|
||||
</article>
|
||||
<article class="task" data-status="done" data-priority="medium">
|
||||
<div class="task-head">
|
||||
<div>
|
||||
|
||||
Reference in New Issue
Block a user