The instrument panel for a thinking being. This foundation proves the served UI reaches a real, authenticated Marvin over the completed API — the surfaces fill in as Epic 9 lands. Below is a live systems check against this process.

Need a clean slate? Start fresh wipes memory, history, or does a full factory reset — always backed up first.

Marvin saves every fact; anything that looks like a secret is flagged and hidden from the on-disk vault until you approve it. Delete what you don't want kept.

Marvin tidies his own memory in the background — folding near-duplicates together and moving long-untouched facts out of everyday recall. Nothing is deleted, and anything here can be put back.

Everything Marvin has recorded, forgotten or removed about you, and when. Nothing here changes anything — these are read-only views of your own record.

Drag to pan · scroll to zoom · click a node for detail. Gated memories show a redacted placeholder, never their content.

Pin a topic and Marvin researches it in the background (a web search + summary), then files the result in Findings. The label is just for your own organizing — it doesn't change what Marvin does. Research needs web search turned on and your approval to use it: without a standing approval the task waits in Approvals for your OK; if web search is turned off it can't run.

Marvin acts through your enrolled devices. Commands still in flight are shown too — a phone that is off or out of signal has not failed, it simply has not answered yet, and hiding that would look exactly like a command that was never accepted.

Read-only, and metadata only. Marvin lists who wrote, the subject and a snippet — it does not fetch message bodies unless you open one. It cannot send or reply from here: those need your explicit approval each time, and are switched off by default.

Read-only. Creating, moving and responding to events needs your approval each time and is switched off by default.

Enrolling issues one credential, shown once. Revoking stops that credential working immediately — the person stays on the roster, marked revoked, and their own memories are never touched.

This is biometric data, and it ships switched off. Marvin only recognises someone you have explicitly taught, from a photo you choose. Revoking erases that person's face data from disk — not a flag, an erasure — and it cannot be undone.

Devices with an ingest-only credential — they may send Marvin signals and nothing else. Revoking deletes the credential; it is not recoverable, and the device stops being able to send immediately.

Metadata only — never message bodies. Marvin records that a call, message or contact arrived and from which device, not what it said. Erasing reports a count for the same reason: it can delete what it was never able to show you.

Files you've uploaded to Marvin (via the chat paperclip). Click a row to see its full details; Download saves the original file back to your device; Remove deletes it from Marvin's store. Removing a file here doesn't affect any chat turn it was already used in.

Everyone Marvin knows, however it learned about them — your phone, and later other sources. Someone here needs no phone number at all: add a name and they exist. Click a row to see every name, number and address Marvin has for them and which source said so. What you set survives every future phone sync. If Marvin can't tell two records apart it never merges them on its own — it asks, and the question waits on the Approvals page.

Your Life OS, as Marvin tracks it. Create, edit and delete right here — and move items through their statuses with the "move to…" control, which only ever offers the legal next steps.

Adjust Marvin's numeric persona dimensions. An override is recorded, audited, and revocable — there is no free-text here (FR-24); natural-language shaping is a chat command.

Everything Marvin can do — built-in tools, tools it generated itself, and skills it has learned. You can ask Marvin to build a new tool or learn a skill below; each one waits in Approvals for your sign-off before it goes live.