Mission works by turning messy context into operating memory. This page explains the intended data classes, retention posture, and handling rules.
Mission may handle profile settings, goals, tasks, relationships, prospects, drafts, approval packets, receipts, outcomes, connector status, social handles, website signals, command-box requests, storage hygiene reports, and agent guide state.
Email, calendar, chat, social, website, and document content can be incomplete, adversarial, stale, or misleading. Mission should use source material as evidence, not as automatic truth.
Mission distinguishes prepared work from executed work. Sent messages, published posts, closed tasks, approvals, rejections, edits, and outcomes should be recorded as receipts where possible.
In local workspaces, durable data stays in workspace files under operator control. Mission storage hygiene only deletes generated temp workspaces and capped synthetic lab artifacts; it does not delete trackers, receipts, packets, drafts, credentials, or pilot-authored data.
Do not share workspace data, examples, screenshots, or case studies without permission from the user or organization whose context appears in the material.