Memory with provenance
Useful context should be visible, editable, and source-aware. No mysterious profile magic.
A private assistant built to give people their time back, not another dashboard to babysit. Zain brings memory, approvals, integrations, Arabic-first polish, and honest failure handling into one calm operating layer.
Every promised workflow must be proved before it is claimed live. If a provider is still on its proof path, Zain says so instead of pretending.
The launch promise is not a thin chatbot. Zain has to understand context, ask before acting, recover honestly when something breaks, and feel premium in English and Arabic.
Useful context should be visible, editable, and source-aware. No mysterious profile magic.
External actions go through a clear approval spine before they touch calendars, inboxes, files, billing, or messages.
The launch suite stays visible, but each provider has to earn its live claim with readback, failure, reload, and safety proof.
RTL, tone, spacing, and mobile polish are part of the standard, not an afterthought.
Pricing copy stays tied to the proof map. Team, family, expense, child, enterprise, billing, and integration promises remain scoped until their proof lanes pass.
For the first members who help shape the product and keep the locked founding price.
The individual plan once the launch suite is proved and opened wider.
Team memory, multi-user approvals, and admin features stay proof-gated until their lanes pass.
Custom integrations, dedicated infrastructure, and SLA terms require scoped agreement and proof.