Trust debt is the name 停止“氛围编程”（Vibe Coding），拥抱新一代软件工程 gives to what accumulates when the speed of agent-generated code outruns the capacity to establish that the code deserves to be trusted. It is introduced as the other half of a trade rather than as a separate failure: the post grants that Vibe Coding genuinely delivers speed, and places the debt directly against it — the speed is there, and trust debt is piling up wildly.
Usage
The term is used to distinguish contexts rather than to condemn a technique. For a one-off script or a prototype, the post treats working by feel as fine and even magical; the debt is what makes the same approach untenable for long-lived software that has to be reliable, which it likens to designing a sea-crossing bridge in a paint program.
The account of how the debt accrues is about where the constraint sits. While humans typed code line by line, the physical limit on output incidentally bought time to absorb context, consider architectural boundaries and run a background quality check. Once generation stops being the bottleneck, human attention and review bandwidth become the binding constraint — the Review Bottleneck this wiki names elsewhere, and the conventional response — open a pull request, read the diff — stops working against hundreds of lines produced in seconds across several microservices, with schema changes and new dependencies among them. What is left, in the post’s characterization, is code that is locally over-optimized and globally incoherent, and the liability is that nobody has established otherwise.
The term is presented as motivating engineering work rather than caution: the same post lists trust engineering as one of its later subjects, proposing a three-dimensional bill of materials for the AI era as the mechanism, and frames its overall answer as delivering trustworthy software out of a mixed human-and-agent team through systematic engineering constraints.
How well established it is: this is one author’s framing, stated in the opening instalment of the author’s own column and offered as a diagnosis rather than a measured finding. The post gives no measurement of the debt and no method for observing it.
Related Terms
- Verification Debt — the closely neighbouring cost of unverified output
- Comprehension Debt — the cost of code no one on the team has understood
- Review Bottleneck — the constraint this debt is said to accumulate behind
- Vibe Coding — the practice whose speed this debt is the counterpart to