Notes and tasks

Two inboxes for the two things that pile up fastest: what you captured and what you owe.

Notes and tasks are the two streams that overflow first in a busy practice. TorchRunner treats each as an inbox you process, not a graveyard you accumulate.

Notes

Everything you capture lands in one place: the thing the client said on the call, the idea between meetings, the detail you do not want to lose. Rather than forcing you to file each note the moment you write it, TorchRunner lets Archie triage them in a batch: link them to the right engagement and Area, surface the ones that imply a task, and clear the rest.

Tasks

The same shape for what you owe. Open work lands in a task inbox, gets connected to the engagement it serves, and is processed rather than left to rot in a list you stop reading. Tasks can be created by you, surfaced from a note, or raised by a Runner that noticed something needs doing.

The maturity ladder

How much TorchRunner does on its own here is something you control, and it climbs in stages.

1. User-initiated by default

   Out of the box, nothing happens to a note or task unless you direct it. This is the floor and it stays the floor until you choose otherwise.

2. Opt-in pre-built paths

   You can switch on specific, well-understood routines, like routing a class of note the same way every time.

3. A narrow unattended band

   Only for the handful of actions that have proven safe and boring on your practice does TorchRunner act without asking. You set this edge, deliberately and narrowly.

Automation is earned. TorchRunner does not assume permission to act. It starts under your full control and graduates only where you say so.