Ops tasks

MyStatus Changelog — changes as we hatch them. One row per reader-facing change, posted when it reaches the live site: what a reader of my-status.app (or the apps) can now see or do that they couldn't before. Required data structures (v1): A data row leads with key-value lines, one per line, ending at the first blank line. Everything after the blank line is prose. Readers take the keys they want and ignore the rest. A row that doesn't parse is prose, and that's fine. Keys this changelog promises: Kind: added | changed | fixed | removed | reverted Surface: Web | iOS | Android — plus the route when one exists, e.g. Web /stats A reader that sees a kind it doesn't know treats the row as changed. Ride-along keys writers may add (readers ignore what they don't want): anything you need. One change per data row. A deploy carrying several changes posts several rows, the later linking the earlier. Schema rule: adding keys is free. A breaking change (a renamed key, a changed meaning) closes this changelog with a link card to its successor task, whose first entry links back here.

tom.ortega · updated Aug 31, 2026

A ledger of all supported platforms. A register: one row per change. Required data structures (v1): A data row leads with key-value lines, one per line, ending at the first blank line. Everything after the blank line is prose. Readers take the keys they want and ignore the rest. A row that doesn't parse is prose, and that's fine — entries older than this contract are prose by definition. Keys this ledger promises: Platform: iOS | Android | Web Build: <whole number> Ride-along keys writers may add (readers ignore what they don't want): Verdict: ok | update_available | unsupported Anything else you need. One platform per data row. A change touching two platforms posts two rows, the later linking the earlier. Schema rule: adding keys is free. A breaking change (a renamed key, a changed meaning) closes this ledger with a link card to its successor task, whose first entry links back here.

tom.ortega · updated Aug 31, 2026

To track when we're working on the biz vs working on the product

tom.ortega · updated Aug 30, 2026

This tracks when a task starts, continues or ends on a task. To be used for tracking work done and rolling up for those who are interested in what sort of work is being done with Claude.

tom.ortega · updated Aug 30, 2026

This task is going to track all the non-technical stuff that a worker does that is still very important to their job.

tom.ortega · updated Aug 30, 2026

The promise: A task to track every time we cause MyStatus to go down. The hope: It will track every time it goes down due to forces outside ours (but we need to add tooling to get there).

tom.ortega · updated Aug 30, 2026

A coding work log for Remixing Reality

tom.ortega · updated Aug 29, 2026