Filing

Every call ends up in its client's folder.

The summary step is the first that knows who a call was with, so filing runs after it. The call's whole file set moves together into one folder per client. Files are moved, never renamed: the ledger keys every item on the file name, so a move is invisible to it and ticked items stay ticked.

Sample folders

The rules the filer follows

All or nothing. If one file of a call would collide with a file already in the destination, the whole call stays where it is. A transcript in one folder with its summary in another is worse than an unsorted call.
Reuse what is there. A folder is matched on the normalized name, so a small spelling difference never opens a second folder for the same client.
Aliases fold. “Valley Comfort” and “Valley Comfort HVAC” are the same roster entry. Matching is exact on the normalized name, never fuzzy: folding a stranger into an existing client is worse than an extra folder.
Unknown goes to _Unsorted. A call with no client is parked, not guessed into someone else's folder.

The roster clients.json

One hand-maintained list of every client and the other names it goes by. Every step reads it; none writes to it.

Client	Also called	Notes file

Processing notes _NOTES.md

Each client folder can hold a notes file with the people and places on that account and a table of what the speech model gets wrong. The summary step reads it, so names come out spelled correctly even when the raw transcript has them wrong.

Correct	The model produces

Email cross-reference email_evidence.json

Optional step. For each client with open items, the mailbox is searched for evidence that an item is already handled, and how long the thread has been quiet. Items are annotated, never ticked: an email showing a proposal went out does not prove a signed agreement came back. A second pass sweeps recent mail for commitments with no call behind them.