Real example: the decision that replaced another
By Soumen Sarkar · October 2026
Real example. On 19 October 2026 our team replaced a four-day-old decision about how pages are found. The new decision was recorded, the old one was marked replaced, and the next session's brief opened with one line saying so, so no agent kept building on the call that no longer stood.
What was the first decision?
On 15 October 2026 we decided how people find pages in a Campfyrr project. The decision, recorded as "Pages are found by time and by label, never by folder", came with the change that built it. Its commit message reads, lightly trimmed:
Pages are found by time and by label, and replaced pages give way to the newest
A project's pages are listed by when they were last worked on: Current,
Last week, Last month, the month before by name, then everything older
together.
Labels say what a page is about and what it holds. They show under a
page's title; clicking one opens every page in the project carrying it.
Labels never appear in the navigation.
That was a clear call: time groups in the side menu, labels on the page, never in the menu.
What changed four days later?
On 19 October the founder looked at the menu and asked for something different. In their words, lightly edited:
The files should always have two dates: create date and update date.
The nav should use the update date and show Today, Yesterday, This week, Older.
Reduce the kind tags and subject tags. Use the documents themselves to come
up with tags. Predefined tags should focus on activity
(trending, hot, recent, debated, appreciated).
That request contradicts the first decision in two places. The time groups change. And tags, which the first call kept out of the navigation, now belong in it.
So the session recorded a new decision, "Pages are found by update day and by tags", and shipped the change the same afternoon. The commit says:
Pages keep two dates; the rail groups by update day and adds activity tags
Every page shows when it was created and when it was last updated. The
rail lists a project's pages under Today, Yesterday, This week and Older
(by update, in the reader's time zone), then a folded Tags line: Hot,
Trending, Debated, Appreciated and Recent.
Nobody edited the old decision or deleted it. Because the new one clashed with it and was newer, the new one stands, and the old one is marked superseded, kept in the record with a pointer to what replaced it.
How did the next session find out?
The next agent session in the project started with its brief, as every session does. The brief's "What changed" section carried two lines about this, quoted as they arrived:
- Reversed: Pages are found by time and by label, never by folder
→ Pages are found by update day and by tags -- Time groups changed to
Today, Yesterday, This week, Older, and tags (activity and topics) are
now in the navigation. (Camp Scout, today)
- The call "Pages are found by time and by label, never by folder"
lasted 4 days before Camp Scout replaced it.
Both titles in the first line link to the two decision pages. The session didn't have to search, ask anyone, or notice a contradiction on its own. It read which call no longer stood, which one replaced it, and why, before it touched any code.
The project's Activity feed shows the same change to anyone who opens it. It's read-only: it shows what happened, and nobody has to approve anything there.
What does this show a tech lead?
- Decisions change, and that's healthy. This one lasted four days. Building the first version is how we learned what the founder wanted from the menu.
- The newest call has to win on its own. If both lines sat side by side in a CLAUDE.md, Anthropic's docs warn that Claude "may pick one arbitrarily". That's the pattern behind why CLAUDE.md keeps growing.
- Sessions hear about the reversal, not just the new rule. A line saying "this replaced that" stops an agent from defending the old call it saw last week.
Where do I go from here?
The problem this answers: Agents ignore team decisions: "Agents break team decisions, and CLAUDE.md doesn't help."
The principle behind this: Decide by doing: Our decisions live in what we do, not in what we say.
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).