What exists?
Required answer shape
List known records by location/module with source and owner.
When missing: Say what is not loaded yet and ask the next intake question.
MIA Intake
Build TD10’s brain by conversation.
MIA starts from zero: asks structured questions, saves factual memory, creates owner-routed action memory, and only claims what has a source or a clear user-provided answer. Telegram can be the first intake channel; WhatsApp can follow later.
MIA
Let’s create TD10 from scratch. I won’t use preview data. First, what is the official restaurant/company name you want this brain to use?
Answer MIA’s setup question...
Let’s create TD10 as a clean tenant.What is the first restaurant location?Who owns compliance and documents?Which source should we register first?Upload or describe the first permit, lease, insurance policy, or SOP.
Acceptance contract
If MIA cannot prove it, she asks or creates a task.
What changed?
Required answer shape
Compare fresh source checks, user updates, and task/action events.
When missing: If no source checks exist yet, recommend registering sources first.
What is stale, missing, or overdue?
Required answer shape
Return stale sources, missing docs, expired/soon records, overdue tasks, affected locations.
When missing: Create setup tasks for the missing/future records instead of inventing status.
Who owns it and what should happen next?
Required answer shape
Return owner, next action, approval requirement, due date, and related records.
When missing: Ask for the owner or assign to default tenant owner until clarified.
Telegram intake is the next wiring step.
The UI and memory contract are ready for blank intake. Next, connect Telegram messages to the same intake state so MIA can ask and save these setup answers outside the web app.