🧠How To Use — Board & Ledgers
Two moving parts, clear jobs:
1. Task Board — the what and when. One file, one table per client. Each row is a task with a due date, time, priority and status. This is your single source of truth for what’s on your plate. Keep it light — short task names, no long context.
2. The Ledgers — the why and the detail. One ledger per client/area. This is where you give me full context: decisions, tech stack, stakeholders, data, and an audit trail. When you ask me to do something for a client (e.g. “audit Cengage’s reporting”), I read that client’s ledger first instead of you re-explaining everything in chat.
The loop
- A task appears → add a row to the Task Board.
- Need to capture context, a decision, numbers, or an audit note → write it in that client’s Ledger.
- Ask me to work → I read the ledger, do the work, and (if you want) log what I did in the Audit Trail section.
- Task done → set Status to ✅ (or move it to the Done archive at the bottom of the board).
Clients & buckets
| Bucket | Clients | Ledger |
|---|---|---|
| 2X — Full Job | Cengage | Cengage - Ledger |
| 2X — Full Job | Octus | Octus - Ledger |
| 2X — Full Job | Fourth (new) | Fourth - Ledger |
| Freelance — Digital Marketing | Tiles Concept (new) | Tiles Concept - Ledger |
| Freelance — AI | EFFEN (AI Contract) (new) | EFFEN - Ledger |
| Personal / Side Business | INDEXA (own) | INDEXA - Ledger |
| Personal / Study | ACCA (exam prep) | ACCA - Ledger |
Tips
- Status/priority use emoji so they stand out in reading view: 🔴🟡🟢 and ⬜🔵⏸️✅.
- Ledgers have an Audit Trail table — that’s the spot for “what changed, when, by whom”.
- Want a Kanban view later? Obsidian’s Kanban plugin reads these tables; just ask and I’ll restructure.