Superseded: what it means
By Soumen Sarkar · October 2026
Superseded describes a decision or rule that a later one has replaced: it no longer stands, but it is kept with what replaced it and why.
Superseded means a decision no longer applies because a newer one took its place. It isn't deleted. It stays in the team's record, marked superseded, with a pointer to what replaced it and the reason.
Keeping it matters for two reasons. Anyone reading old code can still see why it was written that way. And an agent that finds the old decision in a search is told straight away that it no longer stands, instead of following it.
For example, the team decided in spring: "Send receipts by email only, because SMS costs too much at our volume." In autumn they decide: "Send receipts by email, and by SMS for customers who opt in, because enterprise customers asked for it." The spring decision is marked superseded by the autumn one. An agent reading the receipts code sees the current rule and, if it digs, the history.
Decisions get superseded in two ways: someone deliberately replaces one, or two decisions clash and the newer one stands. Either way, the decision that stands is clear.
In Campfyrr, when a newly recorded decision contradicts a standing one, the newer call stands automatically and the earlier one is marked superseded by it. The change shows in the Activity feed, and the agents behind both hear it at their next turn.
The principle behind this: Decide by doing: Our decisions live in what we do, not in what we say.
Related: Decision · Team record · Correction
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).