AI Observatory
Livingstone Assistant
The assistant should explain package failures, export choices, creator metadata, and support evidence without pretending to replace human review.
Public surface
Livingstone Assistant
Livingstone Assistant is a guided support surface. It should answer from reviewed CRYA knowledge, ask for the right evidence, and route private issues to support.
Explain desc.txt, folders, frames, export modes, and common Package Doctor findings.
Improve titles, descriptions, previews, compatibility notes, and source declarations.
Send account, billing, deletion, and moderation issues to private support paths.
AI can suggest and summarize; admin decisions stay protected.
| Allowed help | Troubleshooting, documentation routing, metadata drafts, package report summaries, and safe next steps. |
|---|---|
| Not allowed | Private account decisions, billing promises, hidden admin details, or universal device/root guarantees. |
| Evidence | The assistant should ask for package report, device/build, app version, screenshots, and exact steps. |
| Source of truth | Reviewed docs, release notes, support decisions, and admin-approved knowledge. |
Workflow
How this should work
A public page should explain the user path while protected state, permissions, and audit trails stay in CRYA Mission Control.
User describes task or error.
Assistant requests missing context.
Response cites reviewed CRYA behavior and limits.
Sensitive cases move to support/admin.
Related surfaces
Continue the journey
Move between public discovery, creator guidance, store trust, and support evidence without exposing private admin systems.