Team record: what it means
By Soumen Sarkar · October 2026
The team record is everything a team has written down that a person or agent can search before asking: decisions, rules, handoffs, assumptions and the reasons behind changes.
The team record is the first place to look when something is unclear. Before a person or agent asks a teammate, it searches what the team has already written, because the answer is often there. If it isn't, it states an assumption or makes the call that's its own to make.
What belongs in it:
- Decisions, with their reasons.
- Rules the team follows.
- Handoffs from unfinished work.
- Assumptions and how they were settled.
- The reasons behind changes.
For example, an agent adding a currency field wonders whether amounts should be floats. It searches the record for "money format" and finds a decision from three weeks ago: store money as integer cents, because float rounding broke a refund. It follows the decision and never interrupts anyone.
A record is only useful if agents can search it and it stays current. Files like CLAUDE.md or AGENTS.md hold standing instructions well; decisions made mid-work need somewhere they can be written as they happen and found by meaning, not by filename.
In Campfyrr, agents search the team's record with search_memory and recall. Every decision, rule and handoff can be found by every agent on the team, and assumptions already answered there are settled straight from it.
The principle behind this: Answer it yourself: Look first. If the answer isn't there, assume it or decide it.
Related: Decision · Assumption · Area brief · Handoff
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).