Title and project
Area and a short imperative title. The project list is your own.
Salana
Product · Tasks
Focus on the work that moves you forward. Every substantial piece of work an agent does in your Salana Memory is logged as a task card as it happens and closed with the outcome. You never feed the board; it writes itself.
Most task tools ask you to feed them. You write the task, move it, close it, and the actual work happens somewhere else. The board is out of date the moment you stop maintaining it.
In a Salana Memory the work is the source. An agent starting a substantial piece of work opens a card. When it finishes, it closes the card with what came out: the numbers, the decision, the commit, links to the files it produced. Every chat, terminal and automation follows the same rule.
Drag a card when you want to; you rarely have to. A chat that starts substantial work puts its card in In progress, and closes it to Done with the outcome when it finishes. An automation does the same at 07:00 without anyone watching. What you see on the board is what actually happened in your Salana Memory today, because the agents doing the work are the ones writing it down.
Area and a short imperative title. The project list is your own.
A chat, a terminal session or an automation, with the session it ran in.
One to three lines in past tense: key numbers, decisions, and links to what was made.
One markdown file per card, in one folder, in git. Search it, grep it, take it with you.
The board in the Salana App is a kanban over those files: Inbox, In progress, Done. The morning briefing lists what got done yesterday and what is overdue. Ask “what did we do on the website last week” and the agent reads the cards.
Say “log a task: call the bank about the KYC” and it is on the board. Drag it between columns, rename it, close it with a note. The same file format, the same folder.
Your files, every model, yours forever.