Evidence without automatic green lights
Why repository health, configuration baselines, and review receipts distinguish a verified observation from approval or certainty.
Ideas and decisions from the things I’m building.
Why repository health, configuration baselines, and review receipts distinguish a verified observation from approval or certainty.
How gates, locks, Git preflights, and file guards reduce ambiguity around checks, worktrees, and agent-written files.
Four small tools for durable messages, lifecycle history, generation-safe progress, and decisions whose original wording remains intact.
The shared Postgres limit, the rollout that reduced idle connections, and why a green dashboard is only one kind of evidence.
The infrastructure integration and application workflows behind our self-hosted Temporal deployment.
A cutover trace from Helmsman's move to Kubernetes CronJobs: one declared owner per job, a revision-pinned switch, a rollback that could not be a revert, and alerts that had to move too.
One synthetic headline traced through a partial observation, an upgrade, duplicate deliveries, an edit and a retraction, using the ingestion writer's real storage contract.