--- title: "About — CommitCycle" description: "Who writes the CommitCycle Insights posts, what they work on, and what you can check before deciding whether to believe any of it." url: https://commitcycle.com/about/ language: en --- # Who writes here > Who writes the CommitCycle Insights posts, what they work on, and what you can check before deciding whether to believe any of it. **Paulo L.** — AI Growth Hacker. I build CommitCycle, and I write everything in [Insights](https://commitcycle.com/insights/). ## What I work on CommitCycle is change management for AI coding agents: grants that are bound to one task and one branch and expire on their own, zones that carry an owner and a risk level, an approval moment when a wall has to move, and a per-task record of what a task declared against what it actually touched. **Claude:** Add the board’s connector URL and Claude files and scopes the task from the chat — nothing to install. It cannot approve access: the gate and the zone’s owner decide. **Cursor:** The same connector in Cursor: start the task, read why a file last changed, hand the work in. With the connector alone, nothing on the machine blocks a write. **Console:** In the console a task crosses the gate into In Progress, and a zone’s owner answers an access request — for one hour, four, or until the task closes. **Claude Code:** The hook refuses the write before it lands, names the zone and its owner, and the agent asks for access instead of looking for another way in. Claude Code is where this block has been seen working. **Terminal:** From a terminal, cycle does each step in one command: start brings the grant onto the machine, submit hands it back. It exists because the interesting failure with coding agents is not that they write bad code. It is that they write plausible code in places nobody asked them to go, and that the reasons behind a repository's conventions live in people's heads where an agent cannot read them. ## Why these posts exist Most of what is written about AI agents is written by people selling agents. I am selling something too, so that is not a claim to be above it — it is the reason each post here carries a date and a single sentence stating what it argues, and the reason the posts say plainly where the argument stops working. The line I hold myself to is that a post has to be useful to someone who never installs anything of mine. If the only way a piece pays off is by buying something, it was an advertisement wearing an essay. ## What you can check Everything above is a claim about me, so here is the part that is not. The plugin installs the enforcement and runs on your machine; npm installs the CLI, which is the process without the wall. The [documentation](https://commitcycle.com/docs/) is public, including the pages still marked as pending, because a stub labelled as one is more honest than a page pretending to be finished. This site is built with the process the product enforces — changes to it go through a task, a gate and an audit record. The hosted board is invitation-only while this is small. Saying so is not modesty; it is the single most useful fact for anyone deciding how much weight to put on the rest. ## Getting in touch . If you disagree with something in a post, that is the most useful mail I get.