The framework: write it once, let the rest follow.

The flow

Everything goes into one place and the rest is derived: you write, record, send a message or take a photo, and out comes a planned week and knowledge that builds up on its own.

Capture

The daily note, a recorded meeting, a WhatsApp or a photo. Nothing asks you for a format: capturing and clarifying are two acts, and the mind is for having ideas, not holding them (GTD, Allen, 2001). Clarifying happens separately: the AI marks provisional tasks, you discard the ones that do not belong and closing the day — by hand, or on its own once midnight passes — turns the text into tasks and cards. See The daily note.

Offloading frees resources for the main task (Risko and Gilbert, 2016): what you write or say once leaves your head, as a task with an owner, a date and the link to where it came from. Vague tasks come out flagged as ambiguous, to be rewritten with a concrete outcome: a vague goal performs like "do your best" (Locke and Latham, 1990).

Plan

Tasks is what you committed to; Calendar, when. The Eisenhower quadrants come out on their own from the date, who executes and the quota: nothing is sorted by hand.

Two numbers shape the week. How much fits: one Crítico, three Impacto and five Operativas. It is a ceiling, not a target: less work in progress shortens cycle time (Little's Law, 1961).

Where it lands: you do not perform evenly all day (Horne and Östberg, 1976). You say once when you perform best and which days you work, and the planner builds your energy map. The peak is reserved before the week starts, because the urgent beats the important even when the important pays off more (Zhu, Yang and Hsee, 2018): only Crítico and Impacto go there, and operational work goes outside the peak. And it does not sort a list: every task lands in a block with a day and a time, because deciding when and where you will do something greatly improves follow-through (Gollwitzer and Sheeran, 2006). See Calendar and planning.

Know

Memory, Atlas and Digest build themselves from what you wrote, with nothing entered separately. Instead of searching the raw material every time, the Atlas writes and maintains an intermediate layer — Andrej Karpathy's LLM Wiki pattern —: one article per person, organization and project, with citations to the note or meeting it came from, rewritten on its own when new material comes in. The WhatsApp and Telegram assistant and the AI clients connected over MCP start from that layer. See Atlas.

Each person's entry says which projects they are in, what they decided and what was left in their hands: a group performs better when it knows who knows what (Wegner, 1987). And the Digest tells you per project what moved, what was decided and what is stuck, because seeing progress sustains motivation more than rewards do (Amabile and Kramer, 2011). Unlike PARA, the unit is the day, not the well-filed document.

Why what you already use is not enough

Notes and task managers cover everything, but ask you to do the organizing. Recorders and assistants understand on their own, but cover one piece. Mem, Limitless or Motion each solve one stretch; none covers the whole flow.

What order to start in

• First — just the daily note or the recaps, discarding what detection gets wrong.
• Then — the planner and tasks: on Monday, press Planner.
• Meanwhile — the Atlas builds itself, and you see it through the Digest: that is where the value becomes clear and trust is earned.
• Last — the other channels: WhatsApp, Telegram, the clipper, MCP.

It goes in stages because a habit takes 66 days on average to become automatic (Lally, 2010). After a month, the question is not how much you closed: it is whether the week feels like yours to run.

The Planner and AI detection are Hobby and up; the rest is on Pricing.