“Why not just use an issue tracker?” is the first question people ask about Pathledge. It’s a fair question. Modern issue trackers are excellent, and many now let you assign work to an AI coding agent.
The honest answer is that they’re built to answer a different question. If you ship software for clients with an agent doing much of the typing, it helps to know which question you’re actually trying to answer.
Two questions, two kinds of tool
An issue tracker answers: what should we work on next? It’s built around planning. Backlogs, priorities, cycles, roadmaps, who’s doing what this week. It shines when a product team needs to agree on what to build and in what order.
A delivery record answers: what shipped, why, who approved it, and where is it live? It’s built around proof. Every change keeps its reasoning, its resolution and the release it went out in. Every environment shows which release it’s running. When a client asks “is that fix live for us?”, you answer from the record, not from memory.
Both are useful. They just look forward and backward respectively.
Where the difference shows up
After the ticket is closed
In a planning tool, a closed ticket has done its job. In a delivery record, closing is where the useful part starts.
In Pathledge, each resolution records the root cause, what was done and how it was verified. The ticket then belongs to a release, and the release is recorded against the environments running it. One ticket number links all of it, from the first report to the client’s production environment.
When the release goes out
Most teams write release notes as an afterthought, in a different tool from where the work happened.
In Pathledge, a release has a business summary, a client note, a security note and an answer on whether it needs a maintenance window. It can’t be published with any of them missing, and only an admin can publish it. Your agent can draft all four from the tickets in the release. A person reads them and presses publish.
When you have more than one client
Product teams usually run one product in one production environment. Freelancers and small studios often run the same software for several clients, each on a different release.
Pathledge’s Fleet view shows each client environment against the newest release, and it writes the upgrade note for you. Security fixes are left out of upgrade notes until every production environment has them, so you don’t advertise a fix to one client while another is still exposed.
When the agent is doing the work
Many trackers now treat an AI agent as another assignee. That’s great for getting work done. The open question is what the agent is allowed to do on its own.
Pathledge draws the line in the database. Publishing a release, sharing a resolution or a file with a client, and sealing an evidence record are admin-only, whatever the request says. Tickets your agent raises are labelled as agent-raised. We wrote more about where we drew that line, and the one catch to watch for.
When the client wants to see progress
Planning tools are mostly built for the team doing the work, not for the client paying for it.
Pathledge has a moderated client portal. Comments, files and resolutions are internal by default. A client sees only what an admin chooses to share, and their “request closure” button asks; it never closes anything by itself.
So which one do you need?
You probably want a planning-first issue tracker if:
- you’re a product team deciding what to build next
- your main problem is prioritising a busy roadmap
- you ship one product to one production environment
You probably want a delivery record if:
- you build for clients and get asked “what changed, and is it live for us?”
- an AI agent writes much of the code, and you want its reasoning kept after the chat window closes
- you need a firm line between what the agent drafts and what a person approves
- you run several client environments on different releases
Plenty of teams will use both: a tracker to plan, and a record to prove what shipped. Pathledge is built for the second job, and it does that job end to end.
Where Pathledge stands
Pathledge is in the final phases of beta testing with three teams. If the second list sounds like your week, join the waitlist. You’ll get one email when there’s news, and nothing in between.