How the plain-text files are structured. Timestamp and metadata conventions.
Everything lives in a data/ folder. Files are UTF-8 plain text. You can edit them in any editor; the app and agent read the same files.
One task per block. Task line at column 0: - [ ] Title (pending) or - [x] Title (completed). Metadata on the next lines with exactly 2 spaces indent: key: value. Supported keys: due (YYYY-MM-DD), priority (1–3, 1 = highest), created, completed, tags, url. Lines starting with ; are comments.
; === Personal === - [ ] Call mom due: 2026-02-28 priority: 1 created: 2026-02-27 - [ ] Review PROJECT-PLAN priority: 2 created: 2026-02-27 - [x] Set up dev environment created: 2026-02-26 completed: 2026-02-27
Date line at column 0: YYYY-MM-DD DayAbbrev (e.g. 2026-03-02 Mon). Optional week number w10. Events on the next lines with 2 spaces indent. Timed: HH:MM-HH:MM Title (24-hour). All-day: any line that doesn't start with a time range. Optional id and url with 4 spaces under an event.
2026-03-02 Mon w10
11:00-12:00 meet with joe
id: 6
url: meet.google.com/id/122334
Holiday
id: 7
One entry per line. Format: YYYY-MM-DD HH:MM then exactly two spaces then the content. Timestamp is 24-hour. Parser splits on the first occurrence of two consecutive spaces.
2026-02-28 09:15 Started the day with a short run. 2026-02-28 14:30 Spent time with friends and did some yardwork. 2026-02-28 18:00 Wrapped up work; dinner with family.
Simple bullet list for quick capture. One item per line: - Item to process later. Process by moving items to tasks or calendar or removing them.
- Add a workout planner to the system - Order new A/C filters - Schedule locksmith for keys
Optional: health.md for weight/BP/waist readings; notes/ folder for markdown lists and project notes. For setup steps, see Get Started.