Verification Theater
2026.176The deploy broke. The checks were green. The mechanism measures what it can see - and what it can't see is everything that breaks.
Architecture
tag:
architecture
all tags →2026
Certainty is a boundary too
2026.17416 rounds of adversarial prompts, verified against primary sources. The architecture that makes it impenetrable at the boundary makes it uncalibrated at the center.
The silent assumption in the default
2026.146The config said workers: 4. The machines had 32 cores. The number had been there since 2017. Nobody chose it. Nobody knew why.
The review that happened too late
2026.140The PR has 47 comments. None of them are about the approach.
The mask in the README
2026.139An attention mask drawn in ASCII, and the architectural trade it names.
Earth OS
2026.097If Earth were an operating system, physics would be the kernel.
The config file
2026.096Connection pool sizes, retry counts, timeouts, commented-out endpoints -- and the archaeology of values that survived production.
The dismissal
2026.086Three checks and the developer assumes the fourth is covered. That gap is where the damage hides.
Trust boundaries
2026.079Your code already leaves the machine. The agent just gave it another surface.
Vortex architecture
2026.070What Tesla's 3-6-9 has to say about scaling systems -- and the invariants that hold while the rest moves.
Repeat yourself
2026.049Retries fix distributed systems. Repeating yourself fixes attention asymmetry.
The happy path
2026.016The abstractions rotate every few years. The failure modes don't.
2024
Primary PII
2024.310A regulation arrives. The work looks like encryption at first. It is not.
Scout, plan, wait
2024.233The legacy codebase runs the business. The migration is on every roadmap. Not this one.
2023
Earned, not handed down
2023.261The new user service got Go because it fit. A thing built compatible with the old never needs a migration mandate.
The first five minutes
2023.030The panel is not comparing the diagram to a reference solution. There isn't one.
2022
Building from zero, twice
2022.227What it takes to build a remote engineering center -- and what stays the same when you do it again at a tenth of the scale.
2019
The board stayed green
2019.295The board put us ahead of every customer ticket - until it stayed green while the data underneath it went wrong.
The loyalty engine
2019.201Points are integers. The hard part is time, and users who think faster than your rules.
Prescaling for a known spike
2019.074Autoscale never helped in the time of crisis. What helped was prescaling -- capacity ready before the traffic arrives.