AI coding agents changed how we ship. A change that used to take an afternoon now takes a conversation. What didn’t keep up was the record.
The reason behind a decision lived in a chat window that was gone by the next morning. “What changed, why, and is it live for this client?” meant digging through four places. And an agent that could publish a release or reply to a client on its own felt less like help and more like a liability.
So we built Pathledge: the delivery record for AI-built software.
One ticket number, from the idea to the live environment
The idea is simple. Every piece of work has one ticket number, and everything hangs off it: the decision, the resolution write-up, the release it shipped in, and which environments are running that release.
Your agent does the record-keeping. It gets a key, works as you with exactly your access, reads the ticket and its history before it starts, posts progress, and drafts the resolution and the release notes.
What it can’t do is just as important. It can’t publish a release, share anything with a client, or seal an evidence record. Those steps wait for a person, and they’re enforced in the database, not left to the agent’s good behaviour. Your agent drafts. You approve what ships.
What we’ve learned using it ourselves
Pathledge isn’t a mock-up. It’s the system of record for the team that built it. Over two months, one engineer and his AI coding assistant ran all of their work through it: 180 tickets in August and 390 in September.
We want to be careful with those numbers. Most of the tickets were raised by the engineer himself to record his own work. That’s the point of a record, but it means they don’t measure how quickly clients were answered. The jump from August to September coincides with the assistant taking over the record-keeping around each change. We believe that’s the cause; we haven’t proven it.
Who it’s for
- Freelancers and small studios, who need client-readable releases and a straight answer to “what is this client running?”
- Solo developers with a live product, who want the ticket, the decision and the release to still make sense in March.
- Small teams of one person plus agents, who need one record everyone can read and a line the agent can’t cross.
It is not for agents that publish and reply to clients unattended. That’s the one thing Pathledge is designed not to do.
Where things stand
Pathledge is in the final phases of beta testing with three teams. Access for the waitlist opens after that beta, once the multi-workspace version is ready, in waitlist order.
If that sounds like the record you’ve been missing, join the waitlist. You’ll get one email when there’s news, and nothing in between.