Every ship, essay, and project milestone, merged into one chronology — the same story that's otherwise split across /changelog, /writing, and each project page.
wrote
This week I pointed the whole agent fleet at Claude Fable 5 and turned the effort dial to its highest setting. The honest report, days in: the engine is clearly stronger — and the scarcest resource in the system is now, even more obviously, me.
wrote
I let a fleet of coding agents run while I sleep. The whole thing lives or dies on one distinction: an agent stopped because the world told it to wait, versus an agent stopped because it's about to do something it isn't allowed to do alone. Only one of those is safe to nudge.
shipped
A small set of around-the-home planners now run report-only: each proposes an action and logs it, but never actuates anything for real until a human signs that specific automation off. Safety-first, deny-by-default.
shipped
A deliberate adopt-over-build phase: sharpen the existing toolset and reclaim time from what already runs, with new features a distant third. 'Build nothing' is a valid, healthy week.
shipped
The central status service grew embeddable, glanceable surfaces — a reliability sparkline and a browsable status page — and the operator dashboard added reliability and activity charts plus a ranked triage queue.
wrote
A small always-on box runs a fleet of coding agents across my repositories while I'm away. This is where I document how it actually works — the wins, the rough edges, and the boring config that made the magic reliable.
project milestone — AI-Ops — the Operator Loop
The first always-on guardrail landed: an automation that defends protected hours, so the loop can never schedule over them.
shipped
parallelogramist.com — this build-in-public site — shipped: write-ups of every project, the loop methodology, and a /now snapshot of what's current.
project milestone — AI-Ops — the Operator Loop
A scored leverage ledger turned the next-build choice into a ranked, upkeep-aware decision instead of a guess — toil that costs more than it saves self-prunes.
project milestone — AI-Ops — the Operator Loop
Defend, brief, and triage run report-only by default — they surface a recommendation; a human adopts each one before it ever acts.
Ships are month-granular by design; writing carries its real publish date. See /changelog for ships alone, or /stats for the operation's scale.