Bounded Work Slice
A context-design concept drawing on the idea of bounded contexts that defines explicit information boundaries for an atomic task. The slice contains all facts, constraints and interface definitions the task requires, while excluding unrelated history and side-branch decisions, thereby preventing the two failure modes of information overload and missing information.
Timeline (last 90 days)
The essence of handoff is defining a bounded work slice that contains all information needed to complete the current atomic task while deliberately excluding distracting content, rather than simply passing state.
The typical symptom of a slice that is too narrow is the agent repeatedly asking questions, requesting additional files, or making seemingly reasonable but actually wrong inferences based on incomplete information; the symptom of a slice that is too wide is the agent citing unrelated modules, carrying over old decisions, or diverging from the scope of changes during review.
The bounded work slice draws on the idea of "bounded context" in software engineering, and its boundaries are usually determined jointly by task type, change coupling and role requirements.
All Facts (3)
The essence of handoff is defining a bounded work slice that contains all information needed to complete the current atomic task while deliberately excluding distracting content, rather than simply passing state.
50%UnverifiedThe typical symptom of a slice that is too narrow is the agent repeatedly asking questions, requesting additional files, or making seemingly reasonable but actually wrong inferences based on incomplete information; the symptom of a slice that is too wide is the agent citing unrelated modules, carrying over old decisions, or diverging from the scope of changes during review.
50%UnverifiedThe bounded work slice draws on the idea of "bounded context" in software engineering, and its boundaries are usually determined jointly by task type, change coupling and role requirements.
50%