Issue trackers and Pathmode operate at different layers of the product-development stack — and they're complementary, not competitive.
Issue trackers are the product development system. Linear leads the modern pack, with Jira and Asana running the long tail. Their job is execution: sprints, assignments, status, comments, agents, code intelligence, coding agents. Linear's May 2026 positioning makes it explicit: "the shared product system that turns context into execution." Their primitive is the issue. Their source of truth is the code.
Pathmode is the product judgment layer. It sits upstream of the issue tracker. Its primitive is the evidence-anchored IntentSpec — a structured artifact carrying the why behind what's being built, with each part traced to the evidence that justified it. Its source of truth is intent, not code. Intent is judgment under evidence, not a contract you compile.
The two layers fit together. Pathmode produces the intent; the issue tracker executes against it. Pathmode's IntentSpecs flow into Linear/Jira/Asana issues as structured context, and coding agents run against that context rather than free-text descriptions. When code ships, Pathmode reconciles it against the intent — flagging drift where what shipped no longer matches what was decided.
Where issue trackers stop is the reasoning layer. Linear's Code Intelligence can answer "what does this code do?" by reading the codebase. It can't answer "why did we ship it this way?", "who decided to drop SSO and on what evidence?", or "what tradeoff was made when we narrowed scope?" — because the issue tracker's system doesn't hold the reasoning. The issue description is dead text once the issue closes. Pathmode is the system of record for those decisions.
This is the architectural pattern that holds across every issue tracker in this category. Linear is the most aggressive about extending into AI-era execution (coding agents, code intelligence, automations). Jira owns enterprise distribution. Asana sits in cross-functional work management. The category-level shape is the same: free-text issue as the unit of work, code as the source of truth, no structured place for the reasoning that produced the work in the first place.