Reliability Is a Property of the Loop, Not of the Component
You can ship cheap, noisy models and flaky tools if you explicitly budget surplus capability for a correction loop, because output fidelity is set by the feedback path rather than the forward path — but the guarantee is purchased from a gain budget and breaks under correlated, non-stationary failure, so the budget must be stated and monitored rather than assumed.
AngleTake the negative-feedback amplifier argument literally and follow it into model-selection economics: what per-call accuracy metrics stop telling you once reliability is a loop property, and what closed-loop metrics (convergence, oscillation, correction cost) replace them.
Source video ↗Stop Tuning Retries; Start Budgeting Distance to Instability
Retry depth, verifier strength, and timeout budgets are usually set by trial and error, but they are the agent equivalent of loop aggressiveness and should be chosen as an explicit slack between the nominal operating point and the failure point — expressed as a measured margin, not discovered as production oscillation.
AngleContrast gain/phase margin as a quantified safety factor with the current practice of discovering loop behaviour through burn-in, and show why 'more self-correction' purchases performance out of margin.
Source video ↗Your Context Window Is Not a Belief State
Most agent memory treats retrieved chunks, tool results, and model assertions as ground truth for the current turn; an estimator view says to carry an explicit belief over hidden task state, attach uncertainty to it, and update recursively — which is what makes behaviour degrade gracefully under contradictory or missing observations.
AngleArgue that storing values without confidence makes graceful degradation impossible, and that state estimation is a prerequisite for reasoning about whether a target is reachable or recoverable from what you can observe.
Source video ↗Separate the Objective, the Limits, and the Search
Planner prompts and agent loops typically conflate what good means, what is permitted, and how to compute a plan; keeping cost function, hard-constraint set, and decomposition method as separate inspectable artifacts turns budget, latency, and safety ceilings from prompt-dependent emergent behaviour into enforceable system properties.
AngleWalk through a single planner prompt and split it into three artifacts, showing what becomes structurally enforceable at each split.
Source video ↗