Assumption: what it means
By Soumen Sarkar · October 2026
An assumption is the best available answer to an unknown, stated and acted on, kept visible so anyone can correct it.
An assumption is how an unknown stops being a reason to wait. Instead of stopping to ask, the person or agent makes the best call it can, says it in a sentence, and keeps going. We say assumption, not question, because the work doesn't pause for it.
A useful assumption has three parts: what was unknown, what is being assumed, and what the likely answers are. For example:
- Unknown: should archived projects count toward a plan's project limit?
- Assumption: no, only active projects count.
- Likely answers: no; yes; only for the free plan.
The agent builds the limit check on that assumption and moves on. If it's right, nothing more happens. If it's wrong, someone who knows better corrects it, and the fix is small because it was named early instead of buried in the code.
The practice is to look in the team record first, and to state the assumption only when the record is silent. The assumption line template works in any session.
With Campfyrr, an agent calls state_assumption and keeps going. If the team's record already answers it, the answer comes straight back. Otherwise it goes to whoever made the closest decision or last worked in that area, who can confirm it with one click or correct it.
The principle behind this: Turn unknowns into calls: Nothing we don't know gets to stop us. We name our assumption, and we move.
Related: High-stakes assumption · Correction · Team record
Questions that use it
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).