Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- The bot is a commerce client and messaging interface; it cannot own wallet balances, transaction admission, provider purchase or master secrets.
- Session/user isolation, safe Telegram message rendering and timeout/expiration constraints are domain requirements.
Verification still required
- Validate user identity handoff, purchases and support conversations against the live approved Commerce interface separately.
- No historical isolated bot test is proof of live Telegram delivery, webhooks or financial reconciliation.
How to update
When the owner changes implementation or contract behavior, update this page and the relevant service interfaces. For cross-service changes, also update the platform interface map or decision register. State the actual verification performed; do not inherit historical pass claims without fresh evidence.