For operations and compliance: knowing what changed and why
By Soumen Sarkar · October 2026
For you. When agents build fast, operations and compliance need to know what changed and why, not only who merged it. Campfyrr records each decision with its reason as it is made, writes the reasons for every change in plain words, and keeps replaced decisions with a pointer to what replaced them. It has no audit logs yet; those are planned.
What does an operations or compliance day look like right now?
You're asked to explain a change after it has shipped. Why does the refund screen now skip a step? Who decided exports leave out a field? When did that rule change, and what was it before?
The tools you have answer part of it. A code host's audit log is good at the facts of an action. GitHub's, for example, records "who performed the action, what the action was, and when" (GitHub docs, reviewing the audit log). What it can't tell you is why. The reason sat in an engineer's session, and the session ended.
Agents are the best collaborators a team has had, and they make good calls quickly. What breaks is the path from the person or agent who made a call to the person who has to account for it later. Engineering moves at agent speed, and the explanation reaches you a week late, if it reaches you at all (silos at agent speed).
What changes for you with Campfyrr?
- Each decision is written down when it's made, with its reason. A decision is one sentence saying what was decided and why, recorded in the work, not written up after. Every later session in that part of the product is given it.
- Each change carries its reasons. When a session commits or opens a pull request, Campfyrr writes a reasons page: what the change is for, the calls made, what was assumed, and what was tried and dropped. The link goes in the pull request (why review is slow).
- Nothing is quietly overwritten. When a newer decision replaces an older one, the older one is marked superseded. It stays in the record with a pointer to what replaced it.
- It's written in plain words. You read it from a link. You don't need to read code.
What does that look like in our own record?
On 15 October 2026 our team decided that pages in a Campfyrr project are found "by time and by label, never by folder". On 19 October the founder asked for something different, and a new decision was recorded: "Pages are found by update day and by tags". The first decision wasn't edited or deleted. It was marked replaced, with a pointer to the new one, and the next session's brief said so in one line. The whole trail is in the decision that replaced another.
That's the question you're asked most: what was the rule, what is it now, and when did it change? The record answers it without a meeting.
What doesn't Campfyrr do?
Be clear about this before you rely on it:
- It has no audit logs yet. Audit logs and retention controls are planned for a later Business plan (pricing). Today, don't use Campfyrr as your system of record for a regulated sign-off.
- It only knows what sessions recorded. A call nobody logged isn't there.
- It doesn't review code, run tests or replace CI. Keep your code host's audit log and your approvals where they are.
- It never takes your code, diffs or session transcripts. It keeps the context of the work. The trust page lists what it keeps.
Use it beside your audit log, not instead of it. The log tells you who and when. The record tells you why.
What are the first three things to try?
- Ask a developer to invite you to the project.
- Open the reasons link on the next pull request. Read what it's for and the calls made.
- Ask a developer's session to search the record for one rule you're asked about. Note when it changed and what it replaced.
What's free for operations and compliance?
Everything, right now: Campfyrr is free for everyone during early access. When paid plans start, teams pay for developers. People who only read and answer stay free (pricing). A developer installs it from /connect. For the approver's view of risk and rollout, read the page for CTOs.
The problem this answers: Silos at agent speed: "Engineering moves at agent speed, but product, design, QA and the business still work in separate silos."
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
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).