Posts
All the articles I've posted.
The Sweep Could Not Reach the Project. The Silence Was a Finding.
When monitoring client GCP projects, a broken permission that stops a check is as dangerous as a failing metric. Why our observability platform treats an inability to read data as a critical finding.
The Code Rolled Back. The Schema Could Not.
A rollback restores the code and leaves the database where the migration put it. Why "no rollbacks" depends on schema changes the previous release can still run against.
Scope Every Read: Confidential Docs in a Shared Bucket
Per-matter prefixes, short-lived signed URLs, database-checked reads, and redacted logs for confidential documents in multi-tenant GCP apps.
The Reply Arrived Twice. The Record Updated Once.
Inbound replies and webhooks must link to the right record exactly once, and generated drafts must wait for a human. Two mechanisms from production systems: key on the sender id, hold behind a gate.
The Code Changed. The Description Had to Survive It.
Code changes flow back into the knowledge graph the generator reads: changed files only, merge not replace, both artifacts patched. Freshness as write back, not retrieval ranking.
The OAuth Succeeded. The Reports Still Had to Reconcile.
Hardening QuickBooks OAuth server side and structuring Profit and Loss, Balance Sheet and Cash Flow in Postgres so three reports read at different times still agree.
The Test Passed. The Agent Never Called the Tool.
Grading an agent on the artifact it produced tells you nothing about how it got there, which is the one thing a tool-use environment exists to measure.
I Wrote the Tool for a Human. An Agent Called It.
An agent has only your response bytes to reason from, which turns error messages into control flow and makes response size a correctness property.