Command families
Useful public commands without exposing admin controls
The bot page should help users understand what LivingBootBOT can do, while admin-only settings, private moderation logs, and account data stay protected.
Telegram login can confirm identity for the app without asking users to post tokens or passwords in public.
Latest build, minimum version, known issues, store news, and incident posts should be short and dated.
Package, billing, creator, account, and private moderation issues move to the right support route.
Reviewed knowledge can answer boot animation questions and link users to docs instead of guessing.
Submission status, creator showcases, featured packs, and compatibility notes can route users back to CRYA surfaces.
Rules, reports, warnings, anti-flood, and topic routing keep public help useful without leaking private actions.
Login flow
Identity handoff should feel simple
Telegram login is useful only when the public explanation is clear and the sensitive parts remain private.
User opens the bot from the app, website, or group command.
Bot confirms Telegram identity and creates a short-lived login state.
Backend connects the Telegram profile to the CRYA account with provider badges.
The app and admin surfaces can show the linked account state without exposing raw IDs publicly.
If the login expires, the user restarts the flow instead of posting private codes in chat.
| /commands | Show user-safe commands and hide admin/moderator-only commands from normal users. |
|---|---|
| /latest | Return current app version, minimum supported build, review status, and known release notes. |
| /status | Summarize website, backend, bot, maintenance, AI, and store health with links to the status page. |
| /support and /bug | Collect useful issue context and point private details toward protected support. |
| /modules and /firmware | Route module and Samsung firmware questions to reviewed docs and app surfaces. |
| /release_notes and /known_issues | Show dated updates that can also feed website, app, and community announcements. |
| /store_new | Highlight fresh approved packs and creator drops without exposing review internals. |
Public boundaries
What the bot should never ask for in group chat
The bot should collect enough context to help, but not push sensitive support or admin work into the public group.
Do not ask for passwords, API keys, recovery links, purchase tokens, or private account IDs in public.
Move refunds, account deletion, billing, access grants, and disputes to protected support.
Keep moderation reasons concise in public and keep detailed logs in Mission Control.
Treat root/system actions as risky and point users to backup-first docs.
Topic routing
Clear places for real conversations
Public pages explain where users should go. Private moderation controls stay behind Mission Control.
Workflow and troubleshooting answers guided by reviewed knowledge.
Account, export, app, and package help without sharing private data publicly.
Pack discovery, submission updates, and store questions.
Creator previews, featured packs, badges, and community highlights.
Bot routes
Where users should go after a bot answer
The best bot reply often points to a richer CRYA surface, so the answer can stay short and the next step can be clear.
Topic map, rules, creator showcase, and privacy-safe public support routes.
OpenDocsCRYA DocsPackage Doctor, QMG export, store submission, billing, support evidence, and root safety guides.
OpenAIAI ObservatoryReviewed knowledge, safety rules, cost controls, review queue, and Telegram AI routing.
OpenStatusStatusMaintenance windows, service health, incident guidance, and heartbeat-style public status.
Open