Linear vs Asana

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Asana
   Linear~partialclaimed6/10

   Linear's developer docs are exposed as clean .md pages (agents.md, graphql.md, webhooks.md, sdk.md, aig.md), a pattern consistent with agent-oriented/llms.txt-style documentation that an AI agent could be pointed at directly. However, there's no explicit llms.txt file cited, no first-party statement framing these docs as agent-consumption-optimized, and no independent evidence of an agent successfully using them this way. Missing for 10: explicit llms.txt manifest, documentation of agent-readability intent, third-party confirmation of successful agent consumption.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “The agent must signal its identity clearly so that it can never be mistaken for a person.”

   proof ↗⚑ flag

   Asana✓fullprobed8/10

   A probe confirms Asana serves a live llms.txt at developers.asana.com/llms.txt with markdown-append instructions for docs pages, directly enabling agent-native doc consumption, and this sits alongside a full REST API reference, OpenAPI spec repo, and API explorer. Missing for 10: independent/community confirmation of agents actually using llms.txt in practice, and a discoverable OpenAPI JSON endpoint (probe found 404s on standard paths, mitigated by the GitHub-hosted spec).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.asana.com/llms.txt # Asana Docs Documentation > Documentation for Asana Docs Append .md to …”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Linear
   Linear✓fullclaimed7/10

   Linear exposes a full GraphQL API with API-key and OAuth2 authentication, a typed SDK, webhooks for event-driven automation, and documented rate limits/deprecation policy — all of which allow scripting issue creation, queries, and workflow automation entirely headlessly (e.g. from CI pipelines) without the UI. Missing for 10: no dedicated CLI tool or explicit CI/GitHub Actions integration guide, and no independent hands-on report of using the API in a CI pipeline.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Asana exposes a token-authenticated REST API with webhooks and rule-based automation, enabling scripted/headless interactions suitable for CI-like automation (asana-docs-1, asana-docs-2, asana-docs-15, asana-docs-16, asana-docs-17). However, there is no explicit documentation of CI/CD integration, CLI tooling, or headless execution patterns tailored for automated pipelines. missing for 10: explicit CI/CD examples, dedicated CLI or headless runner, evidence of automated pipeline usage beyond generic API/webhook mentions.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Linear—none0/10

   All MCP-related evidence (linear-probe-1, linear-docs-67, linear-intdir-4, linear-intdir-6) describes Linear exposing its OWN MCP server so that other tools (Cursor, Claude) can connect TO Linear — the opposite direction from the story, which asks whether a user can plug external MCP servers INTO Linear so Linear's agent can use their tools. No evidence shows Linear or Linear Agent consuming/importing third-party MCP servers as a client.

   • [probe] “official MCP server documented at https://linear.app/docs/mcp”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
   • [claimed-docs] “Connect Cursor to the Linear MCP server”
   • [claimed-docs] “Connect Claude to the Linear MCP server”

   proof ↗⚑ flag

   Asana—none0/10

   Evidence confirms Asana publishes an official MCP server (asana-probe-3), meaning Asana exposes its own tools to other MCP clients — but the story asks the reverse: whether a user can plug external MCP servers into Asana so its AI (e.g., AI Teammates/AI Studio) can consume their tools. No evidence pack item describes Asana's AI agents acting as an MCP client or supporting configuration of external MCP servers as tool sources.

   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Asana
   Linear✓fullprobed7/10

   Linear publishes an official MCP server (docs page at linear.app/docs/mcp) and the changelog confirms ongoing feature work on it (e.g., Okta-based access management via Linear's MCP), showing agents can connect through this official channel. Missing for 10: independent/hands-on verification of the MCP server in use and detailed docs on setup/tool coverage beyond the single probe reference.

   • [probe] “official MCP server documented at https://linear.app/docs/mcp”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”

   proof ↗⚑ flag

   Asana✓fullprobed8/10

   Asana documents an official MCP server at a dedicated docs page (asana-probe-3: developers.asana.com/docs/using-asanas-mcp-server), confirming a first-party MCP integration for connecting agents. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and more detail on setup/auth scope beyond the docs link.

   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack documents Linear's GraphQL API, TypeScript SDK, webhooks, OAuth, and MCP server, but nowhere mentions an official command-line interface (CLI) tool for interacting with Linear. Since CLI is a plausible and common tool for developer-facing products, its absence here is a gap rather than an inapplicable axis.

   ⚑ flag

   Asana—none0/10

   Evidence shows Asana has a REST API, OpenAPI spec, and even an MCP server, but nothing mentions an official CLI tool for interacting with Asana. missing for 10: any documentation of an official Asana CLI, install instructions, or command reference.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Linear✓fullclaimed9/10

   Linear ships a well-documented public GraphQL API with introspection, an explorable schema via Apollo Studio, OAuth2/API-key auth, TypeScript SDK, webhooks, rate-limit documentation, and a deprecation policy, giving AI-native users a robust way to programmatically drive the product. missing for 10: independent hands-on developer reports validating real-world API usage/reliability beyond Linear's own docs.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”

   proof ↗⚑ flag

   Asana✓fullclaimed9/10

   Asana publishes a documented REST API with authentication, resource-oriented endpoints, an in-context API explorer, an official OpenAPI spec repo, a developer sandbox, and deprecation/versioning guidance — clearly enabling programmatic/agentic control of the product. Missing for 10: independent third-party hands-on verification of API robustness/reliability beyond vendor docs.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “the API itself will also alert you of upcoming changes. Shortly after we post communication, the API will begin sending Asana-Change headers…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Linear
   Linear~partialclaimed6/10

   Linear documents OAuth2 apps with distinct scopes (e.g. app:assignable, app:mentionable) for building agents, admin approval workflows for third-party apps, and per-key rate limits differentiated by auth type, which together enable a degree of least-privilege credentialing for agent integrations. However, personal API keys (the simpler credential path) are not shown to be scope-limited, and there's no first-party or independent evidence of fine-grained per-resource/action scoping akin to full least-privilege IAM. Missing for 10: documentation of scoped personal API keys, granular resource-level permission control beyond the small named scope list, and independent/hands-on verification of least-privilege enforcement.

   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”
   • [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
   • [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”
   • [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”

   proof ↗⚑ flag

   Asana~partialclaimed5/10

   Asana documents token-based API authorization (asana-docs-1) and describes AI Teammates having scoped permissions, identity, and audit trails governed centrally (asana-docs-13), suggesting some notion of least-privilege agent credentials. However, there is no concrete documentation of issuing scoped/limited-permission API tokens or OAuth scopes specifically for third-party agents, nor granular permission configuration UI/API for developer-issued credentials. missing for 10: explicit scoped OAuth/token permission model documentation, developer-facing controls to limit an API credential's access surface, and independent verification that agent credentials can be scoped rather than full-account access.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear publishes an official TypeScript SDK exposing its GraphQL schema with strongly typed models (linear-docs-53, linear-docs-89, linear-docs-93), backed by full GraphQL API docs, introspection, published schema SDL, OAuth2/API key auth, rate limits, and deprecation policy (linear-supp-graphql-introspection, linear-supp-apollo-explorer, linear-supp-rate-limits, linear-supp-deprecations, linear-docs-99, linear-docs-50). This gives AI-native developers a solid, well-documented official SDK to build against. Missing for 10: independent/hands-on developer corroboration (e.g., GitHub stars, community usage reports) of the SDK itself beyond official docs, and SDKs in languages beyond TypeScript.

   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Install the Linear SDK to use strongly typed models and operations”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack extensively documents Asana's REST API, OpenAPI spec, sandbox, and deprecation policy, but never mentions officially maintained client SDKs (e.g., Python/Node/Java libraries) for developers to build against. Missing for 10: any documentation or reference to first-party SDK packages, language coverage, or SDK versioning/support.

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.asana.com/openapi.json, https://developers.asana.com/swagger.json, https://develo…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear provides documented webhooks with a webhookCreate mutation to subscribe to HTTP push notifications for data create/update/delete events, plus in-app event subscriptions for project views routed to Inbox/Slack, giving AI-native users clear ways to consume event streams programmatically. Missing for 10: independent/hands-on corroboration of webhook reliability or payload completeness beyond first-party docs.

   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”

   proof ↗⚑ flag

   Asana✓fullclaimed7/10

   Asana's platform docs explicitly list webhooks alongside rules and API as a core automation mechanism, allowing external systems (including AI agents) to subscribe to Asana events. missing for 10: no dedicated webhook payload/signature-verification docs or independent hands-on confirmation of webhook reliability in the pack.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

10. ai-native userHand off work between tools or agents without losing context or information

    weight 1 · round to Linear
    Linear✓fullclaimed7/10

    Linear documents extensive hand-off machinery for agentic work: issues can be delegated (not assigned) to AI agents while humans retain ownership, agents behave like workspace members (mentions, comments, docs) so context stays attached to the issue, and MCP/integration connectors (GitHub, Copilot, Codex, Claude, Cursor, Slack) let work flow between tools while Linear remains the shared context hub. Features like 'Write with Agent' (pulls prior updates plus Slack context), checkpoints/version history, guided reviews with before/after screenshots, and Loops updating linked docs/Slack on changes all reinforce continuity across handoffs. missing for 10: independent/hands-on verification that context genuinely survives cross-tool handoffs (all evidence is first-party docs), and no explicit benchmark/comparison of information loss vs other tools

    • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
    • [claimed-docs] “Assigning an issue to your app now sets it as the delegate, not the assignee—so humans maintain ownership while agents act on their behalf.”
    • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
    • [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
    • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
    • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
    • [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
    • [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
    • [claimed-docs] “The agent opens the app, navigates through a flow, and verifies its implementation. It also captures before-and-after screenshots”
    • [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
    • [claimed-docs] “Connect Cursor to the Linear MCP server”
    • [claimed-docs] “Connect Claude to the Linear MCP server”
    • [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
    • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
    • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
    • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”

    proof ↗⚑ flag

    Asana~partialprobed6/10

    Asana documents shared memory across AI Teammates so context 'carried forward' between agents, governance/permissions for agent handoff, and cross-tool integration via API, webhooks, app components, and an official MCP server enabling handoff to external agents/tools. However, all of this is vendor-documented with no independent or hands-on verification that context is actually preserved end-to-end across tool/agent handoffs. Missing for 10: independent/hands-on corroboration of lossless handoff, concrete example of an agent-to-agent or tool-to-tool handoff preserving full context, and clarity on how MCP server handles context transfer in practice.

    • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
    • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
    • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
    • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”
    • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
    • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

    proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Linear~partialclaimed6/10

   Linear ships AI-agent features (Write with Agent for project updates, Loops for automated doc/plan updates, auto-triage/routing of feedback into issues, Linear Agent investigating issues) that surface generated content and suggestions inside the product, per linear-docs-19, linear-docs-38, linear-docs-45, linear-docs-62, linear-docs-95-97. However, these are framed as agentic task-execution/automation rather than analytic 'insights' (e.g., trend analysis, prioritization recommendations, summarization dashboards), and there's no independent/hands-on evidence validating quality of these AI outputs. missing for 10: dedicated insight/analytics generation (e.g., pattern detection across issues, predictive suggestions, summarized health reports) and third-party corroboration of suggestion quality.

   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
   • [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Asana markets AI Teammates, AI Studio, and 'Asana Dash' as an AI Chief of Staff that surfaces insights and suggestions drawing on Work Graph context and shared memory, which directly matches the story. However, these are vendor claims only—there's no independent/hands-on evidence confirming quality or reliability of these AI-generated insights, and details on how proactive/contextual the suggestions are remain thin. Missing for 10: independent corroboration of AI insight quality, concrete examples of AI-generated suggestions in action, hands-on user reviews of Dash/AI Studio outputs.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's "Loops" feature explicitly lets users describe a job in plain language and set it to run on a schedule or in response to events, enabling autonomous background automations (e.g., updating docs, posting Slack updates, monitoring initiatives) without manual triggering. This is well documented across multiple changelog entries describing scheduling, event triggers, and recurring workflows. Missing for 10: independent/hands-on verification of reliability at scale and no third-party community confirmation of autonomous background execution in practice.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “You can now add a loop to Favorites”

   proof ↗⚑ flag

   Asana✓fullclaimed7/10

   Asana documents rule-based automations, webhooks, and 'AI Studio' for no-code autonomous workflows, plus 'AI Teammates' that run inside workflows with shared memory, scoped permissions, and audit trails — directly supporting background/autonomous automation. Missing for 10: independent/hands-on corroboration that these automations reliably run unattended in production, and more detail on triggers/scheduling beyond marketing copy.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Linear
   Linear✓fullclaimed8/10

   Linear ships a built-in 'Linear Agent' that users can delegate issues to directly (assign/mention), which writes code via Claude Code/Codex, edits text, runs Loops for recurring work, drafts project updates, and shows delegated work status in My Issues, all documented extensively in first-party changelog docs. missing for 10: independent/hands-on verification beyond vendor changelog, and clearer detail on reliability/limits of the built-in assistant in real-world use.

   • [claimed-docs] “Linear Agent can now write code using Claude Code and Codex.”
   • [claimed-docs] “Linear Agent can now set up, run, and test your code before returning its work.”
   • [claimed-docs] “We’ve also added section under My Issues → Assigned for your delegated issues. It shows the status of each coding session, and gives you a q…”
   • [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date.”
   • [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
   • [claimed-docs] “@Linear can you take a stab at this?”

   proof ↗⚑ flag

   Asana✓fullclaimed7/10

   Asana ships pre-built AI Teammates/agents (asana-docs-5,6,12,13) and Asana Dash described as an 'AI Chief of Staff' (asana-docs-8) that work within tasks/workflows with shared memory and governance, directly matching delegation of tasks to a built-in assistant. Missing for 10: independent hands-on reviews or third-party validation of AI Teammates actually performing delegated tasks, and detail on the scope/reliability of delegation beyond vendor marketing copy.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear supports natural-language interaction extensively: users can @mention Linear Agent, describe jobs in plain language for Loops, use 'Write with Agent' to draft updates, and delegate issues via comments in natural language (linear-docs-11, -19, -36, -41, -68). This is well documented across multiple first-party changelog entries and the agents.md docs, but missing for 10: independent/hands-on evidence of natural-language command accuracy or limitations, and no dedicated NL command palette/chat interface separate from agent-delegation workflows.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Once connected to Linear, teammates can delegate issues to your agent or mention it in comments.”
   • [claimed-docs] “@Linear can you take a stab at this?”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”

   proof ↗⚑ flag

   Asana~partialprobed6/10

   Asana ships AI Teammates/AI Studio and a Chief-of-Staff style agent (Dash) described as operating with shared memory and governance, plus an MCP server enabling natural-language agent interaction, suggesting real natural-language control surfaces exist. However, there is no first-party documentation or hands-on evidence showing an end user issuing free-form natural-language commands directly in the core Asana UI to create/manage tasks; most 'AI-native' evidence is marketing copy without demonstrated workflows. missing for 10: hands-on demonstration or detailed docs of natural-language command execution in the main product UI, independent verification of Dash/AI Teammates handling arbitrary NL requests, and clarity on how MCP server maps to end-user NL commands versus developer/agent use.

   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”
   • [probe] “official MCP server documented at https://developers.asana.com/docs/using-asanas-mcp-server”

   proof ↗⚑ flag

5. ai-native userBuild and configure my own custom AI agent within the product

   weight 2 · round drawn
   Linear~partialclaimed6/10

   Linear offers in-product mechanisms for creating custom agent-like automation: Loops let users 'describe the job in plain language' and set it to run on a schedule or event (linear-docs-36/95-100), and Skills let teams codify and share recurring agent workflows (linear-docs-23/46). Linear also documents a developer-facing Agents API for building agents that behave like workspace members (assignable, mentionable, can comment) (linear-docs-16, linear-docs-54/64/75/90/94). This is meaningful but falls short of a full custom-agent builder with model/tool selection or a dedicated no-code agent studio. Missing for 10: no evidence of choosing/configuring underlying models or custom toolsets, no dedicated 'agent builder' UI beyond Loops/Skills, and no independent hands-on confirmation of ease-of-use.

   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
   • [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
   • [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
   • [claimed-docs] “How to best integrate an AI agent into Linear”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “app:assignable | Allow the app to be assigned as a delegate on issues and made a member of projects app:mentionable | Allow the app to be me…”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Asana markets 'AI Studio' for no-code agent automations and 'custom AI Teammates' built from team expertise, with governance and shared memory features (asana-docs-6,7,12,13), indicating a self-service agent-building capability. However, all evidence is first-party marketing copy with no tutorial, screenshots, or independent hands-on account of actually configuring an agent end-to-end. missing for 10: independent/hands-on verification of building a custom agent, detailed step-by-step configuration docs, community confirmation of the feature working as advertised.

   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Asana
   Linear~partialclaimed6/10

   Linear's GraphQL API supports introspection and is explorable/queryable via Apollo Studio Explorer with no login required, effectively an interactive reference with runnable queries, plus published docs with sample queries/mutations and an SDK. However, this is a third-party hosted explorer rather than a first-party embedded interactive API reference, and there's no evidence of runnable examples directly within Linear's own developer docs site. missing for 10: first-party embedded interactive API console with runnable examples on developers.linear.app itself, independent/hands-on confirmation of the Apollo Explorer experience, broader runnable example coverage beyond basic query/mutation snippets.

   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Learn how to use the GraphQL API to query and mutate your data”

   proof ↗⚑ flag

   Asana✓fullclaimed8/10

   Asana's developer docs explicitly state each API endpoint has a built-in, in-context API explorer for making requests and viewing responses (asana-docs-16), backed by a RESTful reference (asana-docs-15) and an official OpenAPI spec repo (asana-supp-openapi-spec, asana-docs-20), plus a developer sandbox for safe testing (asana-docs-17). Missing for 10: independent/hands-on confirmation of the explorer's runnable examples in practice, and a working public openapi.json endpoint (probe found 404s at standard paths).

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Asana
   Linear~partialclaimed6/10

   Linear's API is GraphQL, not OpenAPI/REST, but it explicitly supports schema introspection and publishes a full schema SDL file in the linear/linear GitHub repo, plus an explorable schema via Apollo Studio — giving AI-native users machine-readable access to the API's shape without needing a human-written spec. This satisfies the intent of a downloadable machine-readable spec via GraphQL introspection/SDL rather than OpenAPI itself. missing for 10: no explicit OpenAPI/Swagger document, no single-click 'download spec' artifact, and no independent/community confirmation of using the introspection or SDL file in practice.

   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Linear's public API is built using GraphQL.”

   proof ↗⚑ flag

   Asana✓fullprobed9/10

   Asana publishes an official OpenAPI specification (asana_oas.yaml plus app-components spec) in the Asana/openapi GitHub repo, which is machine-readable and downloadable, and the REST API docs corroborate a resource-oriented JSON API with in-context explorer built from this spec. Missing for 10: a directly hosted openapi.json/swagger.json endpoint on developers.asana.com (probe found 404s at expected discovery URLs), so users must know to fetch it from GitHub rather than a standard API-discovery path.

   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.asana.com/openapi.json, https://developers.asana.com/swagger.json, https://develo…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Asana
   Linear~partialclaimed5/10

   Linear's own docs explicitly state its GraphQL API 'doesn't have versioning like many REST APIs,' but they do document a deprecation policy: use of the @deprecated schema directive, proactive outreach for breaking changes, and changelog entries tagged [API]. This satisfies the 'documented deprecation policy' half of the story but directly contradicts the 'versioned APIs' half. Missing for 10: an actual versioning scheme (e.g., v1/v2 endpoints or dated API versions), and independent/community corroboration that deprecation notices are reliably honored in practice.

   • [claimed-docs] “Docs, "Deprecations": "Linear's GraphQL API doesn't have versioning like many REST APIs... we take breaking changes and deprecations serious…”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”

   proof ↗⚑ flag

   Asana✓fullclaimed8/10

   Asana documents a formal deprecation process with Asana-Change headers, Asana-Enable headers for opt-in testing, migration plans, and a deprecation period, plus a public OpenAPI spec repo and REST reference with an interactive explorer, indicating a mature versioned/documented API lifecycle. Missing for 10: independent third-party corroboration of deprecation policy adherence over time and explicit API version numbering scheme details.

   • [claimed-docs] “the API itself will also alert you of upcoming changes. Shortly after we post communication, the API will begin sending Asana-Change headers…”
   • [claimed-docs] “you can test out how the API will behave by sending additional headers in your requests. Sending an Asana-Enable header including comma-sepa…”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”

   proof ↗⚑ flag

4. ai-native userThe documented API rate limits and concurrency caps before building automation at scale

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's developer docs explicitly publish per-auth-type rate limits (API key, OAuth, unauthenticated), leaky-bucket refill behavior, complexity limits, and rate-limit response headers, giving AI-native builders concrete numbers to design automation around. Missing for 10: explicit documented concurrency caps (max simultaneous requests/connections) beyond hourly request quotas, and no independent/hands-on confirmation that these limits hold in practice at scale.

   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear API supports personal API keys and OAuth2 authentication.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack covers Asana's REST API, OpenAPI spec, deprecation policy, and developer sandbox, but nothing addresses documented rate limits or concurrency caps for API usage. Since no citation speaks to this specific axis, it cannot be credited even though it's a fair question for an API platform.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Linear's GraphQL API, SDK, and webhook system (linear-docs-49,53,51) provide the technical means to script bulk changes across issues, and there's a documented bulk import capability (linear-docs-47). However, there is no explicit documentation of a dedicated bulk-edit UI, batch mutation endpoints, or AI-agent-driven bulk operation workflow across many items at once. missing for 10: explicit bulk-edit/multi-select UI docs, batch/bulk GraphQL mutations, and any agent or automation example operating on multiple items simultaneously.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “Import data from other services into Linear”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence describes single-task creation via the API, rule-based automation, webhooks, and AI Studio workflows, but nowhere mentions a bulk/batch endpoint or the ability to update many items in one call as an AI-native user. Missing for 10: explicit bulk/batch API operations, multi-item update endpoints, or documented bulk action support.

   ⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event (e.g., initiative/project/cycle changes), with concrete examples like auto-updating docs or posting Slack messages when a target date changes. This is reinforced by webhook support for event-driven automation via the API. Missing for 10: independent/hands-on corroboration beyond vendor docs, and detail on the breadth of definable trigger conditions/rules.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”

   proof ↗⚑ flag

   Asana✓fullclaimed7/10

   Asana's native Rules engine plus 'rule actions, webhooks, and API' explicitly supports trigger-based automation on events, and AI Studio adds no-code automations layered on top, with app components allowing custom logic to plug into rules. Missing for 10: independent hands-on verification of AI-native rule-building via API/agent, and detail on the range of triggerable events/conditions.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature is explicitly designed for recurring agent workflows: users describe a job and choose to run it 'on a schedule or in response to an event,' with examples like auto-updating launch plans and posting Slack updates when project dates change. Docs also show loops can be shared as team-wide skills and pinned/favorited for ongoing use, covering both scheduling and workflow automation depth. Missing for 10: independent/hands-on confirmation that scheduled loops reliably trigger as configured, and technical detail on scheduling granularity or failure handling.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
   • [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
   • [claimed-docs] “You can now add a loop to Favorites”

   proof ↗⚑ flag

   Asana~partialclaimed4/10

   Asana's platform docs show general automation via rules, webhooks, API, and AI Studio's no-code automations, which could support recurring workflows, but no evidence explicitly describes scheduling or recurring job triggers (e.g., time-based rule triggers). Missing for 10: explicit documentation of recurring/scheduled triggers, cron-like automation, or examples of automating tasks on a recurring schedule.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Linear
   Linear~partialclaimed4/10

   Linear offers general version history/checkpoint restore for work (linear-docs-35) and rich review tooling for agent-produced code changes (guided reviews, diff rendering — linear-docs-7, linear-docs-72), which partially satisfies the 'version, review, rollback' need for AI-generated work. However there is no evidence of version control, review, or rollback specifically for the automations/Loops themselves (the scheduled/event-driven workflows) — only their outputs (documents, code) get versioned. Missing for 10: explicit versioning of Loop/automation definitions, audit trail of automation changes, and a dedicated rollback mechanism for the automation logic itself rather than just its output artifacts.

   • [claimed-docs] “If you need to revert to an earlier version, restore to any previous checkpoint from version history.”
   • [claimed-docs] “Guided Reviews break diffs into focused sections with explainers on what changed and why.”
   • [claimed-docs] “Images, fonts, Markdown, and PDFs now render directly inside Linear diffs.”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence of version history, review workflows, or rollback capability for Asana rules/automations or AI Studio workflows; docs cover API deprecation headers and app components, not automation versioning/rollback. missing for 10: version history UI for rules/automations, diff/review workflow before publishing changes, rollback/restore to prior automation version.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Docs, "Deprecations" ("this page describes our deprecation process"): "We will provide a clear description of the change, how it affects you…”

   proof ↗⚑ flag

Ai task automation

1. ai-native userHave AI automatically triage and prioritize incoming bugs and tasks

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear docs explicitly describe AI-driven triage: incoming feedback/issues are 'instantly routed, labeled, and prioritized for the right team,' and Linear Agent can 'investigate and attempt a fix before it reaches an engineer,' plus a Priority tab surfaces what needs attention. These directly match the automatic triage/prioritization story. Missing for 10: independent/hands-on evidence validating triage accuracy or reliability beyond vendor changelog claims.

   • [claimed-docs] “Automatically turn conversations and customer feedback into actionable issues that are instantly routed, labeled, and prioritized for the ri…”
   • [claimed-docs] “When a new issue is reported, Linear Agent can investigate and attempt a fix before it reaches an engineer, reducing the load on your team.”
   • [claimed-docs] “The new Priority tab separates what needs your attention from what can wait, so something like a review blocking a release never gets buried…”

   proof ↗⚑ flag

   Asana~partialclaimed5/10

   Asana offers rule-based automation, webhooks/API, AI Studio no-code automations, and AI Teammates described as handling 'complex, coordination-heavy work' with shared memory and governance — these are generic building blocks that could be configured to triage/prioritize tasks, but no evidence explicitly documents a bug-triage or prioritization use case or template. Missing for 10: a concrete documented workflow or template showing AI classifying/prioritizing incoming bugs or tasks, independent/hands-on validation of such a workflow.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

2. ai-native userHave my in-app AI assistant learn my tone, shorthand, and preferences to tailor its output

   weight 1 · round to Asana
   Linear—none0/10

   Evidence shows Linear Agent can draft updates, edit text, and run automated 'Loops', but nothing describes it learning an individual user's tone, shorthand, or personal preferences to tailor future outputs — personalization/memory of style is never mentioned.

   ⚑ flag

   Asana~partialclaimed4/10

   Asana's AI Teammates feature claims 'shared memory' where 'every piece of feedback, every preference gets carried forward,' which loosely maps to personalization, but there's no specific evidence of learning tone, shorthand, or writing style, nor any hands-on validation of this personalization actually working. missing for 10: evidence of tone/style/shorthand learning specifically, first-party detail on how preference adaptation works mechanically, and independent corroboration that AI output actually reflects user's individual style.

   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”

   proof ↗⚑ flag

Workflow automation

1. engineerAuto-generate a changelog for each release so shipping progress is easy to review

   weight 1 · round to Linear
   Linear✓fullclaimed7/10

   Linear explicitly documents an auto-generate release notes option in pipeline settings, directly matching the story of auto-generating a changelog per release. missing for 10: no detail on customization/format of generated changelogs, no independent/hands-on corroboration beyond the single changelog entry.

   • [claimed-docs] “Choose to auto-generate release notes in pipeline settings so your changelog is always up to date.”

   proof ↗⚑ flag

   Asana—none0/10

   Asana is a project/task management tool, not a code repository or CI/CD system; nothing in the evidence shows any feature for generating release changelogs from commits, PRs, or version tags. While Asana has APIs, rules, and automation features, none are documented as producing changelogs tied to releases.

   ⚑ flag

2. product managerBuild multi-step automations without writing code

   weight 2 · round to Linear
   Linear✓fullclaimed7/10

   Linear's 'Loops' feature lets users describe a recurring job in plain language and choose a schedule or event trigger, with multi-step behavior like updating documents and posting Slack messages when conditions change—exactly a no-code automation builder usable by a PM. Additional context (skills, agent-based investigation/monitoring) reinforces no-code configurability. missing for 10: independent/hands-on evidence of a PM successfully building complex branching automations, and detail on conditional/branching logic depth

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Build agents that can investigate incidents, monitor SLAs, or analyze customer feedback.”
   • [claimed-docs] “We now support sharing skills with your team so great personal workflows can become shared team process.”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Asana explicitly markets 'AI Studio – Powerful no-code automations' and references 'rule actions' as part of its automation platform, directly supporting a PM building multi-step automations without code. However, the evidence pack lacks deeper documentation (e.g., a rules builder walkthrough, examples of multi-step conditional logic, or independent hands-on validation) beyond marketing taglines. missing for 10: detailed no-code rule-builder documentation/tutorial, independent user validation of multi-step automation building.

   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”

   proof ↗⚑ flag

3. engineerBuild trigger-and-action automation rules to eliminate repetitive manual steps

   weight 3 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, automating recurring work like updating docs, posting Slack messages, or monitoring initiatives — a direct trigger-and-action automation capability, further extensible via webhooks and the GraphQL API for custom automations. missing for 10: independent/hands-on verification of Loops reliability at scale, and more detail on the breadth of available trigger/action types beyond the examples shown.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Evidence confirms Asana has a rule-based automation surface ("rule actions", app components built on the surface of "rules", and AI Studio's no-code automations) that lets engineers/users automate repetitive steps, and the API/webhooks can be combined with rules for custom triggers. However, the pack lacks first-party documentation detailing the actual trigger types, conditions, or multi-step rule builder UI, so the story is only partially evidenced. Missing for 10: dedicated Rules-builder documentation showing trigger/condition/action configuration, and independent/hands-on confirmation of building such rules.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”

   proof ↗⚑ flag

4. engineerCreate a workflow that runs on a schedule or recurring event to handle routine team work

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Loops' feature explicitly lets users describe a job in plain language and choose to run it on a schedule or in response to an event, targeting recurring team work like weekly planning, doc updates, or launch plan syncing (linear-docs-11, linear-docs-36, linear-docs-23, linear-docs-95, linear-docs-96, linear-docs-100). This directly matches the story of scheduled/recurring workflow automation for routine team tasks. missing for 10: independent/hands-on verification of Loops reliability and no detail on error handling or monitoring of scheduled runs.

   • [claimed-docs] “Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.”
   • [claimed-docs] “Loops are a new way for Linear Agent to take on recurring work for your team. Describe the job in plain language and then choose whether it …”
   • [claimed-docs] “Sharing a skill helps your team standardize recurring workflows like writing specs, running weekly planning, or drafting updates.”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “a loop can automatically update the launch plan and post a Slack message explaining what changed, why, and who needs to act”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”

   proof ↗⚑ flag

   Asana~partialclaimed4/10

   Asana's docs reference rule-based automation ('rule actions, webhooks, and our API') and AI Studio's 'no-code automations,' suggesting engineers can build workflow automations, but no evidence explicitly documents a schedule/time-based or recurring-event trigger mechanism for these workflows. Missing for 10: explicit documentation of scheduled/cron-like or recurring-event triggers in Rules or AI Studio, and any hands-on/independent confirmation that such scheduled automations work reliably.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”

   proof ↗⚑ flag

5. ai-native userWhat happens—extra charges, throttling, or a hard stop—when I exceed my plan's automation or API call limits

   weight 3 · round to Linear
   Linear~partialclaimed6/10

   Linear's docs publish exact per-auth-type API rate limits, response headers (e.g. X-RateLimit-Requests-Limit) and a leaky-bucket refill model, and separately allow admins to set spend limits for AI agent/automation usage that reset periodically — together these give a user real visibility into automation/API limits. However, the pack doesn't explicitly spell out the concrete consequence of exceeding a limit (e.g. exact 429 throttling behavior, whether overages incur extra charges, or a hard stop for automation/Loops usage), so the full 'what happens when I exceed' picture is only partially documented. Missing for 10: explicit statement of throttling/error response code, confirmation of no/optional overage billing, and documented consequence for exceeding automation (Loops/agent) usage specifically rather than just spend caps.

   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”
   • [claimed-docs] “Admins can also set workspace-wide and per-user spend limits that reset daily, weekly, or monthly.”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence describes rate limits, throttling behavior, overage charges, or hard stops for exceeding automation/API quotas; docs cover deprecations, sandbox, and API basics but not usage limits or their consequences.

   ⚑ flag

Cross tool sync

1. designerKeep project status updated from my design tool without switching apps

   weight 2 · round to Asana
   Linear—none0/10

   The evidence pack shows Linear's API, webhooks, GraphQL SDK, and general integrations (GitHub, Slack, Okta) but contains no mention of a Figma or other design-tool plugin/integration that lets designers update project status without leaving their design tool. Missing for 10: any Figma/design-tool plugin, any documented design-tool-to-Linear status sync, or third-party evidence of such a workflow.

   ⚑ flag

   Asana~partialclaimed3/10

   Asana's API, webhooks, and App Directory (asana-docs-2, asana-docs-11) allow third-party apps to create/update tasks and status without leaving another tool, and app components let external apps surface inside the Asana UI (asana-docs-3/10/14), which is the general mechanism such a design-tool integration would use. However, there is no evidence of an actual Figma/Sketch/Adobe-type design tool integration or of status updates flowing specifically from a design tool into Asana project status. missing for 10: a named design-tool integration (e.g., Figma plugin) syncing project status, and any hands-on/community confirmation it works.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”

   proof ↗⚑ flag

Docs knowledge

1. product managerCreate and organize shared docs and notes alongside my project work

   weight 3 · round to Linear
   Linear~partialclaimed6/10

   Linear supports document creation and organization tied to projects/issues (teams can create documents from home page, add existing documents to projects/issues, group into sections, comment on docs, mobile doc editing) which covers shared docs alongside project work. However, evidence for cross-team/workspace-wide doc organization, folder hierarchies, or dedicated doc search/collaboration features (e.g. co-editing, version history for docs specifically) is thin. missing for 10: evidence of broader doc organization features (folders/wikis beyond project linkage), real-time co-editing, and independent user feedback confirming docs experience.

   • [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
   • [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”
   • [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
   • [claimed-docs] “Use callout components to draw attention to important information in issue and project descriptions, as well as documents.”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence in the pack shows a native Asana docs/notes feature for organizing shared documentation alongside project work; the docs and community items focus on tasks, API/dev platform, and AI Teammates, not a wiki/notes capability. One community comment even suggests a competing tool being compared lacks 'free form notes and wiki' relative to Asana/Trello, but nothing confirms Asana itself ships a shared-doc feature.

   • [community] “This seems to just be the boards and task lists without the free form notes and wiki? It pretty clearly replaces Trello and Asana.”

   proof ↗⚑ flag

In context discussion

1. engineerComment directly on specific text or images within an item's description

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear's own changelog explicitly states the exact capability: 'You can now comment directly on text or images in issue descriptions,' directly matching the story. missing for 10: no independent/hands-on corroboration beyond the vendor changelog entry.

   • [claimed-docs] “You can now comment directly on text or images in issue descriptions.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains only API/developer platform docs and general community sentiment; nothing describes inline commenting on specific text or images within a task/item description. Missing for 10: any documentation or hands-on evidence of annotation/inline commenting features on description text or embedded images.

   ⚑ flag

Real time sync

1. engineerSee teammates' changes reflected instantly across open sessions without refreshing

   weight 3 · round drawn
   Linear—none0/10

   The evidence pack contains no documentation or community reports describing real-time, no-refresh syncing of teammates' changes across open sessions (e.g., live cursors, instant issue updates, presence). References to webhooks (linear-docs-51/52) describe external HTTP push notifications for integrations, not in-app live UI updates, and speed-related comments (linear-comm-6) address load times, not multi-session sync.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of real-time UI sync, live presence, or websocket-based updates in Asana's interface — only API/webhook automation, developer sandbox, and AI Teammate features, none of which address instant cross-session UI updates for engineers viewing shared work.

   ⚑ flag

Team chat

1. engineerChat with my team directly inside the same tool I plan work in

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Linear supports asynchronous team collaboration via comments on issues, documents, and images (linear-docs-24, linear-docs-22) and @mentions (linear-docs-54), plus Slack integration for notifications (linear-docs-61, linear-docs-81), but there is no evidence of a native real-time chat/messaging feature inside Linear itself — collaboration is comment-based, not conversational chat. missing for 10: a dedicated in-app chat/messaging surface, evidence of synchronous team chat, and any first-party claim positioning Linear as a chat tool rather than relying on comments/Slack.

   • [claimed-docs] “You can now comment directly on text or images in issue descriptions.”
   • [claimed-docs] “Teams can create documents directly from their home page, add existing documents from projects and issues, and group resources into sections…”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
   • [claimed-docs] “Create issues from Slack messages and sync threads”

   proof ↗⚑ flag

   Asana—none0/10

   Asana's evidence pack covers task management, APIs, automations, and AI teammates, but nothing documents an in-app real-time chat/messaging feature for team communication; the closest mention (asana-comm-5) is a vague anecdote about using task comments instead of Slack, not a documented chat capability.

   • [community] “Asana has been around awhile and my team always used it for remote team communication and project management. We never saw the need for apps…”

   proof ↗⚑ flag

App ecosystem

1. engineerKeep tasks bi-directionally synced with my code repository's issue tracker instead of duplicating data

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear's changelog references GitHub-synced issues (opening them in GitHub) and syncing review requests/teams with GitHub, plus a public GraphQL API and webhooks that could be used to build two-way sync with an external tracker, but there is no explicit documentation describing full bi-directional field sync (status, description, comments) that eliminates duplicate data entry with a repo issue tracker. Missing for 10: explicit doc/feature description of two-way sync with GitHub Issues (not just PR/review linking), independent/hands-on confirmation that sync avoids duplication, and coverage beyond GitHub (e.g., GitLab).

   • [claimed-docs] “Open a GitHub-synced issue in GitHub with OG”
   • [claimed-docs] “You can now assign reviews to GitHub teams.”
   • [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “call the webhookCreate mutation with the teamId (or allPublicTeams: true) and url of your webhook”
   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence only shows generic Asana API/webhook/app-directory capabilities (e.g., asana-docs-2, asana-docs-11) that could be used to build custom sync, but there is no documentation of a specific, ready-made bi-directional sync with a code repository issue tracker (e.g., GitHub/GitLab/Jira issues) that avoids data duplication. Without a named integration or sync workflow for this exact use case, this remains unevidenced.

   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

2. engineerSee my assigned tasks from multiple project management tools in one unified view

   weight 2 · round drawn
   Linear—none0/10

   Evidence shows Linear integrates with GitHub, Slack, Okta, and supports one-time data import from other services (linear-docs-47), but there is no evidence of a unified cross-tool task view aggregating assignments from multiple external project management tools (e.g., Jira, Asana) into one dashboard. Linear positions itself as a replacement for such tools rather than an aggregator.

   • [claimed-docs] “Import data from other services into Linear”

   proof ↗⚑ flag

   Asana—none0/10

   Evidence shows Asana's API/integrations let other apps create Asana tasks or embed components, but there is no evidence of a unified view that aggregates an engineer's assigned tasks from multiple different project-management tools (e.g., Jira, Trello) inside Asana itself. Missing for 10: any documentation of a cross-tool task aggregation/unified inbox feature, evidence of pulling in tasks from other PM tools, or a 'My Tasks' view spanning external systems.

   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

3. engineerConnect common tools like Slack, GitHub, and Google Drive natively

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear's integrations directory explicitly documents native Slack (create issues from Slack messages, sync threads, Slack notifications), GitHub (automate PR workflows, review code, sync issues, assign reviews to GitHub teams), and Google Drive-adjacent file referencing plus a broad app ecosystem (Figma, GitLab, Sentry, Datadog, Notion, etc.), backed by OAuth/API infrastructure for deeper connections. Missing for 10: explicit first-party documentation of a native Google Drive integration specifically (only general file/import references appear) and independent hands-on confirmation of these integrations' reliability.

   • [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
   • [claimed-docs] “Create issues from Slack messages and sync threads”
   • [claimed-docs] “You can now assign reviews to GitHub teams.”
   • [claimed-docs] “You can now assign reviews to GitHub teams. Review requests assigned to your GitHub teams appear in a dedicated section of the Reviews inbox…”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
   • [claimed-docs] “Learn how to reference a file in markdown content, or upload with the API”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”

   proof ↗⚑ flag

   Asana~partialclaimed4/10

   Asana's docs mention a broader integration ecosystem (App Directory apps, app components that 'plug directly into Asana UI', APIs/webhooks for building integrations), implying that tools can connect natively, but no evidence explicitly names Slack, GitHub, or Google Drive as first-party native integrations. Missing for 10: explicit documentation of native Slack/GitHub/Google Drive connectors, hands-on confirmation of their functionality, and any independent corroboration of these specific integrations working out-of-the-box.

   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

4. product managerConnect my workspace to thousands of third-party tools via an app marketplace

   weight 2 · round drawn
   Linear~partialclaimed6/10

   Linear ships a documented integrations/app directory (GitHub, Slack, Figma, Salesforce, Sentry, Datadog, Notion, Airbyte, Fivetran, Cursor, ChatGPT, Claude, Jira migration, etc.), an OAuth app creation flow, and admin-level third-party app approval controls, which together function like a marketplace for connecting external tools. However, the evidence shows a curated directory of a few dozen named integrations plus a general public GraphQL/OAuth API for building custom ones, not literally 'thousands' of pre-built marketplace apps as the story implies. Missing for 10: evidence of marketplace scale (thousands of listed apps), a searchable public app store UI, and independent confirmation of ecosystem breadth beyond Linear's own docs.

   • [claimed-docs] “Connect GitHub to automate PR workflows, review code in Linear, sync issues and understand your codebase with Linear Agent”
   • [claimed-docs] “Create issues from Slack messages and sync threads”
   • [claimed-docs] “Create and link issues directly from Figma”
   • [claimed-docs] “Automate your Merge Request workflow”
   • [claimed-docs] “Build custom dashboards and analytics from issue and project data”
   • [claimed-docs] “Delegate issues to Codex directly from Linear”
   • [claimed-docs] “Turn issues into pull requests with Cursor cloud agents”
   • [claimed-docs] “Automate work from issue to tested PR with Devin”
   • [claimed-docs] “Create Linear issues from Datadog Cases and Monitors”
   • [claimed-docs] “Smoothly transition from Jira to Linear”
   • [claimed-docs] “Sync your Linear data with the Fivetran connector”
   • [claimed-docs] “Create Linear issues from Salesforce cases”
   • [claimed-docs] “Connect Linear to Airbyte and consolidate data in data warehouses, lakes, and databases”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”
   • [claimed-docs] “Use URL parameters to send users directly to a pre-filled Create OAuth App form in Linear. An equivalent JSON manifest format lets you store…”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Asana docs confirm an 'App Directory' with many third-party apps that create tasks and kick off workflows, plus a public REST API, webhooks, and app components for building custom integrations, which together support a marketplace-style ecosystem. However, no evidence quantifies the marketplace size ('thousands of tools') or shows a browsable marketplace UI/listing, and no independent/community source corroborates breadth of integrations. missing for 10: concrete count/scale of App Directory listings, independent hands-on evidence of marketplace breadth, and marketplace browsing/install UX documentation.

   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

Extensibility

1. designerBuild custom views and dashboard widgets that feel native to the product

   weight 1 · round to Asana
   Linear—none0/10

   Evidence only shows saved/shareable filtered views (linear-docs-13) and standard issue/project views — there is no SDK, embed framework, or dashboard-widget builder that would let a designer create custom native-feeling widgets or dashboards. The public API/webhooks/SDK docs (linear-docs-49-53) are developer-facing data access, not a UI customization surface for designers.

   ⚑ flag

   Asana~partialclaimed5/10

   Asana's developer docs describe 'app components' that let third-party apps plug directly into the Asana UI on the surface of tasks or rules, which supports building native-feeling integrations, but the story's specific asks—custom views and dashboard widgets—are not evidenced; only task/rule surface extensions are documented, with no dedicated widget/dashboard SDK or design guidelines mentioned. Missing for 10: explicit dashboard widget support, custom view builder APIs, design system/UI kit guidance, and independent/hands-on confirmation from designers building such components.

   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components. Build app components on the surface of tasks or rules so that customers can us…”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components.”

   proof ↗⚑ flag

Getting started

1. product managerThat exporting my workspace preserves full history—comments, attachments, and audit trails—not just task titles

   weight 3 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of a workspace export feature at all—only import tooling (from other services into Linear) is documented, with nothing about exporting comments, attachments, or audit trails out of Linear. This is a fair question for a project-management tool, so absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “Import data from other services into Linear”
   • [claimed-docs] “Import tooling for uploading from other systems”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence pack item addresses workspace export functionality, let alone preservation of comments, attachments, or audit trails during export; docs focus on API, automation, and AI Teammates instead.

   ⚑ flag

2. engineerFollow a guided walkthrough to set up my workspace the first time

   weight 1 · round drawn
   Linear—none0/10

   No evidence describes an onboarding wizard, guided workspace setup, or first-run tutorial for new engineers; the pack covers agents, integrations, API docs, and changelog features but nothing about initial workspace configuration guidance.

   ⚑ flag

   Asana—none0/10

   The evidence pack covers Asana's developer API, OpenAPI specs, MCP server, and general community sentiment about product quality, but contains no mention of a guided onboarding walkthrough or setup wizard for new workspace users. Missing for 10: any documentation of an in-app guided setup flow, first-run wizard, or onboarding checklist for engineers configuring a new Asana workspace.

   ⚑ flag

3. product managerImport my data from another tool when switching over

   weight 2 · round to Linear
   Linear✓fullclaimed6/10

   Linear documents explicit import capabilities: generic 'Import data from other services into Linear' plus a dedicated Jira migration flow ('Smoothly transition from Jira to Linear') and import tooling for uploading from other systems mentioned in the repo README. This directly satisfies the PM's need to migrate data when switching tools, though detail is thin — missing for 10: specifics on which tools/formats are supported, what data (comments, attachments, custom fields) is preserved, and independent/community confirmation that migrations work smoothly in practice.

   • [claimed-docs] “Import data from other services into Linear”
   • [claimed-docs] “Import tooling for uploading from other systems”
   • [claimed-docs] “Smoothly transition from Jira to Linear”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence describes an import/migration feature for bringing data from other tools (e.g., CSV import, Trello/Jira migration wizards); the pack only covers API access, app directory integrations, and AI teammates, none of which constitute a documented data-import capability for onboarding.

   ⚑ flag

4. product managerJumpstart a new project using pre-built templates

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of pre-built project or issue templates for jumpstarting new projects; the closest feature, the 'project composer' with Linear Agent, is AI-assisted drafting rather than a template library. missing for 10: any documentation of a templates gallery, template selection UI, or first-party/community evidence of template-based project creation.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of Asana's project templates or template galleries for jumpstarting new projects; all docs entries focus on API, integrations, and AI Teammates. missing for 10: any documentation or community evidence of pre-built project templates, template gallery, or template creation workflow.

   ⚑ flag

Pricing transparency

1. product managerWhether my plan enforces a minimum seat count or annual billing commitment before I subscribe

   weight 3 · round drawn
   Linear—none0/10

   No evidence in the pack addresses pricing plans, seat minimums, or annual billing commitments for Linear's subscription plans; all evidence relates to product features, API, and integrations. Missing for 10: any pricing page or plan documentation disclosing seat minimums, billing cadence, or contract terms.

   ⚑ flag

   Asana—none0/10

   No evidence in the pack addresses Asana's pricing plans, minimum seat requirements, or annual billing commitments; all evidence concerns API/developer docs and general community sentiment.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Linear
   Linear~partialclaimed7/10

   Linear's GraphQL API exposes the same schema used internally to build the app, with full introspection, mutations for issues/projects/comments, webhooks, OAuth2/API key auth, and an SDK, covering most core CRUD and workflow operations (linear-docs-49, linear-supp-graphql-introspection, linear-docs-74, linear-docs-92-93). However, several UI-native features (Agent sessions/Loops orchestration nuances, admin spend limits, Okta/SSO provisioning, third-party app approval flows, mobile-specific review UI) are not clearly exposed as API-first operations, and no independent evidence confirms 1:1 parity between UI and API surfaces. missing for 10: explicit documentation/confirmation that all admin/security settings (SSO, spend limits, app approvals) and newer Agent/Loop features are fully API-controllable, plus independent verification of full UI-API parity.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “query Issue { issue(id: "BLA-123") { id title description } }”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Linear provides webhooks which allow you to receive HTTP push notifications whenever data is created, updated or removed.”
   • [claimed-docs] “Linear supports OAuth2 authentication, which is recommended if you're building applications to integrate with Linear.”
   • [claimed-docs] “Docs, "Rate limiting" publishes exact per-auth limits ("API key — 2,500 requests per User per 1 hour; OAuth App — 5,000 per User; Unauthenti…”

   proof ↗⚑ flag

   Asana~partialclaimed6/10

   Asana's REST API is comprehensive and well-documented (CRUD on tasks, projects, webhooks, app components, OpenAPI spec, sandbox, explorer), covering most core workflow actions available in the UI. However there's no evidence that newer AI-native surfaces (AI Studio, AI Teammates/Dash) or all UI-specific features are fully exposed via the same API, so full UI/API parity isn't demonstrated. missing for 10: explicit confirmation that AI Studio/Teammates features and all UI settings/admin controls are API-accessible, independent verification of full parity.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Automate tedious work in powerful, bespoke ways with our platform features like rule actions, webhooks, and our API.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Each API endpoint features a built-in, in-context API explorer through which you can make requests (and see responses).”
   • [claimed-docs] “A developer sandbox is a temporary Asana domain with limited users.”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”
   • [claimed-docs] “Plug your app directly into the Asana UI with app components . Build app components on the surface of tasks or rules”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Linear~partialcommunity4/10

   Linear has no documented one-click 'export all data' feature; however, its open GraphQL API (with full schema introspection, SDK, and reasonable rate limits) lets a technical user programmatically pull out all their issues, projects, and comments, which is a de facto exit path. There's no bulk-export or archive format documented, and community confirms no self-hosting option, meaning a full clean 'leave with your data' workflow is not officially supported. missing for 10: a documented bulk/archival export feature (e.g., JSON/CSV dump), official data-portability tooling, and independent confirmation that a full account export actually works.

   • [claimed-docs] “Linear's public API is built using GraphQL. It's the same API we use internally for developing our applications.”
   • [claimed-docs] “Docs, "Getting started": "Linear's GraphQL endpoint is: https://api.linear.app/graphql — It supports introspection so you can query the whol…”
   • [claimed-docs] “Docs, "Getting Started": "Our GraphQL API is explorable and queryable via Apollo Studio (studio.apollographql.com/public/Linear-API), no dow…”
   • [claimed-docs] “The Linear Typescript SDK exposes the Linear GraphQL schema through strongly typed models and operations.”
   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   Asana~partialclaimed4/10

   Asana's REST API returns JSON, an open format, so data could in principle be pulled out via API calls (asana-docs-15), and OpenAPI specs are published for structured access (asana-supp-openapi-spec). However, there is no documented dedicated bulk-export/full-account-export feature, no CSV/backup tool, and no explicit data-portability policy in the evidence pack. Missing for 10: a documented full-data export/backup mechanism, guarantees of completeness, and independent confirmation that users can fully migrate away using this API.

   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”
   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Linear—none0/10

   No evidence indicates Linear's application source is published under an open license; the only related item is a stray README reference on GitHub (linear-docs-101) which does not establish an open-source license or full source availability. Linear is a closed, proprietary SaaS product per all other evidence (docs, integrations, community threads about lack of self-hosting).

   • [claimed-docs] “Import tooling for uploading from other systems”
   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   Asana—none0/10

   Asana is a closed, proprietary SaaS product; the only public repo referenced (Asana/openapi) contains API specification files, not the product's actual source code, and no evidence indicates any open-license release of Asana's codebase.

   • [claimed-docs] “Official Asana/openapi repo, "Asana's OpenAPI Specifications": "This repository contains the OpenAPI Specification for Asana's APIs", publis…”
   • [claimed-docs] “To build (i.e., update) the OpenAPI specifications for the REST API (./defs/asana_oas.yaml) and for app components”

   proof ↗⚑ flag

Mobile access

1. engineerManage my tasks from a full-featured native mobile app without missing desktop functionality

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Docs show mobile app supports specific engineer workflows like reviewing code diffs and commenting (linear-docs-6) and, as of a recent update, document creation/editing (linear-docs-71), indicating mobile parity is being actively built out rather than already complete. There is no evidence of full task-management parity (e.g., initiatives, project views, filters, admin settings) on mobile, and no independent/community confirmation of a full-featured mobile experience. Missing for 10: comprehensive mobile feature-parity documentation covering all core desktop workflows (initiatives, filters, admin, integrations), and independent user reviews confirming no functionality gaps on mobile.

   • [claimed-docs] “Use the Linear mobile app to review code changes, comment on specific lines, and iterate with Linear Agent.”
   • [claimed-docs] “Document creation and editing are now available in Linear's iOS and Android apps.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no mentions of a native mobile app, mobile feature parity, or any mobile-specific capability—only API, developer platform, AI features, and general community sentiment about the web app's performance. Absence of evidence for this applicable axis (mobile apps are a plausible feature for a task/project management SaaS) means 'none'.

   ⚑ flag

Task management

1. product managerTrack cross-team dependencies to coordinate large launches

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear's initiative feature lets a team be assigned to lead cross-team work with statuses (proposed/canceled) and priority, which supports coordinating large launches (linear-docs-4, linear-docs-14, linear-docs-37, linear-docs-63, linear-docs-76), and project-view subscriptions notify on changes (linear-docs-61). However, there's no explicit evidence of dependency-specific features like blocking/blocked-by issue relations or a dependency graph across teams. missing for 10: explicit issue-to-issue dependency/blocking relation docs, cross-team dependency visualization, hands-on evidence of coordinating a large launch using these features.

   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of Asana's dependency-tracking, portfolios, or cross-team coordination features (e.g., task dependencies, portfolio views) that would support this story; documentation cited focuses on API access, integrations, and AI Teammates rather than planning/tracking capabilities like dependency management.

   ⚑ flag

2. product managerCustomize fields and workflow statuses to match my team's process

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no vendor documentation describing custom issue fields or configurable workflow statuses for teams; the only relevant community evidence explicitly states Linear lacks the ability to define different issue types or add custom fields, and describes this as a deliberate design choice against Jira-style customization.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains only API/developer-platform docs, AI teammate features, and community sentiment about UI/performance — none of it addresses custom fields or configurable workflow statuses, which is the actual subject of this story. Although this is a fair and expected capability for a work-management product like Asana, no evidence in the pack demonstrates it.

   ⚑ flag

3. product managerTrack initiatives with status, priority, and an owning team

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear docs show initiatives support status (Proposed/canceled/other statuses), priority, and an owning team assignment ('assign a team to lead an initiative'), directly matching the story. missing for 10: independent hands-on corroboration of the initiative-tracking UI beyond changelog claims.

   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of Asana's Portfolios/Goals features, custom fields for status or priority, or team ownership assignment for initiatives — it is entirely focused on the developer API, AI Teammates/agents, and general community sentiment. Without evidence of initiative-level tracking with status, priority, and owning team, this capability cannot be credited.

   ⚑ flag

4. engineerPlan and manage sprints for agile software development

   weight 2 · round to Linear
   Linear~partialcommunity4/10

   Evidence shows Linear supports general agile planning artifacts—issues, priorities, initiatives, roadmaps, and project alignment (linear-docs-76, linear-docs-63, linear-docs-37)—and community comments confirm it functions as a fast issue tracker (linear-comm-1, linear-comm-6). However, the pack contains no direct evidence of Linear's sprint/cycle-specific features (e.g., cycle planning, sprint velocity, burndown, backlog grooming) that would confirm dedicated sprint management. Missing for 10: explicit documentation of Cycles/sprint creation, velocity tracking, sprint retrospectives, and backlog prioritization tools.

   • [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [community] “We've been using Linear for a couple months. It's kind of like Superhuman in that the primary benefit is hotkeys. Otherwise it is an issue t…”
   • [community] “Can't speak for other teams... but we migrated from JIRA to Linear for our small team, and haven't looked back. Just the simple fact that it…”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of sprint boards, backlogs, story points, or agile/scrum-specific features in Asana; it focuses on API/developer platform capabilities and AI agent features. Community comments only compare Asana's general UI to Jira without confirming sprint-planning functionality, and some users note Asana lacks features that PMs/engineers need versus Jira for dev workflows.

   • [community] “I've found Asana to be a much, much nicer product to work with than Jira (at least as a developer, not sure about from the management side.)…”
   • [community] “While better than Jira in UI, I haven't been able to like Asana as a product for some reason. In my previous company we moved away from Asan…”
   • [community] “i remember reading about asana on here years ago. wasn't it supposed to be the thing that saved us from JIRA but ended up turning into the v…”

   proof ↗⚑ flag

5. engineerCreate tasks and assign them to teammates with due dates

   weight 3 · round to Asana
   Linear~partialcommunity4/10

   Evidence confirms issue creation (IssueCreate mutation) and assignment (assignedIssues, agents 'delegated issues through assignment') as core API/product capabilities, implying basic task creation and assignment support, but no evidence pack item explicitly documents setting or displaying due dates on issues. Missing for 10: explicit documentation of a due-date field on issues, UI walkthrough of assigning a task with a due date, and independent confirmation of this specific workflow.

   • [claimed-docs] “mutation IssueCreate { issueCreate( input: { title: "New exception" ...”
   • [claimed-docs] “const myIssues = await me.assignedIssues();”
   • [claimed-docs] “Agents behave similar to other users in a workspace. They can be @mentioned, delegated issues through assignment, create and reply to commen…”
   • [community] “I have used Linear on a couple of my hobby projects and it's a great tool to quickly capture features and bugs. My one gripe... is that the …”

   proof ↗⚑ flag

   Asana~partialclaimed5/10

   Docs confirm Asana supports creating tasks via UI/API (asana-docs-1, asana-docs-11, asana-docs-15) and that third-party apps can create tasks and kick off workflows, but the evidence pack never explicitly documents the assignee or due-date fields on a task object. Missing for 10: explicit documentation of assignee and due-date task fields, and independent hands-on confirmation of assigning tasks with due dates.

   • [claimed-docs] “Learn to create and authorize with a token then create tasks via the API.”
   • [claimed-docs] “Many apps in our App Directory create Asana tasks and kick start workflow from other tools.”
   • [claimed-docs] “The Asana API is a RESTful interface with predictable resource-oriented URLs, accepts JSON or form-encoded requests, returns JSON”

   proof ↗⚑ flag

6. engineerBreak work into subtasks and link dependent tasks so blocking order is clear

   weight 3 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of sub-issues, issue hierarchies, or blocking/blocked-by dependency links—core planning-tracking features one would expect docs to cover for an issue tracker. Nothing here cites Linear's sub-issue or relation functionality, so this applicable axis is unsupported by the given evidence.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains no documentation or community evidence describing Asana's subtask creation or task dependency/blocking-order features—it is entirely focused on API/developer platform capabilities, AI teammates, and unrelated community sentiment about UI/performance/Jira comparisons. Absence of evidence for this applicable, mainstream planning capability yields 'none'.

   ⚑ flag

7. engineerLog time directly against tasks and projects

   weight 2 · round drawn
   Linear—none0/10

   No evidence in the pack mentions time tracking, time logging, or timesheet functionality against tasks/projects in Linear; the evidence focuses on issue tracking, agents, coding sessions, and planning features.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of time-tracking or time-logging features against tasks/projects in Asana; it covers API, automation, AI teammates, and app components, none of which address engineer time logging.

   ⚑ flag

Views organization

1. engineerHow the product performs and whether item caps apply in workspaces with tens of thousands of tasks

   weight 2 · round drawn
   Linear—none0/10

   No evidence pack item addresses performance benchmarks, scalability limits, or item caps for workspaces with tens of thousands of tasks; community comments only mention general speed vs Jira without scale specifics. This is a fair question for an issue tracker but remains unaddressed here.

   ⚑ flag

   Asana—none0/10

   No vendor documentation addresses item caps, workspace size limits, or performance characteristics at scale (tens of thousands of tasks); the evidence pack only contains generic API/AI-feature docs and anecdotal community complaints about poor performance (e.g., 'worst performing web app', suspected O(n^2) algorithms) with no concrete data or documented limits. This is an applicable engineering concern for a task-tracking tool, but no first-party or independent source quantifies scaling behavior or caps.

   • [community] “The funny thing is that Asana is possibly the worst performing web app out of all the ones I use on a regular basis. I have a strong suspici…”
   • [community] “i dont understand why you would even listen to them, their website is such a piece of shit- terrible performance, terrible ui. maybe their i…”

   proof ↗⚑ flag

2. engineerSwitch between board, list, calendar, and timeline views of the same work

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack has no mention of board, list, calendar, or timeline views, or of switching between them — only a generic reference to sharing 'any filtered view' via URL, which doesn't establish this specific multi-view capability.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of Asana's board, list, calendar, or timeline views or any ability to switch between them—only API/developer platform docs and general community sentiment about the product. This is a fair axis for a work-management tool, but no evidence supports it here.

   ⚑ flag

3. engineerSave a filtered view of work and share it with a link

   weight 2 · round to Linear
   Linear✓fullclaimed9/10

   Linear explicitly documents saving/sharing filtered views: "You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop" (linear-docs-13), directly matching the story of sharing a filtered work view via link. Missing for 10: independent/hands-on community confirmation of this specific feature beyond the vendor changelog.

   • [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence in the pack addresses saved/filtered views, custom fields/search filters, or shareable links to such views in Asana; the evidence is entirely about API, AI teammates, and general sentiment.

   ⚑ flag

4. engineerSearch across all tasks, docs, and comments and get fast, accurate results

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no documentation or community commentary about a search feature spanning issues, docs, and comments, nor any claims about speed or accuracy of such search — only filtering/view-sharing and speed-of-loading tickets are mentioned, which is a different capability.

   ⚑ flag

   Asana—none0/10

   The evidence pack contains no mention of Asana's search feature across tasks, docs, and comments, nor any data on search speed or accuracy; it only covers API access, automations, AI teammates, and general product sentiment unrelated to search. This is a fair axis for a planning/tracking tool, but no supporting evidence exists.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Linear—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Linear workspaces; only unrelated features (access control via Okta, admin app approvals, self-hosting explicitly denied) are covered.

   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
   • [community] “I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the clou…”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence in the pack discusses data residency, regional storage options, or data locality controls for Asana; the pack covers API/dev tooling and AI Teammates features only. missing for 10: any mention of region selection, data residency policy, or geographic storage controls.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Linear—none0/10

   No evidence in the pack addresses AI training data opt-out or any policy preventing customer data from being used to train AI models; the pack covers agents, integrations, API, and workspace features but is silent on AI training data usage policy.

   ⚑ flag

   Asana—none0/10

   No evidence pack item addresses AI training data opt-out, data usage policies for AI/ML model training, or any privacy controls specific to preventing data use in training. Evidence covers API docs, AI Teammates features, and general community sentiment, none of which touches this axis. Missing for 10: explicit documentation of an AI-training opt-out/opt-in setting, data processing terms addressing model training, and any admin control to restrict data use for AI training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack covers admin access control, identity management (Okta/SSO), API rate limits, and agent behavior, but contains no mention of data retention policies, data deletion controls, or configurable retention windows for AI-generated content or session data. Missing for 10: any documentation of retention periods, deletion/export APIs, or admin controls specifically for purging AI agent data or session history.

   ⚑ flag

   Asana—none0/10

   No evidence pack items address data retention policies, deletion controls, or data lifecycle management for AI features/agents; only general API, developer sandbox, and AI Teammate governance mentions (audit trail, permissions) are present, none of which describe retention/deletion controls.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Linear—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out settings for Linear; the material covers agents, integrations, API, and product features but nothing about privacy/telemetry controls. Missing for 10: any documentation of a telemetry setting, opt-out toggle, privacy policy statement, or usage-tracking disclosure.

   ⚑ flag

   Asana—none0/10

   No evidence pack items mention telemetry, usage tracking, opt-out settings, or privacy controls for AI features; the pack covers API/developer docs and general community sentiment only.

   ⚑ flag

Ai insights

1. ai-native userAsk AI a question and get an instant answer with citations from my workspace content

   weight 2 · round to Asana
   Linear—none0/10

   The evidence shows Linear Agent can draft updates by gathering context (e.g. 'Write with Agent' reviewing changes and Slack messages) and supports MCP integrations for external AI tools, but there is no documented feature where a user can directly ask a question and receive an instant answer with citations pulled from workspace content. This is a plausible axis for a workspace tool, but no such Q&A/citation feature is evidenced.

   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Connect ChatGPT deep research to Linear”
   • [claimed-docs] “Previews of Linear issues, views and projects and query Notion AI”

   proof ↗⚑ flag

   Asana~partialclaimed4/10

   Asana markets 'Asana Dash — Your AI Chief of Staff' and AI Teammates that draw context from the Work Graph and shared memory, suggesting an in-workspace Q&A assistant, but no evidence describes citation of specific workspace items in answers or an 'ask a question, get instant answer with citations' UX. Missing for 10: explicit documentation of citation/sourcing behavior in AI answers, hands-on or independent verification of accuracy/citations.

   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Pre-built AI agents that work alongside your team inside real workflows, with shared memory, governance, and context from the Work Graph, so…”
   • [claimed-docs] “Shared memory means AI Teammates learn from the work itself. Every completed task, every piece of feedback, every preference gets carried fo…”
   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

2. ai-native userHave AI draft a project or initiative status update from recent activity

   weight 2 · round to Linear
   Linear✓fullclaimed8/10

   Linear's 'Write with Agent' feature explicitly drafts project status updates by reviewing recent activity changes and linked Slack messages, and Loops can also react to initiative/project changes to keep documents and plans updated automatically. Missing for 10: independent/hands-on corroboration of update quality, and explicit first-party example of initiative-level (vs project-level) status update drafting.

   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you.”
   • [claimed-docs] “Instead of finding that context manually, click Write with Agent to let Linear do it for you. The agent reviews changes made since the last …”
   • [claimed-docs] “Loops are recurring agent workflows for teams. They now respond to more workspace activity, including changes to initiatives, projects, and …”
   • [claimed-docs] “When scope or timing changes, a loop can update the relevant Linear document so plans stay aligned.”
   • [claimed-docs] “When a project's target date changes, a loop can automatically update the launch plan and post a Slack message explaining what changed, why,…”
   • [claimed-docs] “You can now edit text with Linear Agent, and use Loops to keep docs and project descriptions up-to-date. Author name indicators let you chec…”

   proof ↗⚑ flag

   Asana~partialclaimed4/10

   Asana markets AI Teammates and 'Asana Dash - Your AI Chief of Staff' plus AI Studio automations that could plausibly draft updates from activity, and a developer tutorial exists for generating reports of status updates, but no evidence explicitly confirms an AI feature that drafts a project/initiative status update from recent activity. Missing for 10: a concrete first-party doc or demo showing AI-generated status update drafting, and independent/community confirmation it works as described.

   • [claimed-docs] “Asana Dash arrow-right icon Your AI Chief of Staff”
   • [claimed-docs] “Turn your team's collective expertise into custom AI Teammates built to handle the complex, coordination-heavy work that slows your team dow…”
   • [claimed-docs] “AI Studio arrow-right icon Powerful no-code automations”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

Dashboards

1. product managerBuild dashboards and widgets to report on project progress

   weight 2 · round to Asana
   Linear—none0/10

   The evidence pack covers Linear's agent/AI coding features, initiatives, teams, and API/webhooks extensively, but contains no mention of dashboard-building or configurable reporting widgets for tracking project progress. Filtered/shared views (linear-docs-13) and project view event subscriptions (linear-docs-61) are the closest hints, but neither describes a dashboard or widget system a PM could assemble for progress reporting.

   • [claimed-docs] “You can now share any filtered view by copying its URL from your browser, or by pressing ⌘/Ctrl Shift C on desktop.”
   • [claimed-docs] “Added ability to subscribe to events in project views and receive notifications in Inbox or Slack”
   • [community] “The killer missing feature for us is that we can't define different issue types... there's no way to show the issue layout as an expandable …”

   proof ↗⚑ flag

   Asana~partialclaimed3/10

   The evidence pack only shows API-level access to status updates for building custom reporting apps (asana-docs-4, asana-docs-9), not any native dashboard/widget-building UI for PMs to visualize project progress. Missing for 10: documentation of Asana's built-in Reporting/Dashboards or Portfolio charting features, native widget customization, and any hands-on evidence of PMs actually building such dashboards.

   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool.”
   • [claimed-docs] “Learn to read status updates from Asana and share them in another tool. This step-by-step tutorial, example app, and recipe will help you bu…”

   proof ↗⚑ flag

2. product managerRoll up progress across multiple projects into a single portfolio view

   weight 2 · round to Linear
   Linear~partialclaimed4/10

   Linear's Initiatives feature (grouping multiple projects under a lead team, with status like proposed/canceled and priority) points toward portfolio-style organization, but the evidence never explicitly describes progress roll-up (e.g., aggregated completion percentages or a dedicated portfolio dashboard) across projects. Missing for 10: explicit documentation of progress aggregation/visualization across projects, independent/hands-on confirmation of a portfolio view, and any reporting-specific UI details beyond initiative metadata.

   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work”
   • [claimed-docs] “You can now assign a team to lead an initiative, making it clear who is responsible for driving the work and how it contributes to the broad…”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside”
   • [claimed-docs] “Proposed and canceled statuses make it clear when an initiative is under consideration or has been intentionally set aside... Priority commu…”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
   • [claimed-docs] “Plan and navigate from idea to launch. Align your team with product initiatives, strategic roadmaps, and clear, up-to-date PRDs.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no documentation or references to Asana's Portfolios feature, cross-project rollups, or multi-project dashboards — only API/developer docs, AI teammate marketing, and unrelated community sentiment. Missing for 10: any docs-1 or product page describing portfolio creation, progress rollup, or multi-project status aggregation.

   ⚑ flag

Access control

1. product managerReview an admin audit log of actions taken across the workspace

   weight 2 · round drawn
   Linear—none0/10

   The evidence pack contains no mention of an admin audit log feature listing actions taken across the workspace; the only near-miss reference (linear-docs-59) discusses private teams enabling 'audits' as a use case, not an actual audit log capability. This is an applicable security/compliance axis for a workspace tool like Linear, but no evidence shows it delivers the capability.

   ⚑ flag

   Asana—none0/10

   The evidence only mentions an audit trail scoped to AI Teammate/agent actions (asana-docs-13), not a workspace-wide admin audit log of user actions that a product manager could review for security purposes; no docs on an Admin Console audit log feature are present.

   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

2. product managerAssign granular permissions and roles to control who can view or edit work

   weight 2 · round to Linear
   Linear~partialclaimed5/10

   Linear offers some access-control building blocks—private/restricted sub-teams and initiatives that limit visibility to team members (linear-docs-15, linear-docs-29, linear-docs-40, linear-docs-59), Okta-based identity and 'existing Linear permissions' management (linear-docs-5, linear-docs-60, linear-docs-67), and admin approval of third-party apps (linear-docs-73)—but there's no evidence of granular, role-based view/edit permission assignment at the issue or field level that a PM could configure themselves. Missing for 10: documented custom roles/permission levels, per-user or per-field view/edit controls, and any PM-facing UI for assigning such permissions beyond team membership.

   • [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
   • [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
   • [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”
   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
   • [claimed-docs] “Third-party app approvals are now available on paid Linear plans, allowing admins to review and approve apps before they're installed.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no documentation of Asana's actual user-level permission/role system (e.g., project privacy settings, member roles, task-level view/edit controls). The closest mention (asana-docs-13) is about governance of AI Teammates/agents, not human-user granular permissions, so it does not substantiate this story. Missing for 10: docs on project/task privacy settings, member role definitions (admin/editor/viewer), and any independent confirmation these controls work as described.

   • [claimed-docs] “Every agent has an identity, scoped permissions, an audit trail, and cost constraints, with data access, approved actions, and spend all man…”

   proof ↗⚑ flag

3. product managerCreate private sub-teams restricted to specific members

   weight 1 · round to Linear
   Linear✓fullclaimed9/10

   Linear's docs explicitly describe private sub-teams with restricted visibility options — 'Private to team members — the team is hidden, except to members directly invited to that sub-team' and 'Restricted to parent team members', directly matching the story of PM-created private sub-teams limited to specific members. Additional docs confirm these sub-teams can organize sensitive-data groups and that initiatives led by private teams stay confidential. Missing for 10: independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Private sub-teams organize groups that work together under one umbrella, like independent business units, skunkworks efforts, or teams handl…”
   • [claimed-docs] “Restricted to parent team members — parent team members can see and choose to join the sub-team... Private to team members — the team is hid…”
   • [claimed-docs] “For work that requires tighter access, initiatives led by private teams are only visible to team members.”
   • [claimed-docs] “initiatives led by private teams are only visible to team members. This creates a secure place for confidential planning, regulated projects…”

   proof ↗⚑ flag

   Asana—none0/10

   No evidence in the pack addresses Asana's team/sub-team structures, privacy settings, or member restrictions; all documentation focuses on API, developer tools, and AI features. This is an applicable axis for a work-management tool but is unevidenced here.

   ⚑ flag

4. engineerSecure organization access with SSO and SAML

   weight 3 · round to Linear
   Linear~partialclaimed7/10

   Linear's docs describe Okta-based identity verification and centralized access management for admins, indicating SSO support, and the MCP changelog confirms managing employee access via Okta-managed identity. However, none of the evidence explicitly mentions SAML configuration or enterprise SSO setup details, and there's no independent/hands-on confirmation of the feature working. Missing for 10: explicit SAML protocol documentation, broader SSO provider support beyond Okta, and independent verification of enforcement.

   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions.”
   • [claimed-docs] “Linear verifies their identity through Okta and applies their existing Linear permissions. Admins can manage access centrally”
   • [claimed-docs] “Linear's MCP now supports managing employee access through your existing Okta-managed identity.”
   • [claimed-docs] “Admins can manage access centrally, without requiring employees to sign in or authorize Linear individually.”

   proof ↗⚑ flag

   Asana—none0/10

   The evidence pack contains no documentation or claims about Asana supporting SSO or SAML for organization access; all docs are about the API, integrations, and AI features. The only tangential mention (asana-comm-4) discusses a competitor's free Azure AD SSO, not Asana's own SSO/SAML capability, and does not confirm Asana ships this feature.

   ⚑ flag

Trust reliability

1. product managerThe vendor's published uptime SLA and can check real-time incident status via a public status page

   weight 3 · round drawn
   Linear—none0/10

   No evidence pack item mentions a published uptime SLA or a public status page with real-time incident status; only unrelated docs, community sentiment, and API/agent features are provided. Missing for 10: any mention of an SLA commitment, a status page URL, or incident history/uptime reporting.

   ⚑ flag

   Asana—none0/10

   No evidence pack item mentions an SLA, uptime guarantee, or a public status page with real-time incident reporting; all developer docs focus on API usage, deprecations, and app components rather than platform reliability commitments.

   ⚑ flag

2. product managerThe vendor's documented support response times for each plan tier

   weight 2 · round drawn
   Linear—none0/10

   No evidence pack item mentions support response time SLAs or plan-tier support commitments; the pack covers product features, API, and agent capabilities but nothing about documented support response times per pricing tier.

   ⚑ flag

   Asana—none0/10

   No evidence in the pack references support response times, SLAs, or plan-tier support commitments; all documentation relates to API, integrations, and AI features.

   ⚑ flag