Issue trackers and Pathmode overlap more than they did a year ago, and it is worth naming the overlap before the difference.
The trackers draft now, not just track. Linear's project composer develops an idea with its agent before the project goes live, pulling context from the workspace and connected tools to sharpen the brief and build a plan. Jira's Rovo drafts from workspace context. Asana's AI assistants summarize and propose work. So "the tracker has no upstream" is no longer true, and a reader who has used one of these composers will notice if a comparison says otherwise. What is still true is what the drafted brief does not carry.
Pathmode is the product judgment layer around the tracker. Its primitive is the evidence-anchored IntentSpec: a structured artifact whose parts each point at the signal that justified them. Its agent drafts as well, and that is the point of comparison. The difference is in what happens to the draft afterward.
Anchoring. Every requirement in an IntentSpec is anchored to a quote, a metric, or an observation. Pulling context in to sharpen a brief informs the prose and then stops being addressable, so the reason cannot be interrogated later.
Verification. When a pull request opens, Pathmode grades the diff against the intent and cites the code it relied on, flagging a dropped outcome or an unenforced constraint. Native code review reviews the code, and code intelligence explains the code. Neither measures the code against the brief that asked for it.
Residence. Pathmode's intent is a file in the repository the coding agent builds from, versioned with the code and readable by any agent over MCP. The tracker's brief lives in the tracker, which is why the brief and the codebase drift apart over the quarter after the issue closes.
Judgment state, the narrowest of the four. Linear shipped text attribution in July 2026: author indicators distinguish a colleague from the Agent from a Loop, agent edits highlight for review, and it persists through version history. Who typed a line is answerable there, and Jira and Asana are behind on even that. What a label does not carry is whether anyone has since resolved the line. In Pathmode an agent-added claim arrives unresolved and stays that way until a person keeps it, edits it, or removes it, and editing one makes it the editor's own. A label can be read or ignored. A state has to be cleared.
Where the trackers stop is the reasoning trail. Code intelligence can answer "what does this code do?" It cannot answer "why did we ship it this way?", "who decided to drop SSO and on what basis?", or "what did we give up when we narrowed the scope?" The brief holds the conclusion. It does not hold which parts a human accepted, what stood behind them, or whether the shipped code still honors them.
This shape holds across the category, with different amounts of drafting bolted on. Linear is the most aggressive about extending into AI-era execution, from the project composer through coding sessions to native diffs. Jira owns enterprise distribution and is adding Rovo across it. Asana sits in cross-functional work management. In all three the unit of work is a document, the reasoning behind it is unattributed, and nothing after the merge checks the code against what was decided.
They compose. Pathmode produces the intent and holds the result to it. The tracker schedules the work, runs the agents, and ships it. Pathmode's MCP server is a grounding source those agents can read from, so the drafting surface your team already likes works against an artifact that remembers.