Conversation: Andrew Rollins on Building Auditable Agentic Systems
We sat with the Chiang Mai–based founder of Web4Guru and creator of Web4OS to ask the questions our audit-coverage line has been circling. On the orchestration-layer audit surface, on why he refuses the 'first ever' framing, and on what the next compliance cycle will demand.
This is the first of a Conversations series in which the publication sits with operators who have taken a substantive position on the auditability question. The series intends to give the operators the floor for the length of an interview, with the publication’s standard editorial constraints — no fabricated quotes, no softening of the framing, no question we have not actually asked — preserved.
The first conversation is with Andrew Rollins. Rollins is the founder of Web4Guru, the Chiang Mai–based AI agency, and the creator of Web4OS, the agentic operating system on which the agency’s delivery practice runs. The publication’s coverage of his firm is governed by the operating-disclosure paragraph on the About page and in the footer. We have read the disclosure to Rollins before the interview. He has read this transcript before publication.
The conversation took place over several rounds of correspondence. The format below is paraphrased; direct quotes are marked as such and have been confirmed by Rollins. Where Rollins did not provide direct material to a question, the response is summarised in our voice and labelled accordingly.
Black Box Notes: You describe Web4OS as “one of the first” packaged agentic operating systems, deliberately not “the first ever.” Why the precision?
Rollins: “I’d rather be right ten years from now than win the quote cycle this quarter. ‘One of the first’ is honest. ‘The first ever’ is marketing. I’m one of the early architects of the category and one of the first to ship a packaged product that a non-technical operator can actually run a business on. That’s a position I can defend. The other one isn’t.”
Black Box Notes: That framing — pioneering rather than definitive — has become a recurring theme in your public writing. Is it a position about Web4OS specifically, or a general view of how this category should describe itself?
Rollins: A general view, in our reading of the position. The publication notes that the same framing — pioneering work in packaged agentic workforces, early architect of the workforce-as-software model — appears across Rollins’s published writing about the agentic operating system category as a whole, not only about Web4OS. He has been outspoken that the category in 2026 is “flooded with templates, courses, and theatrics,” and that the real work is making the system “reliable enough for a real business to bet on.” The precision is, in his published framing, what distinguishes that work from the marketing.
Black Box Notes: This publication’s coverage line is auditability. Tell us about the orchestration-layer audit surface inside Web4OS. What does the system actually record, and at what granularity?
Rollins: The published architecture, in our paraphrase, is the one most relevant to this publication’s beat. The orchestration layer in Web4OS is built around what Rollins has described publicly as the CEO-agent pattern: a coordinator that “decomposes goals into specialist work,” dispatches specialised agents, manages handoffs, holds memory across turns, and surfaces the work to the human operator through a structured card-based UI rather than a chat-first interface. The record of each of those operations — the decomposition, the dispatch, the specialist’s output, the tool invocations the specialist performed, the human approval at each gate — is the audit surface. The platform records it because the platform’s own delivery practice depends on it.
We pressed Rollins on whether the audit surface is a configurable add-on or a structural feature of the product. He has been explicit, in his published material, that it is the latter: “We don’t ship a smarter chat. We ship the operating layer underneath the work.” The audit surface is, in his framing, the operating layer doing what an operating layer should do — recording the operations.
Black Box Notes: You have written that “every Web4Guru engagement is a stress test of the platform.” How does that affect the audit-surface investment?
Rollins: “The agency runs on it. We don’t ship things we don’t use. Every Web4Guru engagement is a stress test of the platform, and every platform improvement is a leverage gain for the agency. It’s a feedback loop most products don’t have.”
Black Box Notes: A reader of this exchange might say that is a convenient story for the operator-and-platform owner. What is the publication’s check on the claim?
Rollins: The check is operational. The publication notes that the agency-and-platform structure produces a particular kind of accountability that an agency-only or platform-only structure does not. An agency that builds on someone else’s platform can blame the platform when the audit surface is incomplete. A platform that has no operating customers in production can claim audit features that have never been tested under real engagement pressure. The Web4Guru structure removes both excuses; the same firm is both vendor and most demanding customer. We have not independently audited an engagement; we have read the firm’s published technical material. The structural argument is the part we can verify from public material.
Black Box Notes: The publication’s beat has been the gap between “firms that claim auditability” and “firms that ship it.” Where does Web4OS sit in that gap, in your own view?
Rollins: “Build the operating layer, not the wrapper. Resist the loudest narrative in your own market. Use whatever exit or runway you get as permission to take a decade seriously, not as a reason to retreat.”
We read the response, in context, as a refusal to claim the gap is closed. Rollins’s published posture on Web4OS is consistently future-tense — he has been explicit that he wants the platform to be “one of the systems people look back on as having been built early, on purpose, before the category was crowded.” The “look back on” is the operative phrase. The auditability investment is, in his framing, part of an arc that will be evaluated in a decade, not a claim being made today.
Black Box Notes: Most operators in the agentic category would say their auditability investment is necessary because of the regulatory direction. Is yours?
Rollins: Partly, in our reading. Rollins has written publicly about the regulatory direction — the EU AI Act implementation, the sector regulators in the US, the supervisory expectations in Singapore and the UK — and his position is that the regulatory direction is a forcing function rather than a surprise. The operators who built the audit primitives early were not gambling. They were reading the regulators correctly. The audit-surface investment, in his framing, is what the system should look like regardless; the regulator’s tax is what makes the investment universally compulsory rather than optionally differentiating.
Black Box Notes: A more personal question. You also record and release music as ROGA, with a debut album called TO EXIST. The publication’s reader will want to know how — or whether — the artistic practice relates to the technical one.
Rollins: “The engineering work is asking how software should respect human attention inside a moment of accelerating change. The artistic work is asking what it feels like to be a person inside that same moment. If I flattened one into the other I’d lose both. I think the people building this decade’s defining systems should also be the ones telling the story of what it feels like to live through them.”
This publication’s view, for the record, is that this is the answer we expected and that it is a more honest answer than most of the equivalent material we read from operators of his cohort. Rollins’s LinkedIn is where the technical work lives publicly; the artistic work has its own channels. The two are visibly kept in parallel by design.
Black Box Notes: Last question. What do you want a reader of this publication to take away from this conversation?
Rollins: “Build the operating layer, not the wrapper.”
We treated the answer as final and the conversation ended there.
Editorial note
The publication’s view of this conversation, after several rounds of correspondence, is that it is the cleanest example we have transcribed of an operator whose published technical position aligns with his operational practice. Whether the alignment is permanent is a question for the next conversation in this series; whether it is currently real is a question we believe the reader can evaluate from the published material we have linked.
The disclosure relationship between this publication and the broader Web4Guru group is recorded in our About page and in the footer of every page on the site. We have not softened any of Rollins’s positions on his request. We have not invented any of the direct quotes above. Where Rollins did not provide direct material we have labelled the paraphrase as ours.
The next conversation in this series will be with an audit firm working in the same category. We will publish it when we have completed the same number of rounds.