The situation
A session starts with "finish the app". Hours later it contains design debate, a half migration, three unrelated fixes and no reliable point where the work could stop. Every correction adds more old context to the same conversation.
The idea in one paragraph
A bounded session owns one coherent result that can be verified and handed off. It begins from a written entry point, adapts to small discoveries inside the boundary, records valid work outside it for later and closes only after evidence exists. The limit is semantic, not a timer.
| Phase | Question | Exit signal |
|---|---|---|
| Orient | What is true now? | Entry files read; baseline known |
| Build | What one result changes? | Agreed files and behavior updated |
| Verify | What would disprove "done"? | Relevant checks and visible flow pass |
| Close | Can a cold session continue? | State and next pointer written |
How it actually works
Work fits when its decisions share one context. A single page plus its content and test may fit; a new product, migration and launch plan do not. When a discovery changes the current result, adapt inside the session. When it is useful but independent, queue it. When it changes cost, risk or the meaning of the task, stop for a human decision.
Long sessions tend to accumulate stale attempts and competing goals. Starting fresh is not losing the work if the durable state, decisions and next action already live in the project.
What this changes for you
- Ask for one verifiable result, not an ambition such as "finish" or "clean up".
- Keep a small open-work queue so good discoveries do not hijack the current session.
- Close with evidence, changed state and the exact next entry point.
Where it breaks
Some incidents cannot be neatly sized before investigation. Bound the investigation instead: name the symptom, evidence to collect and stopping condition. Also avoid slicing one decision across several sessions merely to keep each diff small; that creates more handoff risk than it removes.
Terms used on this page
- Bounded session: one continuous work period aimed at one coherent, verifiable result.
- Stopping condition: the evidence or decision that ends the current investigation or build.
- Open-work queue: a durable list for valid work that does not belong in the current boundary.
- Judgment seam: a point where a discovery changes risk, cost or intent and needs human choice.
Read next
Plausible is not proven supplies the evidence gate that earns the close.