Learn MYOS
The task system
Everything that lands in your vault comes from a task. That single rule is what turns a folder of notes into a system you can ask questions of.
Your open tasks are the queue you and your assistant work through. The archive is everything that has already been through it.
Why the rule is strict
A vault without it becomes a junk drawer. Files appear, nobody knows why they exist, and six months later you cannot tell what was decided from what was drafted and abandoned.
With it, the task list is a complete record of events. Your assistant can read the archive and answer "what happened with this client", "why did we choose that", and "what did I actually ship last month", because every one of those answers has a file that names itself.
What a task looks like
Open one and you will see frontmatter at the top: an id, a status, a priority, a due date, the date it was created, and the entity or area it belongs to. Below that is a title, a last-updated line, and whatever working detail the task accumulates.
Your assistant writes them in this shape automatically. You never format one by hand.
Active and Archive
_Tasks/Active/ is your live list. _Tasks/Archive/ is everything finished.
Completed tasks move, they are never deleted. The archive is the searchable history of your own work, and it gets more valuable every month rather than less.
The archive habit
Finishing a task is two steps, not one. Your assistant marks it done, stamps the date, and moves the file. Then it runs the archivist, which sends three specialists over the finished work.
One folds what happened into the entity and area files, so the area's landing page tells the story without you writing it. One checks whether anything about how you work or what you are focused on should update your profile. One tidies the links between the task and everything it touched.
This is where knowledge compounds. The task is a short-lived thing. What it taught the system outlives it.
Big work
Work larger than one task gets a major task as the hub, with subtasks chained to it. The hub holds purpose and milestones. The subtasks hold the working detail and the decisions.
Decisions live on the subtask that made them, never on the hub. When you come back in a year asking why you chose the thing you chose, the reasoning is sitting on the file where the choosing happened.
What this costs you
Almost nothing, because you do not run it. You say what you want done, your assistant creates the task, and it closes the loop when the work is finished.
Next: Areas. Or see what ships in the kit.