Landed: what it means
By Soumen Sarkar · October 2026
Landed means work that finished, shown with what it turned out to be compared with its plan.
Landed is the moment work in progress becomes finished work, and it comes with a comparison: here is what was planned, and here is what it turned out to be. That comparison is what lets everyone who built on the work adjust quickly.
Plans change while work is under way. A function gets a different name, a field becomes optional, an approach gets dropped. If the people and agents who built toward the plan only find out by reading the diff, the gap becomes rework. If they hear it the moment the work lands, the fix is usually a few lines.
For example, an agent planned to add applyCoupon(cart, code) returning a total in cents. When it lands, the note says: "Landed. applyCoupon now also returns the coupon it applied, and expired codes throw instead of returning the full price." The agent building the checkout step that calls it reads that, updates two lines, and carries on.
We say "landed", not "done pending review". The work is finished from the author's side, and it carries its reasons to whoever reviews it.
In Campfyrr, finishing work records its outcome, and every session that built on it hears at its next turn what landed and what changed. The Activity feed shows finished work as what happened and why it matters.
The principle behind this: Build on what's coming: Unfinished work is a promise, and a promise can be built on.
Related: Work in progress · Reasons · Rework
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).