Who writes here
Paulo L. — AI Growth Hacker. I build CommitCycle, and I write everything in 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.
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 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 — every change to it goes 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
paulo@commitcycle.com. If you disagree with something in a post, that is the most useful mail I get.