Playbooks

Routes through more than one tool.

Each tool does one job. Some things I want need two or three, one after another. A playbook is the route I take: which tool, what I check, and which file I save and open in the next. A playbook is only written down after I have taken the route myself.

Pouring

Passing a result from one tool to the next is a pour, and I pour by hand: I save the result I have checked as a file, then open that file in the next tool. Nothing moves between the tools on its own, so the next tool starts from exactly what I checked. If I change the result later, the next tool sees the change only when I save the file and open it again.

I did once build a pour that sent each statement straight from Tables into Regulars. It worked, but a poured statement was gone when the app closed, and a year needs twelve statements kept somewhere. Saved files already did that, so I took it out the same day.

So far

A year of statements

Tables, then Regulars

Twelve monthly statement PDFs become one list of what I pay for again and again, sorted by what each costs in a year. No models: ordinary code all the way.

A pile of photos

Local, Sort, then Local and Geo

A folder of unsorted photos moved into the folders I already have, by a script I read and run, with an undo. Apple’s Vision and, where Local has indexed the folders, EmbeddingGemma.