<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Michael Cabassol — Writing</title><description>Point of view. Systems are accountability. These are not tutorials.</description><link>https://ucby.io</link><item><title>Omnigent: Who wrote the day&apos;s commits</title><link>https://ucby.io/projects/omnigent/authorship</link><guid isPermaLink="true">https://ucby.io/projects/omnigent/authorship</guid><description>What it means for an agent fleet to build its own platform: 200 card branches merged in a day, a five-PR chain from store to React panel in 3 hours 20 minutes, a card filed only after its dependency merged, and the batch gate that shipped inert for forty minutes. Also who actually wrote the day&apos;s four throughput fixes.</description><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Omnigent: Where code replaces the model</title><link>https://ucby.io/projects/omnigent/deterministic</link><guid isPermaLink="true">https://ucby.io/projects/omnigent/deterministic</guid><description>Where an agent fleet replaces LLM turns with code: a stage executor that moves cards on stored proof, a dispatch seam that launches workers without a coordinator turn, and routing as a table lookup that names its rule. Orchestration went from 54% of tokens to 3% of daily spend. What the code owns, what the model still decides, and how you know the split was safe.</description><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Omnigent: How review decides a pass</title><link>https://ucby.io/projects/omnigent/review</link><guid isPermaLink="true">https://ucby.io/projects/omnigent/review</guid><description>How an agent fleet&apos;s review stage decides what pass means: a deterministic pre-pass that computes contract, blast-radius, and test-adequacy facts before any model reads the diff and grades unknown unless it holds proof; a clean round that no longer routes into fixing (81% first-verdict pass against 13 to 14%); a reviewer on a different vendor; and one real round with four blocking findings.</description><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Omnigent: Three weeks of throughput engineering</title><link>https://ucby.io/projects/omnigent/throughput</link><guid isPermaLink="true">https://ucby.io/projects/omnigent/throughput</guid><description>Three weeks of making an agent fleet faster, in the order it happened: the token read that found the orchestrator at 54% of spend, the deterministic transitions that took it to 3%, the context ladder that broke builders and was reversed, the timeout storm, and the day the board merged 246 cards. Each with its measurement and its caveat.</description><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate></item><item><title>I take the project the process can’t start</title><link>https://ucby.io/writing/i-take-the-project-the-process-cant-start</link><guid isPermaLink="true">https://ucby.io/writing/i-take-the-project-the-process-cant-start</guid><description>A project that is taking too long is rarely short of engineers. It is short of a start. An architecture decision review board sat in design for two years; two weeks in Cursor produced a working prototype, and the team had it in prod six weeks later. Leadership supplies the cover.</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate></item><item><title>I don’t know if the air cover was real</title><link>https://ucby.io/writing/i-dont-know-if-the-air-cover-was-real</link><guid isPermaLink="true">https://ucby.io/writing/i-dont-know-if-the-air-cover-was-real</guid><description>My director answered every wild idea with ‘run with it, go for it.’ I never found out whether the cover behind him was real, and the team built like it was. Cover is local — a direct leader’s willingness, backed one level up, not an executive’s presence.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>I gate on what a test suite can check</title><link>https://ucby.io/writing/i-gate-on-what-a-test-suite-can-check</link><guid isPermaLink="true">https://ucby.io/writing/i-gate-on-what-a-test-suite-can-check</guid><description>The line for an autonomous system is verifiability, not consequence. A bug fix has known inputs and a full test suite; an Architecture Decision Review Board Submit has subjective business judgment. At 10,000 lines a card, manual review is theater.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>My eval is the health check</title><link>https://ucby.io/writing/my-eval-is-the-health-check</link><guid isPermaLink="true">https://ucby.io/writing/my-eval-is-the-health-check</guid><description>The eval that gates my deploys is the health check: real dependencies, a rolling error tally, per-instance stats. The orthodoxy says keep checks shallow. When an invalidation flood from another team blew up a shared Mongo, the deep check was the alarm, not the breaker.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Cache any function in one line, and measure whether it helped</title><link>https://ucby.io/notes/cache-any-function-in-one-line</link><guid isPermaLink="true">https://ucby.io/notes/cache-any-function-in-one-line</guid><description>Any function cached by a hash of its inputs — one-minute TTL, no invalidation, at hundreds of millions of calls a day. The business owned the staleness dial.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Canary deploys on a Lambda alias: the rollback I allow</title><link>https://ucby.io/notes/canary-deploys-on-a-lambda-alias</link><guid isPermaLink="true">https://ucby.io/notes/canary-deploys-on-a-lambda-alias</guid><description>Publish the version, shift traffic incrementally, shift it back when health goes away. Reverting the repo is the one I refuse — expand-only schema is what makes it safe.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Decomposing a Figma design for an AI coding assistant</title><link>https://ucby.io/notes/decomposing-a-figma-design-for-an-ai-coding-assistant</link><guid isPermaLink="true">https://ucby.io/notes/decomposing-a-figma-design-for-an-ai-coding-assistant</guid><description>Two years of Figma design, no engineer, two weeks. Whole pages didn&apos;t work, so the breakdown became mine: a screenshot per component, then one workflow at a time.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>The in-app agent: page state in, an action list out</title><link>https://ucby.io/notes/in-app-agent-page-state-in-actions-out</link><guid isPermaLink="true">https://ucby.io/notes/in-app-agent-page-state-in-actions-out</guid><description>Page state in, a JSON action list out, executed by the client, then re-read. Two allow-lists hold it: the schema&apos;s verbs and the serializer&apos;s ids. Submit stays human.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Pre-rendering for crawlers: the governor and the URL set</title><link>https://ucby.io/notes/pre-rendering-for-crawlers</link><guid isPermaLink="true">https://ucby.io/notes/pre-rendering-for-crawlers</guid><description>Chromium in Lambda renders pages to S3. CloudFront serves them to bots. One setting bounds the fan-out, and a Redis set stops the crawl re-rendering what it already did.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Migrations that run at startup, under a lock</title><link>https://ucby.io/notes/startup-migrations-with-lock</link><guid isPermaLink="true">https://ucby.io/notes/startup-migrations-with-lock</guid><description>Migrations baked into the service, not the pipeline. It reads the schema version on boot and migrates under a lock. Forward-only, so a traffic-layer rollback is safe.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Trace every function with one attribute</title><link>https://ucby.io/notes/trace-every-function-with-one-attribute</link><guid isPermaLink="true">https://ucby.io/notes/trace-every-function-with-one-attribute</guid><description>A .NET aspect timed every function it wrapped, flushing once per request to Graphite, Splunk, and Redis. get-user-info spiked to ~150 ms. Dashboard found it in an hour.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Casting models across an agent pipeline</title><link>https://ucby.io/notes/casting-models-across-an-agent-pipeline</link><guid isPermaLink="true">https://ucby.io/notes/casting-models-across-an-agent-pipeline</guid><description>Model and effort are picked by stage, not by card. Fable 5 specs low, Sonnet 5 builds, GPT-5.6 Sol reviews xhigh — a different vendor, by design.</description><pubDate>Sat, 29 Aug 2026 00:00:00 GMT</pubDate></item><item><title>CDK stacks across regions: the shape that held</title><link>https://ucby.io/notes/cdk-stacks-across-regions</link><guid isPermaLink="true">https://ucby.io/notes/cdk-stacks-across-regions</guid><description>CloudFront&apos;s certificate must sit in us-east-1; the platform ran in us-west-2. A stack export can&apos;t cross regions. SSM Parameter Store carried the ARN instead.</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate></item><item><title>One state file or many: how I split Terraform state</title><link>https://ucby.io/notes/one-state-file-or-many</link><guid isPermaLink="true">https://ucby.io/notes/one-state-file-or-many</guid><description>Environment directories are standard. What matters more is splitting by change velocity: Terraform owns what&apos;s stable, the CLI owns what gets tuned constantly.</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Terraform or CDK: how I decide</title><link>https://ucby.io/notes/terraform-or-cdk-how-i-decide</link><guid isPermaLink="true">https://ucby.io/notes/terraform-or-cdk-how-i-decide</guid><description>Terraform or CDK: a mandate decided it, not features. Stripped the enterprise&apos;s CDK harness on day one. CDK&apos;s ergonomics come with CloudFormation&apos;s cost.</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Terraform state corruption: what I did before the retry</title><link>https://ucby.io/notes/terraform-state-corruption-before-the-retry</link><guid isPermaLink="true">https://ucby.io/notes/terraform-state-corruption-before-the-retry</guid><description>State corruption from a dead session token, a flaky VPN, or a security-group rename. The ladder I climbed before nuke-and-reimport — dev only, never prod.</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Autonomy expands with instrumentation, not capability</title><link>https://ucby.io/writing/autonomy-expands-with-instrumentation</link><guid isPermaLink="true">https://ucby.io/writing/autonomy-expands-with-instrumentation</guid><description>The most autonomous system I run builds my software — 1,487 cards closed in 5 weeks, measured off the board itself. The autonomy came from telemetry, a lineage graph, and gates, not smarter models. Same-model review passes its own blind spots; &gt;50% of tokens went to review.</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate></item><item><title>A hundred people asking, is it your problem?</title><link>https://ucby.io/writing/a-hundred-people-asking-is-it-your-problem</link><guid isPermaLink="true">https://ucby.io/writing/a-hundred-people-asking-is-it-your-problem</guid><description>A hundred-person bridge call is not a root-cause process. One pane of glass, drill until you hit the cause — and the goal is an AI agent that gets there first.</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate></item><item><title>I don’t hire on certifications</title><link>https://ucby.io/writing/i-dont-hire-on-certifications</link><guid isPermaLink="true">https://ucby.io/writing/i-dont-hire-on-certifications</guid><description>A badge is a study path. The résumé is the systems catalog: what was on fire, what we decided, what the numbers did.</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate></item><item><title>The load balancer runs my test suite</title><link>https://ucby.io/writing/the-load-balancer-runs-my-test-suite</link><guid isPermaLink="true">https://ucby.io/writing/the-load-balancer-runs-my-test-suite</guid><description>Distribute a system across AWS and the risk moves into the seams. Coverage can&apos;t see that. Bake the integration test into a health endpoint, thread a request ID through everything, put every log in one place.</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate></item></channel></rss>