Mechanism: Escalation — When to Switch Model, Mode, or Human
Escalation is a planned step-up when the current approach stalls — switch model, mode, human reviewer, narrower slice, or different…
Escalation is a planned step-up when the current approach stalls — switch model, mode, human reviewer, narrower slice, or different…
Interface-first means defining the contract — types, function signatures, route schemas, or module API — before the agent implements internals,…
A vertical slice is a single session that ships one path through the stack — request to response, UI to…
An example-driven spec defines behavior through concrete input/output pairs (and edge cases) before implementation — so the agent builds toward…
Acceptance criteria are specific, checkable conditions that must all pass for work to count as done — turning a (/mechanism-goal/)…
Split & conquer is planning work so each agent session has a single shippable job — with its own (/mechanism-goal/),…
Negative space is the practice of naming what must stay unchanged — files, behaviors, APIs, and styles — so the…
Rollback is having a known-good restore point — commit, stash, branch tip, or snapshot — before agent edits land, so…
A checkpoint is a mandatory pause — human or automated — between agent output and merge, where you review the…
A context budget is a deliberate limit on what you load into the model's window — files, history, rules, and…