Pathmode vs. Linear

Linear and Pathmode operate at different layers of the product-development stack — and they're complementary, not competitive.

Linear is the product development system. Issues, projects, sprints, comments, agents, Code Intelligence, Coding Agent — Linear runs the execution layer. Their May 2026 positioning made 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 Linear's execution layer. Its primitive is the evidence-anchored IntentSpec — a structured artifact carrying the why behind what's being built (objective, outcomes, edge cases, constraints, verification criteria), 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; Linear executes against it. Pathmode's IntentSpecs flow into Linear issues as structured context, and Linear's Coding Agent runs against that context rather than a free-text description. When code ships, Pathmode reconciles it against the intent — flagging drift where what shipped no longer matches what was decided.

Where Linear stops is the reasoning layer. 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 Linear'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.

Scenario: Customers keep abandoning the onboarding flow at the workspace-creation step.

With Linear alone, a PM opens an issue: "Improve workspace creation conversion." The description carries some context — maybe a screenshot, maybe a quote. The Coding Agent picks up the issue, reads the description, and ships a redesigned workspace-creation form. Conversion moves up four points. Six months later, no one remembers why the original form was structured that way, what edge cases were considered, or whether the change kept the constraint about email-domain validation intact.

With Pathmode upstream of Linear, the team first captures evidence on the Evidence Board: a metric ("42% drop-off at workspace creation"), three customer quotes ("I didn't know what to put in the workspace name"), and a session observation ("users hesitate on the slug field"). That evidence compiles into an IntentSpec: objective ("reduce workspace-creation drop-off to under 15%"), outcomes ("first-attempt completion rate > 80%"), edge cases ("SSO domains, reserved slugs, name collisions"), constraints ("email-domain validation must remain enforced for B2B accounts"), verification ("A/B test, statistically significant lift over two weeks").

The IntentSpec flows into a Linear issue as structured context. The Coding Agent executes against the spec, not a free-text description. When the code ships, Pathmode reconciles it against the intent: "shipped change does not enforce email-domain validation on workspace creation" — a real drift the team would have missed in Linear alone.

Linear ships the work. Pathmode keeps it honest.