Field note: building the business layer in a week
By Soumen Sarkar · October 2026
Field note. In one week we turned Activity into one read-only feed, put the business teammates into the plan, and built the pieces that let them see and answer the work from a link. We also changed our price, our philosophy's name and our content plan, and shipped a blank-page bug we fixed three times.
What did we set out to do?
The week of 13 to 19 October started as a product week and ended as a business week. Our question was the one on our silos at agent speed hub: engineering moves at agent speed, so how does everyone else keep up without a meeting?
This note comes from our own record: the 84 commits in this repository that week and the progress section of our master plan. It doesn't come from Campfyrr itself. Our own cloud sessions still have no Campfyrr token, so they can't log their work there yet. That's on our list.
What did we build?
- Activity as one feed (14–17 October). Each project has one read-only feed, newest first. It shows decisions, assumptions, finished work, pages written and paused work. Each entry says why it matters first, then what happened.
- Handoffs as paused work. A session that stops unfinished shows as paused work, with the next step written out.
- Answering from a link (19 October). Each open assumption has its own page. Anyone with the link can keep it, correct it or pass it on, and the agent gets the answer. Activity links to that page while the assumption is open.
- Publishing from Claude Code (19 October). A
publish tool turns a plan, test results or a sample output into a page with a share link. That's the core of showing the work to people who don't read code. See how to publish a plan or test results. - Business context on an area (19 October). Anyone on the team can attach a customer's words, a pricing call or a deadline to part of the product. The next agent working there is told about it in its brief.
- A plain-words "where are we" view of a project, for people outside engineering.
The plan added business teammates as free readers early on 19 October, with "no features built". The features above landed later that same morning.
What did we decide?
- Nothing waits on a person. On 14 October, Activity had action buttons, a needs-your-action count in the top bar and a banner. A clash between two decisions went to both people to settle. A day later we removed all of it. Now a newer decision that clashes with an older one stands automatically, and the old one is marked replaced. The feed reports. It doesn't ask.
- Business teammates are free. We charge per developer. Founders, PMs, sales and support read and answer for nothing, as pricing says.
- Content follows the buyer's problems. On 14 October we wrote a philosophy-first library. On 19 October we replanned it around fourteen problem hubs. Ten hubs went live that evening.
What did we get wrong?
- The price, twice in one evening. On 18 October the revenue plan said $19 per developer. The master plan, committed sixteen minutes later, said $9. That's below every tool we compared and small enough for a lead to expense.
- The philosophy's name, three times. It was renamed on 14 October, and the same day the plan flagged that the new name was too close to another product's. On 17 October it became VibeFlock. Redirects kept every old link working.
- Our own product's name for its record. We called the team's story "the Lore". On 19 October we renamed it "the Record", so nobody mistakes it for Lore (lore.link), another product in this space.
- Blank pages. An imported README that only linked to another file showed as an empty page. We fixed it, then found blank-line files and headings-only files did the same. We fixed those too, and added a check that every scheduled run now uses.
What did we learn?
Most of the week's best calls were reversals, made fast and recorded with their reasons. That's fix forward in practice: ship the first version, see it, correct it in the open. The removed buttons taught us the most. A page that asks people to act becomes a queue. A page that reports, and lets people answer from a link when it's theirs to answer, keeps everyone moving.
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: Fix forward: We don't guard the gate. We correct the course.
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).