Three tools, each with one job, and a folder of short written recipes that any AI assistant can follow. Here is how they fit together, and the recipes we use most.
The one question
Everything gets sorted by what kind of thing it is
Is it something to do, something to know, or a record?
Something to do
Google Tasks
You'd tick it off. "Chase the plumber on Thursday."
Something to know
The vault
You'd open and read it. "What the plumber quoted, and why we chose him."
A record
The admin app
A row with numbers. "Plumber invoice, £240, 19 Nigel Road."
The three layers
Where things live
An item lives in exactly one place. A task stays short and links to the vault page that holds the background.
Action layer
Google Tasks
What needs doing. Most lists are ordered by priority, with no dates, so deadlines stay real.
@ lists are per person, + lists are short projects that get deleted when done.
Knowledge layer
The vault
Plain Markdown pages in a git repo, one folder per area of life. The canonical record of reasoning, history and reference.
Plans, research, itineraries
What was decided, and why
The workflow recipes themselves
finance/turkey/wine/garden/holidays/workflows/
Records layer
The admin app
A web app with a database behind it. Claude reads and writes it directly through a connector.
Invoices, expenses, time log
Donations, property ledger, tax years
Turkey finance, wine sales, meals
/invoices/expenses/property/charities
Two things sit to one side. The Family shared Drive holds the documents themselves (PDFs, statements, receipts), and the vault links to them. Admin's old to-do screen is a frozen archive: nothing new ever goes there.
The recipes
A workflow is one short file, in plain English
Each process is written so a person can read it in two minutes and any AI assistant can follow it. Angela's assistant reads the same files as mine, so the two can't drift apart.
workflows/charity-donations.md
---
title: Charity donations
for: [angela, tufan]
needs: Gmail, Drive, admin app
owner: tufan
last_reviewed: 2026-11-06
review_every: 3 months
---## When to use itA donation receipt arrives...## Steps1. Record it in admin...## Rules, and whyGift Aid only if... because...## Watch out forDuplicate receipts from...
HeaderWho it's for, what tools it needs, who owns it, and when it was last checked.
When to use itThe situation that sets it off.
StepsWhat to do, in order.
Rules, and whyThings an assistant wouldn't guess. Each rule gives its reason, so anyone can tell when it's stopped being true.
Watch out forMistakes that have actually happened.
A monthly check lists any file past its review date and asks the owner one yes/no question: "still right?"
How Claude finds them
A front door, an index, then one file
Claude never loads everything. It follows three hops and reads only the recipe the task needs.
AGENTS.mdThe front door. Who I am, how the vault is laid out, where to look.
→
claude/workflows.mdThe index: "when this happens, read that file".
→
workflows/wine.mdThe one recipe for the task in hand.
Claude on the laptop reads the vault straight off disk. Claude in the browser or on the phone reaches the same files through a vault connector.
The daily rhythm
Tidy up at night, think in the morning
Loose ends and planning happen in the evening, so the morning goes straight onto the biggest piece of work.
8pm
Evening run
An automatic routine builds an attention list and proposes tomorrow's one big thing.
Late evening
30-minute review
Work the list, file anything new into its proper list, confirm tomorrow's focus.
6:30am
Top-up
Adds anything newly due and overnight calendar changes. Never re-plans.
Morning
Deep work
No tidying jobs surface unless something is genuinely urgent.
The key workflows
The recipes we use most
There are about 27 in all. These are the ones that come up week to week.
Everyday
Google TasksWhich list a to-do goes in, when it gets a date, how to merge duplicates.
Getting documents inDrop it in Downloads or forward the email. Claude names it, files it on the Family Drive, and parks the original for review rather than deleting it.
Writing an emailsharedClaude drafts it or puts it on the clipboard. It never sends: I always send it myself.
Money
Client invoicingTime log to invoice to timesheet, with an insurance turnover check on every invoice.
Angela's invoices, expenses and quarterly tax sendsharedHer assistant follows the same files.
19 Nigel Road ledgersharedLetting agent statements, repairs and rent for the rental flat.
Bank importsUK and Turkey statements loaded into admin each month.
Paperwork
Charity donationssharedReceipt recorded in admin and filed on Drive.
Health documentssharedLetters and results filed per person and condition.
Receipts and membershipsWarranties and subscription paperwork, filed so they can be found later.
Life
WineSales, what to drink next, tastings and merchant statements.
TripsA vault page per holiday, plus a map built from a Google Sheet.
Reading listThings to read, watch or listen to, kept in admin.
WorkoutsApple Watch files land on Drive automatically, ready to analyse.
shared means Angela's assistant uses the same file.
Ground rules
Three things that hold across every workflow
Just do the obvious next step
Once a workflow is established, the assistant gets on with it and only asks at real choices: whose data, which charity, anything destructive.
Check status, not just dates
A finished task keeps its old due date forever. Before calling something overdue or missing, check whether it was actually done.
Nothing gets thrown away
Processed files are parked for review, finished checklists are archived with a banner, and outcomes are written up in the vault.