Capacities vs Poly

Agent access

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

   weight 2 · round to Poly
   Capacities✓fullprobed8/10

   A live probe confirms docs.capacities.io/llms.txt returns HTTP 200 with structured, agent-readable content describing Capacities' documentation, directly matching the story of pointing an agent at an llms.txt file; this is corroborated by the broader developer docs (MCP, API) being machine-consumable and openly hosted. Missing for 10: independent third-party confirmation that agents actually consume this llms.txt successfully in practice, and no explicit vendor statement promoting llms.txt as a first-class agent onboarding feature.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.capacities.io/llms.txt # Capacities Documentation > Documentation for Capacities, a note-taking an…”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”

   proof ↗⚑ flag

   Poly✓fullprobed9/10

   Poly directly serves an llms.txt with a full agent-oriented documentation index, confirmed live via runtime probe (HTTP 200, structured docs list, companion llms-full.txt, /raw/*.md mirrors of every page), explicitly designed for agent consumption alongside CLI and MCP integration docs. Missing for 10: no independent third-party report of an agent actually using llms.txt to onboard, only first-party docs and probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.poly.app/llms.txt # docs.poly.app > Poly documentation ## Documentation Sets - [docs.poly.app](h…”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”
   • [claimed-docs] “Import your existing files from Google Drive, Dropbox, iCloud, or your local machine.”

   proof ↗⚑ flag

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

   weight 2 · round to Poly
   Capacities~partialprobed3/10

   Capacities exposes a REST API with bearer/OAuth auth and a hosted MCP server (verified live with 401/OAuth challenge), which could be scripted from a CI pipeline to automate content creation/export, but there is no documented CLI, container image, or explicit 'headless mode' for running the app itself in automation contexts. Missing for 10: dedicated CI/headless-mode documentation, CLI or batch-automation examples, and independent evidence of the API being used in automated pipelines.

   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly~partialprobed4/10

   The `poly` CLI is explicitly described as 'scriptable from the terminal' (poly-docs-17) and supports commands like `poly search` (poly-docs-6), suggesting scriptable automation is possible, and the MCP server exists for programmatic agent access (poly-probe-rt-2). However, both the CLI and MCP server rely on browser-based OAuth authentication (poly-probe-rt-2), which is a significant barrier to headless/CI use, and there is no documentation of API keys, service accounts, or CI-specific setup for non-interactive automation. Missing for 10: documented headless/non-interactive auth method (API key or service token), explicit CI/automation examples or docs, evidence of running without a browser session.

   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Capacities—none0/10

   Evidence consistently shows Capacities exposes itself AS an MCP server (and its own chat-connector/API) so external AI clients (ChatGPT, Claude, custom agents) can connect TO Capacities — the reverse of this story, which asks whether Capacities can consume external MCP servers to use their tools. No documentation or probe shows Capacities' AI assistant/chat feature acting as an MCP client that plugs in third-party MCP servers.

   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
   • [claimed-docs] “Chat Connectors let you connect AI chat apps, like ChatGPT, Claude, Cursor, or Le Chat, to your Capacities space.”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly—none0/10

   All MCP-related evidence describes Poly exposing its own hosted MCP server (mcp.poly.app) for external AI assistants like Claude Code, Codex, ChatGPT, etc. to consume — i.e., Poly acting as the MCP *server* — not Poly acting as an MCP *client* that can plug in and use tools from third-party MCP servers. No documentation, CLI reference, or probe shows Poly's built-in agent connecting to or consuming external MCP servers.

   • [claimed-docs] “The Model Context Protocol (MCP) lets compatible AI assistants connect to Poly.”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “The official plugin loads your Poly memory when each session starts, teaches Claude how to use Poly, and connects the Poly MCP server.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

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

   weight 3 · round to Poly
   Capacities✓fullprobed8/10

   A runtime probe confirms a live, official hosted MCP server at https://api.capacities.io/mcp that responds with proper OAuth-protected-resource metadata and read/write scopes, and Capacities' developer docs explicitly document this MCP endpoint. This is genuine first-party server infrastructure an AI agent can connect to, not just a client-side integration guide. Missing for 10: independent/community confirmation of a successful agent connection in practice, and the docs text is inconsistently worded (framing it as building a 'custom MCP client' rather than clearly as 'our official server'), which adds minor ambiguity.

   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”

   proof ↗⚑ flag

   Poly✓fullprobed9/10

   Poly documents and runtime-verifies an official hosted MCP server (mcp.poly.app/mcp) with OAuth auth, exposing search/fetch/CLI tools, and it's usable from Claude Code, ChatGPT, Codex, Gemini, and other MCP clients. missing for 10: independent third-party (non-vendor) confirmation of a successful end-to-end agent connection beyond the probe and docs.

   • [claimed-docs] “The Model Context Protocol (MCP) lets compatible AI assistants connect to Poly.”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “The official plugin loads your Poly memory when each session starts, teaches Claude how to use Poly, and connects the Poly MCP server.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Poly
   Capacities—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Poly✓fullprobed8/10

   Poly ships a documented official CLI (`poly`) with 25+ commands for searching, reading, creating, and organizing files from the terminal, plus an agent-skill that composes CLI commands, confirmed by both docs and a runtime probe. missing for 10: independent/hands-on community verification of the CLI itself (community evidence discusses filesystem access concerns, not CLI usage) and no visible changelog/versioning depth for the CLI beyond docs.

   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [claimed-docs] “The [`poly-cli` agent skill] teaches an agent how to search, read, create, update, and organize your Poly files by composing `poly` commands…”
   • [probe] “official CLI documented at https://docs.poly.app/cli”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”

   proof ↗⚑ flag

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

   weight 3 · round to Capacities
   Capacities✓fullprobed9/10

   Capacities documents a REST API with Bearer-token OAuth authentication for accessing/creating/manipulating content, and this is independently verified by a runtime probe showing a live OpenAPI 3.1 spec at api.capacities.io and a correctly bearer-gated /spaces endpoint. It also exposes an official hosted MCP server (with OAuth-scoped read/write) confirmed live via probe, giving AI-native users multiple documented, working integration paths. Missing for 10: deeper endpoint-level documentation excerpts and independent third-party developer testimonials beyond the runtime probes.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”

   proof ↗⚑ flag

   Poly~partialprobed7/10

   Poly documents a CLI (`poly` with 25+ commands) and a hosted MCP server (https://mcp.poly.app/mcp with OAuth) that let AI agents and assistants drive file search, read, write, and organization programmatically, confirmed by both docs and a live runtime probe. However, there is no conventional public REST/OpenAPI API — probes for openapi.json/swagger.json all returned 404 — so agentic access is limited to MCP/CLI surfaces rather than a general-purpose documented API. missing for 10: a REST/OpenAPI-documented API, independent third-party corroboration of API usage beyond vendor docs.

   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”
   • [probe] “official CLI documented at https://docs.poly.app/cli”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

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

   weight 2 · round to Capacities
   Capacities~partialprobed5/10

   Capacities' API and MCP server use Bearer/OAuth 2.0 authentication, and the live MCP endpoint exposes discrete 'mcp:read' and 'mcp:write' scopes, showing some notion of least-privilege access. However, there is no documented mechanism for a user to generate multiple distinct API keys per-agent, restrict a token to specific spaces/objects, or revoke individual credentials independently. Missing for 10: docs on issuing/managing multiple scoped tokens, per-agent key rotation/revocation, and fine-grained resource-level permissions beyond read/write.

   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750)”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's MCP/agent integrations use a single OAuth login granting 'full access to your Poly files' (poly-docs-30, poly-docs-29) rather than any scoped or least-privilege credential/token mechanism; no docs mention granular permission scopes, read-only vs write tokens, or per-agent credential issuance. This axis is applicable (Poly ships agent/API integrations) but no evidence supports scoped credentialing — missing for 10: any documented scope/permission model, token-level restriction, or least-privilege API key issuance for agents.

   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [claimed-docs] “Give Claude Code persistent context and full access to your Poly files.”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Capacities
   Capacities~partialprobed7/10

   Capacities exposes a documented REST API with a verified live OpenAPI 3.1 spec and Bearer/OAuth authentication, plus an official hosted MCP server with live OAuth-gated endpoints — solid ground for building integrations. However, no dedicated client SDKs (e.g. Python/JS libraries) are evidenced, only the raw REST API and MCP protocol spec. Missing for 10: language-specific official SDK packages, code samples/quickstarts beyond raw API docs.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750)”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”

   proof ↗⚑ flag

   Poly—none0/10

   Evidence shows a CLI and an MCP server integration, but no official SDK (Python/JS/etc.) or API client library is documented; the OpenAPI probe returned 404s across all candidate paths, indicating no formal API spec developers could build an SDK against.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”
   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Capacities—none0/10

   Evidence shows Capacities has a REST API and MCP server for pull-based access, but no documentation or probe indicates any webhook subscription mechanism for event notifications.

   ⚑ flag

   Poly—none0/10

   No evidence of any webhook or event-subscription mechanism; Poly's integration surface is limited to MCP, CLI, and file sync, none of which describes outbound event notifications via webhooks.

   ⚑ flag

Agentic features

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

   weight 2 · round to Poly
   Capacities~partialclaimed6/10

   Capacities offers concrete in-app AI features—AI Chats with context, AI Property Auto-Fill, and AI Image Analysis (OCR, categorization)—that provide AI-generated insights/suggestions on user data, and these are opt-in with privacy controls. However, these are fairly narrow (chat, auto-fill, image analysis) rather than broader proactive insight generation like automated summaries, trend detection, or knowledge-graph-driven suggestions. Missing for 10: evidence of proactive/automated insight surfacing (e.g., suggested connections, summaries across notes), independent hands-on reviews validating quality of AI suggestions, and broader coverage beyond the three documented AI features.

   • [claimed-docs] “AI Property Auto-Fill: Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to au…”
   • [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
   • [claimed-docs] “AI Image Analysis: Analyze any image with one click. The AI extracts a title, description, text (OCR, including handwritten text), a color p…”
   • [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”

   proof ↗⚑ flag

   Poly✓fullprobed7/10

   Poly's docs describe natural-language search, an automatic 'second brain' memory layer, and an agent that can summarize, explain, and generate insights from indexed files (docs-2, docs-3, docs-31, docs-14), directly matching the AI-generated insights/suggestions story. Missing for 10: independent/hands-on evidence of proactive insight generation (vs. just search/summarize-on-request) and no third-party validation of insight quality beyond vendor docs.

   • [claimed-docs] “Search inside your files with natural language that's gives you results down to the exact timestamp, page, paragraph, or frame.”
   • [claimed-docs] “Poly automatically remembers key details, forming a "second brain" for you out of your files.”
   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [claimed-docs] “It automatically parses, transcribes, and indexes your files that make it up to 20x faster for an agent to read and understand them. Use our…”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”

   proof ↗⚑ flag

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

   weight 2 · round to Poly
   Capacities—none0/10

   Evidence shows only a scheduled full-export feature and API/MCP integration points for external clients, but nothing indicating autonomous, self-triggering background automations (e.g., workflows/triggers acting on data changes) running inside Capacities.

   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”

   proof ↗⚑ flag

   Poly~partialprobed5/10

   Poly's agent can perform multi-step file tasks, spawn subagents, and be invoked via CLI/MCP/plugins, but these are triggered interactively (chat requests, CLI commands, agent sessions) rather than described as scheduled or event-triggered background automations running autonomously without a user prompt. There's no documented scheduler, trigger system, or 'run this automatically every day/on file change' capability. missing for 10: explicit scheduling/trigger mechanism (cron-like, event-driven, or always-on background execution), evidence of automations persisting and running unattended over time, and independent confirmation of autonomous background operation.

   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress. Moreover, agents/subagents can communicate with each ot…”
   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [claimed-docs] “The official plugin loads your Poly memory when each session starts, teaches Claude how to use Poly, and connects the Poly MCP server.”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

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

   weight 3 · round to Poly
   Capacities~partialclaimed5/10

   Capacities ships a built-in AI assistant with AI Chats (pass blocks/notes as context), AI Property Auto-Fill, and AI Image Analysis, which are genuine in-app AI delegation features (opt-in, per capacities-docs-16/23/24/36). However, these are narrow, single-step assist functions rather than open-ended agentic task delegation (e.g., multi-step autonomous workflows or tool-use chains). Missing for 10: evidence of multi-step/autonomous task execution, any agent-like planning or tool invocation by the built-in assistant, and independent hands-on validation of these AI features' reliability.

   • [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
   • [claimed-docs] “AI Image Analysis: Analyze any image with one click. The AI extracts a title, description, text (OCR, including handwritten text), a color p…”
   • [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”

   proof ↗⚑ flag

   Poly✓fullprobed8/10

   Poly ships a built-in agent that can search, read, write, edit, and organize files across multiple steps (poly-docs-14, poly-docs-27, poly-docs-31), and can even spawn subagents to delegate subtasks (poly-docs-21, poly-docs-35), directly matching the story of delegating tasks to an in-product AI assistant. This is corroborated by runtime probes confirming a live agent/MCP infrastructure (poly-probe-rt-1, poly-probe-rt-2). Missing for 10: independent hands-on user reports specifically validating the agent's task execution (community commentary focuses on search/security concerns rather than confirming agentic task delegation in practice).

   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “The Poly agent can write and edit files directly in your storage.”
   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress. Moreover, agents/subagents can communicate with each ot…”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

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

   weight 2 · round to Poly
   Capacities~partialprobed5/10

   Capacities supports AI chats with context, AI property auto-fill, and connects to external AI assistants (ChatGPT, Claude, Cursor) via chat connectors and a live MCP server with read/write scopes, letting AI act as an intermediary for natural-language commands. However, there is no evidence of a native in-app natural-language command palette/interface where a user directly types free-form commands to control the app itself (e.g., 'create a project page and link it to my meeting notes') — the NL interaction is mediated through external AI tools/chat rather than a first-party built-in command layer. missing for 10: first-party in-app natural-language command interface, hands-on evidence of NL commands controlling core app actions (creating/organizing objects) rather than just chat/auto-fill, independent user reports validating this workflow.

   • [claimed-docs] “Chat Connectors let you connect AI chat apps, like ChatGPT, Claude, Cursor, or Le Chat, to your Capacities space.”
   • [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
   • [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [claimed-docs] “AI Property Auto-Fill: Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to au…”

   proof ↗⚑ flag

   Poly✓fullprobed8/10

   Poly's docs describe a built-in agent operable via natural language — searching, summarizing, editing, and organizing files with plain-language requests (poly-docs-2, poly-docs-31, poly-docs-14, poly-docs-27), plus a CLI and MCP-based integrations exposing the same commands to AI assistants. This directly matches the ai-native natural-language-command story. Missing for 10: independent/hands-on verification that NL commands work reliably in practice (community evidence only discusses trust/security concerns, not functional testing of NL command execution).

   • [claimed-docs] “Search inside your files with natural language that's gives you results down to the exact timestamp, page, paragraph, or frame.”
   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “The Poly agent can write and edit files directly in your storage.”
   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Capacities—none0/10

   Evidence confirms a REST API and a machine-readable OpenAPI 3.1 spec exist, but there is no sign of an interactive reference (e.g., Swagger/Redoc UI, try-it-now console, runnable code snippets) — docs are plain markdown reference pages and the openapi.json is only a raw spec file, not an interactive explorer.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.capacities.io/openapi.json, https://docs.capacities.io/swagger.json, https://docs.capac…”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”

   proof ↗⚑ flag

   Poly—none0/10

   The probe explicitly found no OpenAPI/Swagger spec at any candidate path, and the evidence pack contains no mention of an interactive API reference or runnable examples anywhere in Poly's docs or CLI/MCP materials.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to Capacities
   Capacities✓fullprobed8/10

   A live runtime probe confirms Capacities serves a genuine machine-readable OpenAPI 3.1.0 spec at https://api.capacities.io/openapi.json, paired with a working bearer-gated REST API, directly satisfying the story; the docs also describe the REST API and Bearer auth. missing for 10: an explicit documentation page linking to/download-able copy of the spec (the docs subdomain's openapi.json paths 404) and independent/community confirmation of the spec's existence.

   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.capacities.io/openapi.json, https://docs.capacities.io/swagger.json, https://docs.capac…”

   proof ↗⚑ flag

   Poly—none0/10

   A direct probe for OpenAPI/Swagger specs at all standard paths returned 404s, and no evidence pack item mentions a downloadable API spec; Poly instead documents an MCP server and CLI, not a machine-readable REST API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Capacities—none0/10

   Capacities' docs describe a production REST API and MCP server with bearer/OAuth auth, but there is no mention of a sandbox, staging, or test space that lets an AI-native developer experiment without touching real production data. Missing for 10: any documented sandbox/staging environment, test API keys, or a dedicated test space feature.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe direct agent read/write access to a user's real files, Drive/Dropbox imports, and MCP integrations, but nowhere mention a sandbox, staging, or test environment isolated from production data. Community comments even highlight anxiety about the agent having broad access to real files with no isolation layer. missing for 10: any documented sandbox/staging mode, test data set, or isolated environment separate from the user's live files.

   • [claimed-docs] “The Poly agent can write and edit files directly in your storage.”
   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [community] “Hooking up the Internet to my filesystem is scary. What security measures are in place to ensure a compromise of your infrastructure doesn't…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Capacities—none0/10

   Evidence confirms Capacities ships a REST API and MCP server, but nothing documents API version numbers, a versioning scheme, or a deprecation policy — the OpenAPI spec is even labeled 'Beta' with no stability guarantees mentioned.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”

   proof ↗⚑ flag

   Poly—none0/10

   No evidence of any versioned public API or documented deprecation policy — probes for OpenAPI/Swagger specs all returned 404, and docs only cover CLI/MCP/agent integrations, not API versioning or deprecation guarantees. missing for 10: versioned API reference, deprecation policy documentation, changelog/versioning scheme.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”

   proof ↗⚑ flag

Agent ops

1. ai-native userMy coding agent or assistant can read AND write my notes headlessly — through a documented local API, vendor API, or MCP server — without me touching the GUI

   weight 3 · round to Poly
   Capacities✓fullprobed8/10

   Capacities ships both a documented REST API (Bearer/OAuth authenticated, verified live with a 401 on keyless access) and an official hosted MCP server at api.capacities.io/mcp with confirmed read AND write scopes (mcp:read mcp:write), enabling headless agent read/write access without the GUI. missing for 10: independent third-party hands-on report of an agent actually using the MCP server end-to-end, and clearer documentation of write-operation specifics/limits in the API docs.

   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”

   proof ↗⚑ flag

   Poly✓fullprobed9/10

   Poly ships a documented hosted MCP server (mcp.poly.app) with OAuth, exposing search, fetch, and CLI-equivalent tools, plus a CLI/agent-skill that lets agents read, write, create, and organize files headlessly, and a Claude Code plugin that loads Poly memory and connects the MCP server automatically — all confirmed live via runtime probes. missing for 10: independent (non-vendor) hands-on confirmation that write operations via MCP work reliably in practice, beyond docs and probes.

   • [claimed-docs] “The Model Context Protocol (MCP) lets compatible AI assistants connect to Poly.”
   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “The official plugin loads your Poly memory when each session starts, teaches Claude how to use Poly, and connects the Poly MCP server.”
   • [claimed-docs] “The [`poly-cli` agent skill] teaches an agent how to search, read, create, update, and organize your Poly files by composing `poly` commands…”
   • [claimed-docs] “The Poly agent can write and edit files directly in your storage.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

Ai assist

1. ai-native userConnect external LLMs and AI tools to my notes through first-party connectors or an ecosystem of AI plugins

   weight 2 · round drawn
   Capacities✓fullprobed9/10

   Capacities ships first-party AI connectors (Chat Connectors for ChatGPT/Claude/Cursor/Le Chat), a documented and runtime-verified hosted MCP server with OAuth scopes, and a REST API confirmed live via OpenAPI probe, giving multiple first-party paths to connect external LLMs/tools to notes. Missing for 10: independent hands-on user reports specifically testing these connectors/MCP server in practice, and evidence of a broader third-party plugin ecosystem beyond the officially listed chat apps.

   • [claimed-docs] “Chat Connectors let you connect AI chat apps, like ChatGPT, Claude, Cursor, or Le Chat, to your Capacities space.”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”

   proof ↗⚑ flag

   Poly✓fullprobed9/10

   Poly ships a first-party MCP server (mcp.poly.app) with OAuth, documented and runtime-verified as live, plus official plugins/integrations for Claude, ChatGPT, Claude Code, VS Code, and a CLI usable by agents, giving AI-native users multiple first-party ways to connect external LLMs to their notes/files. missing for 10: no independent hands-on confirmation of the plugin ecosystem working smoothly beyond docs/probe, and community feedback raises unresolved trust/security concerns rather than functional failures.

   • [claimed-docs] “The Model Context Protocol (MCP) lets compatible AI assistants connect to Poly.”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “The official plugin loads your Poly memory when each session starts, teaches Claude how to use Poly, and connects the Poly MCP server.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [claimed-docs] “Give Claude Code persistent context and full access to your Poly files.”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-14): https://docs.poly.app/llms.txt served an agent-oriented docs index ('# docs.poly.app', with a companion…”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

2. ai-native userA built-in AI assistant can answer questions, summarize, and draft grounded in my own notes — with clear controls over what data it sees

   weight 2 · round to Capacities
   Capacities~partialclaimed7/10

   Docs confirm a built-in AI Chat that can be grounded on selected notes/blocks as context (capacities-docs-23), AI property auto-fill and image analysis (capacities-docs-24, docs-36), and explicit opt-in/data-sharing controls for AI features (capacities-docs-16). This covers Q&A and grounding-with-control well, but explicit 'summarize' and 'draft' capabilities aren't directly documented, only implied via chat/context features. missing for 10: explicit documentation of summarization/drafting workflows, independent/hands-on user validation of AI answer quality or grounding accuracy.

   • [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
   • [claimed-docs] “AI Image Analysis: Analyze any image with one click. The AI extracts a title, description, text (OCR, including handwritten text), a color p…”
   • [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”

   proof ↗⚑ flag

   Poly~partialcommunity5/10

   Poly's built-in agent clearly summarizes, explains, drafts, and edits notes grounded in the user's own files (poly-docs-31, poly-docs-14, poly-docs-27, poly-docs-3), and Mind/journaling gives a personal-notes corpus for it to draw on (poly-docs-12, poly-docs-26, poly-docs-32). However, evidence for granular controls over *what the assistant itself sees* is thin: docs describe the agent getting 'full access to your Poly files' (poly-docs-30) rather than scoped visibility, and the only access controls documented are sharing/revoke permissions for other people (poly-docs-9, poly-docs-33), not data-scoping for the AI itself — a gap community users flag as a trust concern (poly-comm-2, poly-comm-4). Missing for 10: explicit per-folder/file visibility toggles or exclusion settings for the assistant, and independent confirmation that such controls work as intended.

   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “The Poly agent can write and edit files directly in your storage.”
   • [claimed-docs] “Poly automatically remembers key details, forming a "second brain" for you out of your files.”
   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Give Claude Code persistent context and full access to your Poly files.”
   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it.”
   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it. You stay the owner,…”
   • [community] “Hooking up the Internet to my filesystem is scary. What security measures are in place to ensure a compromise of your infrastructure doesn't…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”

   proof ↗⚑ flag

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

   weight 2 · round to Poly
   Capacities—none0/10

   The evidence shows a REST API and MCP server for programmatic access, plus scheduled full exports and selective exports, but nothing documents a bulk/batch operation capability (e.g., batch API endpoints, multi-select bulk edit/tag/delete across many items) that an AI agent could invoke at scale.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”

   proof ↗⚑ flag

   Poly~partialclaimed5/10

   Poly's CLI is described as 'scriptable from the terminal' (poly-docs-17) and the agent can chain multi-step tasks like 'organizing a folder' or spawning subagents to handle work in parallel (poly-docs-14, poly-docs-21, poly-docs-31, poly-docs-35), which implies some automation across sets of files, but there is no explicit documentation of a true bulk/batch operation (e.g., 'rename/tag/move N files at once') or a dedicated batch API/command. Missing for 10: an explicit bulk-operation example or batch command, evidence of scale (many items processed in one call), and independent/hands-on confirmation that automation reliably spans large item sets.

   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress.”
   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress. Moreover, agents/subagents can communicate with each ot…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Capacities—none0/10

   Capacities offers an API, MCP server, and AI assistant features, but no evidence of a rules/trigger engine (event-based automation like 'when X happens, do Y') exists in the docs pack—only manual actions, scheduled exports, and AI-assisted fill-in features are documented.

   ⚑ flag

   Poly—none0/10

   Poly's docs describe on-demand agent actions (search, summarize, edit, organize) and multi-step task execution, but there is no evidence of a rules/trigger system that fires actions automatically on defined events (e.g., file-added, schedule, webhook-based automation). Automation is user-initiated per request, not event-driven.

   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “Ask it to summarize, explain, or even edit your files. Automate tasks like organizing a folder.”
   • [claimed-docs] “Your agent can spawn its own subagents, assign them tasks, and track their progress.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Capacities—none0/10

   No evidence of any scheduling, cron-style triggers, or recurring workflow/automation capability aside from a manual 'automated full export' schedule which is not a general job/workflow scheduler; the API, MCP server, and AI features shown are all synchronous/manual, not recurring triggers for workflows.

   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe agent-driven task automation (multi-step tasks, subagents, organizing folders) but there is no mention of recurring/scheduled execution, cron-like triggers, or workflow scheduling anywhere in the evidence pack.

   ⚑ flag

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

   weight 1 · round to Poly
   Capacities—none0/10

   Capacities documents templates, an API, and an MCP server for integrations, but nothing in the evidence describes an automation-building feature (workflows/triggers/actions) let alone version history, review, or rollback for such automations.

   • [claimed-docs] “Templates allow you to prefill the content of an object- you can prefill properties and blocks in your objects.”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly~partialclaimed4/10

   Poly documents file-level version history and rollback (flashback mode, conflict-preserving recovery) that would cover changes made by its agent when it edits files, but there is no evidence of a first-class 'automation' object (e.g., saved workflows/skills) that can be versioned, reviewed, or rolled back as a unit — only raw file state is versioned. missing for 10: dedicated automation/workflow versioning UI, diff/review of agent actions before execution, rollback of multi-step agent tasks (not just files) as an atomic unit.

   • [claimed-docs] “Even conflicting edits are preserved, so you can recover any version of any file at any time.”
   • [claimed-docs] “Go into flashback mode at any time to see exactly what your files looked like at any point in the past, down to the millisecond.”
   • [claimed-docs] “The Poly agent can handle tasks that span multiple steps — reading, searching, writing, and organizing — in a single request.”
   • [claimed-docs] “The Poly agent can write and edit files directly in your storage.”

   proof ↗⚑ flag

Capture

1. researcherClip web pages, articles, and highlights from my browser straight into my notes with an official clipper or capture flow

   weight 2 · round drawn
   Capacities—none0/10

   No evidence pack item mentions a browser extension, web clipper, or article/highlight capture flow for Capacities; the closest features are generic content-type ingestion and a mobile app for 'capture on the go', not a browser clipper. This is a reasonable axis for a note-taking/knowledge-base app (competitors ship clippers), so absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “The mobile app is a companion to desktop for day-to-day work in your space: search and capture on the go.”
   • [claimed-docs] “Any image you input into Capacities becomes an image object, that can be reused anywhere in your space.”
   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe importing from Drive/Dropbox/iCloud/local files and from note apps like Notion/Obsidian/Evernote, but there is no mention of a browser extension, web clipper, or capture flow for saving web pages/articles/highlights directly into Poly. This is a fair capability for a 'second brain' note tool, so absence of evidence means it is not delivered.

   • [claimed-docs] “Import your existing files from Google Drive, Dropbox, iCloud, or your local machine.”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”

   proof ↗⚑ flag

Daily notes

1. power-userI get an automatic daily note for each day, pre-filled from a template, as the default landing place for journaling and capture

   weight 3 · round to Capacities
   Capacities~partialclaimed6/10

   Capacities docs confirm a native daily-note concept uniquely linked to each day for quick capture (capacities-docs-21) and a general templates feature that can pre-fill properties and blocks in objects (capacities-docs-9), and daily notes surface backlinked references automatically (capacities-docs-8). However, the docs never explicitly confirm that a template is auto-applied to the daily note by default or that the daily note is the default landing page/capture surface on app open. Missing for 10: explicit documentation of template-to-daily-note binding, and confirmation that the daily note is the default landing view.

   • [claimed-docs] “A daily note is a note that is uniquely linked to one day. It often serves as a quick and simple way to write down ideas or things to rememb…”
   • [claimed-docs] “Templates allow you to prefill the content of an object- you can prefill properties and blocks in your objects.”
   • [claimed-docs] “The next section shows all references of that day, including objects with properties to that day and mentions of the day in your writing.”

   proof ↗⚑ flag

   Poly~partialclaimed3/10

   Poly Mind's journaling feature provides a manual 'quiet place' to write daily thoughts and syncs entries as Markdown files, which loosely matches the capture/journaling theme, but there's no evidence of automatic daily note creation, template pre-fill, or it being the default landing screen. missing for 10: automatic daily note generation, template pre-fill mechanism, evidence of default-landing behavior on app open.

   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life. Write a few thoughts, attach files, or add the broader context behind a…”

   proof ↗⚑ flag

Editor

1. power-userDefine reusable templates (with variables like date and title) and apply them when creating recurring kinds of notes

   weight 2 · round to Capacities
   Capacities~partialclaimed6/10

   Capacities docs confirm a template system that lets you prefill properties and blocks of an object type, which supports reusable templates for recurring note kinds (e.g., Meetings, Projects) as suggested by the object-type-first workflow. However, no evidence describes dynamic variable insertion (e.g., auto-filled current date or title placeholders) within templates. Missing for 10: explicit documentation of variable/placeholder support (date, title, etc.) in templates and independent hands-on confirmation of this behavior.

   • [claimed-docs] “Templates allow you to prefill the content of an object- you can prefill properties and blocks in your objects.”
   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
   • [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's Mind/journaling docs describe creating markdown journal entries and importing notes, but there is no evidence of a reusable template system with variables (date, title) for recurring note types.

   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life. Write a few thoughts, attach files, or add the broader context behind a…”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”

   proof ↗⚑ flag

2. power-userWrite and format notes with headings, callouts, tables, code blocks, and embedded media in a fast keyboard-driven editor

   weight 2 · round to Poly
   Capacities—none0/10

   The evidence pack covers linking, templates, object types, and AI features but never documents core editor formatting elements (headings, callouts, tables, code blocks) or keyboard-driven editing speed/shortcuts, so this applicable power-user capability has no supporting evidence.

   ⚑ flag

   Poly~partialclaimed3/10

   Poly supports Markdown-based journaling (auto-synced .md files in the Mind folder) and offers Vim keybindings for file editing, suggesting some keyboard-driven text editing capability, but there is no documentation of rich formatting elements like callouts, tables, code blocks, or embedded media in a dedicated note editor. Missing for 10: explicit support for headings/callouts/tables/code blocks, embedded media, and any description of a fast dedicated editor UI beyond basic Markdown journaling.

   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Vim keybindings (enable in Settings)”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life. Write a few thoughts, attach files, or add the broader context behind a…”

   proof ↗⚑ flag

Migration

1. switcherExport my entire knowledge base at any time in open formats, so leaving is as easy as arriving

   weight 2 · round to Capacities
   Capacities✓fullclaimed7/10

   Capacities documents a native Full Export feature (Settings > Full Export) that can be run on demand or scheduled automatically, exporting content as Markdown with properties as front matter and collections as CSV files explicitly 'to reuse your content in other apps or work with it programmatically' — both open, portable formats satisfying a switcher's exit needs. Missing for 10: independent/hands-on verification of export completeness (media, attachments, block-references, backlinks fidelity) and confirmation this covers the entire space rather than only selected content in the documented flows.

   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
   • [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
   • [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”

   proof ↗⚑ flag

   Poly~partialclaimed4/10

   Poly stores files as real files that sync to a local Finder/Explorer folder (poly-docs-23) and journal entries are plain Markdown (poly-docs-12), implying your data always exists in accessible, mostly-original formats rather than a locked proprietary export. However, there is no explicit 'export my knowledge base' feature, bulk-export tool, or open-format guarantee for the indexed metadata/second-brain layer — only import pathways (poly-docs-1, poly-docs-22) are documented. Missing for 10: an explicit export/backup command or API, confirmation that indexed metadata (tags, memory, search index) can be exported, and any open-format guarantee beyond raw file sync.

   • [claimed-docs] “your Poly files appear as a real folder in Finder or Explorer, with files downloading on demand and syncing back automatically.”
   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Import your existing files from Google Drive, Dropbox, iCloud, or your local machine.”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”

   proof ↗⚑ flag

2. switcherImport my existing notes from Notion, Evernote, Roam, or plain Markdown with structure, links, and attachments preserved

   weight 3 · round to Poly
   Capacities~partialclaimed4/10

   Docs provide a detailed Notion-to-Capacities migration guide (curate structure, export as Markdown+CSV, define object types before import) which covers the Notion import path, but there is no evidence at all for importing from Evernote or Roam, and no confirmation that links/attachments are preserved on import (the export docs describe front matter/CSV output going out of Capacities, not import fidelity). missing for 10: Evernote import support, Roam import support, plain Markdown import instructions, explicit evidence that internal links/backlinks and attachments survive the import process, independent/hands-on reports confirming fidelity.

   • [claimed-docs] “Migrate from Notion by curating structure before export.”
   • [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
   • [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
   • [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”

   proof ↗⚑ flag

   Poly~partialclaimed5/10

   Poly's docs explicitly state you can 'bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more,' directly covering two of the four named sources, and general file import (Google Drive/Dropbox/local) plus native Markdown journal files supports plain Markdown ingestion. However, Roam is never explicitly named, and there is no documented detail on how structure, internal links, or attachments are preserved during the import process, nor any hands-on/community confirmation of import fidelity. Missing for 10: explicit Roam support, documented handling of internal links/structure/attachments during migration, independent corroboration of import fidelity.

   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”
   • [claimed-docs] “Import your existing files from Google Drive, Dropbox, iCloud, or your local machine.”
   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”

   proof ↗⚑ flag

Graph

1. researcherExplore my knowledge base as an interactive graph of notes and connections, filtered to what I care about

   weight 1 · round to Capacities
   Capacities~partialclaimed5/10

   Capacities has a documented Graph View that visualizes an object's links as a network showing the 'local neighbourhood' around the open note, which supports interactive graph exploration of the knowledge base. However, the evidence never describes any filtering mechanism (by tag, type, date, or search term) within the graph view itself, so the 'filtered to what I care about' part of the story is unevidenced. missing for 10: documented graph filtering/faceting by object type, tag, or search query, and any independent hands-on account of using filters in graph view.

   • [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph”
   • [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph, so you can see the local neighbourh…”
   • [claimed-docs] “All backlinks are grouped together at the bottom of your object in a section titled "Backlinks".”
   • [claimed-docs] “Capacities lets you link to individual blocks inside of an object, and reference them in other pages. We call this concept block-based linki…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe a 'second brain' with search, journaling, tagging, multiple folder views (Icon, Grid, Feed, Detail, Tree, etc.), and Notion/Obsidian import, but nowhere mention a graph visualization of notes/connections or filtering such a graph — this is a plausible axis for a notes/second-brain product but no evidence supports it.

   • [claimed-docs] “Poly automatically remembers key details, forming a "second brain" for you out of your files.”
   • [claimed-docs] “Eight ways to look at a folder — Icon, Grid, Feed, Detail, Tree, C”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”

   proof ↗⚑ flag

Links

1. researcherLink notes with [[wiki-style]] links and see every backlink and unlinked mention of a note in context

   weight 3 · round to Capacities
   Capacities~partialclaimed5/10

   Docs confirm backlinks are grouped in a dedicated 'Backlinks' section on each object and graph view shows links between notes, and daily notes show 'mentions of the day in your writing,' but there is no explicit mention of [[wiki-style]] link syntax or a general unlinked-mention detection feature across regular notes (only for daily notes). missing for 10: explicit [[wiki-link]] syntax documentation, a general unlinked-mentions panel for all object types, and independent/hands-on confirmation of in-context backlink previews.

   • [claimed-docs] “All backlinks are grouped together at the bottom of your object in a section titled "Backlinks".”
   • [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph”
   • [claimed-docs] “The next section shows all references of that day, including objects with properties to that day and mentions of the day in your writing.”
   • [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph, so you can see the local neighbourh…”
   • [claimed-docs] “A daily note is a note that is uniquely linked to one day. It often serves as a quick and simple way to write down ideas or things to rememb…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's 'Mind' feature supports journaling, importing notes from other PKM tools, and semantic search, but nothing in the evidence pack mentions [[wiki-style]] linking, backlink panels, or unlinked-mention detection — core PKM/wiki-linking features. Since Poly Mind explicitly targets note-taking/second-brain use cases, this axis is a fair question for the product, but no evidence shows it delivers wiki-links or backlinks.

   • [claimed-docs] “Poly automatically remembers key details, forming a "second brain" for you out of your files.”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life. Write a few thoughts, attach files, or add the broader context behind a…”

   proof ↗⚑ flag

2. power-userReference or transclude an individual block or section of one note inside another and have it stay in sync

   weight 2 · round to Capacities
   Capacities✓fullclaimed8/10

   Capacities explicitly supports block-based linking/embedding (block references) where an embedded block is identical to the original and edits propagate everywhere it's used, plus backlinks and graph view to surface these connections — directly matching the transclusion-stays-in-sync story. Missing for 10: independent hands-on verification of sync behavior across notes and any documented limits (e.g., section-level vs single-block granularity).

   • [claimed-docs] “Capacities lets you link to individual blocks inside of an object, and reference them in other pages.”
   • [claimed-docs] “Capacities lets you link to individual blocks inside of an object, and reference them in other pages. We call this concept block-based linki…”
   • [claimed-docs] “An embedded block is identical to the original. This means that any edits will occur in all places where this block is used.”
   • [claimed-docs] “All backlinks are grouped together at the bottom of your object in a section titled "Backlinks".”
   • [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph, so you can see the local neighbourh…”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe file search, an agent, a CLI/MCP integration, and a Markdown-based Mind/journal folder, but nothing in the evidence describes block- or section-level transclusion between notes that stays synced (no backlinks, embeds, or live-sync block references are mentioned anywhere in the docs pack).

   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life.”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life. Write a few thoughts, attach files, or add the broader context behind a…”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”

   proof ↗⚑ flag

Ownership

1. power-userMy notes live in local files or a local-first store that I own and can read without the app, and everything keeps working fully offline

   weight 3 · round to Capacities
   Capacities~partialclaimed5/10

   Capacities documents offline-first behavior (work offline, sync when back online, offline search) and a full/scheduled export to Markdown+CSV/front-matter that is 'easy to reuse... work with programmatically,' giving some data ownership. However, there is no evidence the primary store is plain local files usable without the app day-to-day — the live working format is the app's own sync/cloud store, and export is a periodic snapshot rather than the native storage format. Missing for 10: evidence of a genuine local-first primary file format (e.g. markdown files on disk that the app just syncs), and confirmation that full functionality (not just search) works offline without any cloud dependency.

   • [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “Search in Capacities is great for navigation, finding, and connecting your content. It works offline on all devices, giving you quick search…”
   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
   • [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
   • [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”

   proof ↗⚑ flag

   Poly!disputedcontradicted4/10

   Docs describe files/journal entries as real local files (synced Finder folder, Markdown notes in a 'Mind' folder), suggesting some local-first storage, but the core search/indexing/agent stack is cloud-hosted (remote MCP server at mcp.poly.app, OAuth-gated, server-side parsing/transcribing/indexing) — and a hands-on community reviewer explicitly notes 'your service, by nature, is reading and analyzing all of my files using a remote server,' directly contradicting a fully offline, locally-owned workflow. Missing for 10: no documentation of an offline mode, no evidence local files remain fully functional/searchable without the cloud service, and no rebuttal to the community's remote-dependency observation.

   • [claimed-docs] “your Poly files appear as a real folder in Finder or Explorer, with files downloading on demand and syncing back automatically.”
   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “It automatically parses, transcribes, and indexes your files that make it up to 20x faster for an agent to read and understand them.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”
   • [community] “It feels like an LLM wrapper in search of a problem. Cloud search plus already exists... I do not find the idea of bringing my data to your …”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

2. researcherMy notes are stored or exportable in open, documented formats (Markdown, JSON) so my archive outlives the vendor

   weight 2 · round to Capacities
   Capacities✓fullclaimed7/10

   Capacities documents a full, schedulable export to Markdown (with front matter) plus CSV for collections, explicitly stated to make content reusable in other apps or programmatically ('capacities-docs-11','capacities-docs-31'), alongside a REST API for direct data access ('capacities-docs-33'). This gives researchers a genuine open-format escape hatch beyond vendor lock-in. Missing for 10: independent/hands-on verification of export completeness and fidelity (e.g., whether all object types and block-links survive the export), and confirmation that the 'Full Export' truly captures the entire space rather than only selected/migration content.

   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
   • [claimed-docs] “Migrate from Notion by curating structure before export.”

   proof ↗⚑ flag

   Poly~partialclaimed5/10

   Poly's Mind journal entries are explicitly stored as plain Markdown files synced to a folder (poly-docs-12), and the desktop client exposes all Poly files as a real Finder/Explorer folder that syncs back automatically (poly-docs-23), so notes aren't locked in a proprietary blob. However there is no documented bulk-export feature, no JSON export format, and no explicit statement about long-term archival or vendor-independence beyond this folder-sync mechanism; import from other note apps (poly-docs-22) is one-way and does not evidence export-out portability. Missing for 10: explicit JSON/structured export option, a documented full-archive export or backup mechanism, and any statement guaranteeing data portability/format stability if the vendor shuts down.

   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “your Poly files appear as a real folder in Finder or Explorer, with files downloading on demand and syncing back automatically.”
   • [claimed-docs] “Bring existing notes and memory archives into Poly Mind from Notion, Obsidian, Evernote, Bear, and more.”

   proof ↗⚑ flag

Self host

1. developerRun the whole system without the vendor's cloud — local-only mode or a self-hosted sync backend I operate myself

   weight 2 · round drawn
   Capacities—none0/10

   Capacities is offline-first (local caching with sync) but all evidence shows sync and API/MCP endpoints run through the vendor's own cloud (api.capacities.io); there is no documented self-hosted sync backend or fully local-only mode without vendor infrastructure. Missing for 10: any option to self-host sync server, any documented local-only deployment mode, independent confirmation of running without vendor cloud.

   • [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”

   proof ↗⚑ flag

   Poly—none0/10

   All evidence points to Poly being a cloud-backed service (hosted MCP server at mcp.poly.app requiring OAuth login to Poly's cloud, cloud-based indexing/search) with no documented local-only mode or self-hosted sync backend option; community comments even complain that files/data must go through Poly's remote servers rather than staying local.

   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”
   • [community] “It feels like an LLM wrapper in search of a problem. Cloud search plus already exists... I do not find the idea of bringing my data to your …”

   proof ↗⚑ flag

Mobile

1. power-userFull-featured iOS and Android apps give me my whole knowledge base — capture, search, and linking — not a stripped-down companion

   weight 2 · round drawn
   Capacities—none0/10

   The only description of the mobile app in the evidence pack is Capacities' own docs stating it is 'a companion to desktop for day-to-day work... search and capture on the go' — this explicitly frames mobile as a stripped-down companion, not a full-featured app with linking/graph/backlinks parity, and no evidence shows block-based linking, graph view, or full object-type editing on iOS/Android. missing for 10: any documentation or reports of full linking/graph/template features on mobile, evidence that mobile isn't limited to search+capture, independent hands-on confirmation of mobile feature parity.

   • [claimed-docs] “The mobile app is a companion to desktop for day-to-day work in your space: search and capture on the go.”

   proof ↗⚑ flag

   Poly—none0/10

   Evidence pack extensively documents desktop, CLI, web/MCP, and Finder/Explorer integration, but contains no mention whatsoever of iOS or Android apps, mobile capture, or mobile search/linking capability. missing for 10: any evidence of iOS app, Android app, or mobile-specific capture/search/linking features.

   ⚑ flag

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

   weight 2 · round drawn
   Capacities~partialprobed5/10

   Capacities ships a documented REST API (with a live OpenAPI spec) and an official hosted MCP server with both read and write scopes, letting programmatic clients create/manipulate content and integrate agents — a real API-driven workflow, not just a UI. However, no evidence shows the API/MCP exposes UI-only features like AI property auto-fill, AI image analysis, chat connectors, graph view, or templates, so full UI-API parity is not demonstrated. Missing for 10: confirmation that AI assistant features, graph view, templates, and chat connector functionality are all reachable via API/MCP, and independent hands-on verification of API completeness.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”

   proof ↗⚑ flag

   Poly~partialprobed5/10

   Poly ships a scriptable CLI (25+ commands) and a hosted MCP server exposing search, fetch, and a virtual `poly` CLI as tools, giving programmatic access to core file search/read/write/organize workflows that mirror the UI's agent capabilities (poly-docs-17, poly-probe-rt-2, poly-probe-4). However there is no documented REST/OpenAPI API (openapi probes all 404'd), and no evidence that UI-only features like sharing/permissions management, the eight folder views, flashback/version history, or journaling are exposed programmatically. Missing for 10: a general-purpose REST/OpenAPI surface, API parity for sharing/permissions, version history, and Mind/journaling features.

   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “The [`poly-cli` agent skill] teaches an agent how to search, read, create, update, and organize your Poly files by composing `poly` commands…”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”
   • [probe] “official CLI documented at https://docs.poly.app/cli”
   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it.”
   • [claimed-docs] “Go into flashback mode at any time to see exactly what your files looked like at any point in the past, down to the millisecond.”

   proof ↗⚑ flag

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

   weight 3 · round to Capacities
   Capacities✓fullclaimed8/10

   Capacities offers full/selective export to open Markdown+CSV formats (front matter, CSV collections) explicitly designed for reuse in other apps or programmatic work, plus scheduled automated full exports, giving users a genuine 'export and leave' path. missing for 10: no independent/hands-on verification that exported data is fully lossless (e.g., all block references, embeds, graph links preserved) and no evidence of bulk data deletion/account closure workflow alongside export.

   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
   • [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”
   • [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”

   proof ↗⚑ flag

   Poly~partialclaimed4/10

   Poly's desktop sync exposes files as a real folder in Finder/Explorer with files kept in their original formats and synced back automatically (poly-docs-23), and journal entries are stored as plain Markdown files (poly-docs-12), which implies some natural portability rather than lock-in. However, there is no explicit documentation of a bulk 'export all data' feature, data-export API, or guarantee that a user can fully extract their indexed memory/context in open formats and leave — missing for 10: an explicit export/data-portability feature, documentation of exporting the 'second brain'/index data, and any mention of account deletion/data takeout.

   • [claimed-docs] “your Poly files appear as a real folder in Finder or Explorer, with files downloading on demand and syncing back automatically.”
   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”
   • [claimed-docs] “Finder tags sync bidirectionally with Poly tags, colors included.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Capacities—none0/10

   No evidence of Capacities' source code being open-licensed or publicly available; it is a closed, proprietary SaaS/app with a documented API and MCP server, but no open-source repository or license is mentioned anywhere in the evidence.

   ⚑ flag

   Poly—none0/10

   No evidence of any open-source license or public source repository for Poly; it appears to be a closed, proprietary SaaS/desktop product with only documentation and API/MCP endpoints disclosed. Missing for 10: any open-source license file, public code repository, or statement of source availability.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Capacities—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Poly—none0/10

   All evidence describes Poly as a hosted SaaS (cloud sync, hosted MCP endpoint at mcp.poly.app requiring OAuth, subscription-based) with no mention of a self-hosted or on-prem deployment option anywhere in the docs or probes.

   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [community] “This is really cool! I suck at organizing my filesystem and I've lost track of how many times I had to find that ONE PDF which I KNOW I have…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”

   proof ↗⚑ flag

Metadata

1. power-userAttach typed properties and tags to notes and use them consistently for organization and retrieval

   weight 2 · round to Capacities
   Capacities✓fullcommunity8/10

   Capacities is explicitly object-type-first, letting users define custom object types with typed properties (front-matter on export) and tags, with AI auto-fill for properties, and search/graph/backlinks for retrieval; a HN commenter corroborates that all content becomes taggable, reusable entities in a network of notes. missing for 10: independent hands-on validation of complex multi-property queries/filtering at scale and more detailed docs on tag hierarchies or property types beyond basic examples.

   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
   • [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself.”
   • [claimed-docs] “AI Property Auto-Fill: Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to au…”
   • [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
   • [claimed-docs] “Search in Capacities is designed to return useful results even when your wording is not exact.”
   • [claimed-docs] “Search in Capacities is great for navigation, finding, and connecting your content. It works offline on all devices, giving you quick search…”
   • [community] “Have been using it for a while now, there are really some cool new concepts... all media is automatically treated as an entity that can be r…”

   proof ↗⚑ flag

   Poly~partialclaimed4/10

   Poly documents tag support that syncs bidirectionally with Finder tags and colors, and search/retrieval features (natural language, visual similarity), but there is no evidence of 'typed properties' (structured metadata fields/schemas) or of consistent, structured tag-based retrieval workflows beyond basic color/tag sync. missing for 10: typed/structured property fields, evidence of consistent tag-based filtering or retrieval UI, cross-file property schemas.

   • [claimed-docs] “Finder tags sync bidirectionally with Poly tags, colors included.”
   • [claimed-docs] “Eight ways to look at a folder — Icon, Grid, Feed, Detail, Tree, C”
   • [claimed-docs] “Search inside your files with natural language that's gives you results down to the exact timestamp, page, paragraph, or frame.”

   proof ↗⚑ flag

Queries

1. power-userQuery my notes by their structured properties and render live database-style views (tables, boards, lists) from those queries

   weight 3 · round to Capacities
   Capacities~partialclaimed4/10

   Capacities clearly supports structured object types with custom properties (docs-26, docs-29, docs-35) and lists 'Smart queries' as a paid feature (docs-27), implying some query capability over properties, but there is no documentation describing table/board/list view rendering, filtering/sorting UI, or database-style views comparable to Notion databases. missing for 10: explicit documentation of query views (table/board/list), filter/sort UI, examples of rendering query results as live views.

   • [claimed-docs] “Task management, AI assistant, Calendar integrations, Smart queries, Task actions”
   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
   • [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself.”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe file search, tagging, journaling, and multiple folder 'views' (Icon, Grid, Feed, Detail, Tree, etc.) but there is no evidence of structured/custom properties on notes nor of live query-driven database views like tables or boards built from property filters — the 'eight ways to look at a folder' are display modes, not queryable schema-based views.

   • [claimed-docs] “Eight ways to look at a folder — Icon, Grid, Feed, Detail, Tree, C”
   • [claimed-docs] “Finder tags sync bidirectionally with Poly tags, colors included.”
   • [claimed-docs] “Search inside your files with natural language that's gives you results down to the exact timestamp, page, paragraph, or frame.”

   proof ↗⚑ flag

Search

1. researcherInstantly search all my notes with full-text search plus filters on tags, properties, and paths — including offline

   weight 3 · round to Capacities
   Capacities~partialclaimed6/10

   Docs confirm full-text search that works offline and tolerates inexact wording (capacities-docs-10, capacities-docs-22, capacities-docs-13, capacities-docs-37), and object types/tags/properties exist as structural concepts (capacities-docs-26, capacities-docs-35). However, no evidence documents explicit search filters/query syntax for tags, properties, or paths specifically. Missing for 10: documented filter syntax or UI for narrowing search by tag/property/path, independent hands-on confirmation of filtered search results.

   • [claimed-docs] “Search in Capacities is designed to return useful results even when your wording is not exact.”
   • [claimed-docs] “Search in Capacities is great for navigation, finding, and connecting your content. It works offline on all devices, giving you quick search…”
   • [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”

   proof ↗⚑ flag

   Poly~partialclaimed4/10

   Poly documents natural-language full-text search (down to timestamp/page/paragraph), a CLI 'poly search' command, visual similarity search, and Finder-tag syncing, but nowhere combines these into documented filter syntax on tags/properties/paths, nor claims search works offline (files instead 'download on demand' and sync back, implying online-first indexing). missing for 10: explicit support for combined tag/property/path filters in search queries, explicit documentation of offline full-text search capability.

   • [claimed-docs] “Search inside your files with natural language that's gives you results down to the exact timestamp, page, paragraph, or frame.”
   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [claimed-docs] “Visual similarity — find images that look like a reference image you provide”
   • [claimed-docs] “Finder tags sync bidirectionally with Poly tags, colors included.”
   • [claimed-docs] “your Poly files appear as a real folder in Finder or Explorer, with files downloading on demand and syncing back automatically.”

   proof ↗⚑ flag

Automation hooks

1. developerDrive the app from outside — create or open notes via a URI scheme, deep links, or a local endpoint — to wire it into my scripts and workflows

   weight 2 · round drawn
   Capacities~partialprobed6/10

   Capacities exposes a documented REST API (Bearer-auth, OpenAPI spec verified live) that lets developers create and manipulate content programmatically, which satisfies the 'local endpoint' part of the story for scripting/automation. However, there is no evidence of a URI scheme or deep-link mechanism for opening/creating notes from other apps, only a hosted (not local) API and MCP server. Missing for 10: documented URI scheme or deep-link support, evidence of a local (non-cloud) endpoint, and independent confirmation of scripting workflows beyond the API docs.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
   • [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750)”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”

   proof ↗⚑ flag

   Poly~partialprobed6/10

   Poly ships a scriptable `poly` CLI (poly-docs-6, poly-docs-17, poly-probe-4) and a local/hosted MCP endpoint (poly-docs-29, poly-probe-rt-2) that let external scripts search, read, and create/edit files including Mind journal notes, satisfying the 'local endpoint for workflows' part of the story. However there is no documented URI scheme or OS-level deep-link mechanism for opening/creating notes, only CLI/MCP paths. Missing for 10: URI scheme/deep-link support, explicit CLI subcommand for creating a note by title/URI, independent confirmation of CLI scripting reliability.

   • [claimed-docs] “poly search "the contract with the March deadline"”
   • [claimed-docs] “`poly` is Poly's command-line tool: your files, searchable and scriptable from the terminal.”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [probe] “official CLI documented at https://docs.poly.app/cli”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

Plugins

1. power-userBrowse and install from a large catalog of community plugins/extensions to add features the core app doesn't ship

   weight 3 · round drawn
   Capacities—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Poly—none0/10

   Evidence shows Poly ships its own integrations (CLI, MCP server, plugins for Claude/ChatGPT/VS Code) that let Poly connect into other tools, but there is no mention of a marketplace or catalog of third-party/community-built plugins that extend Poly itself with new features.

   • [claimed-docs] “Use our plugin with leading agents like Claude, ChatGPT, and VS Code and make your file workflows insanely fast.”
   • [claimed-docs] “The Model Context Protocol (MCP) lets compatible AI assistants connect to Poly.”
   • [claimed-docs] “Connect Poly to AI assistants and code editors with the local CLI first, then set up an MCP integration.”
   • [claimed-docs] “MCP clients can connect to `https://mcp.poly.app/mcp` (streamable HTTP). Authentication is OAuth: a browser window signs you into Poly on fi…”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”

   proof ↗⚑ flag

2. developerBuild my own plugins against a documented extension API/SDK with samples and developer docs

   weight 2 · round to Capacities
   Capacities~partialprobed5/10

   Capacities exposes a documented REST API (with OpenAPI spec, verified live) and an MCP integration standard for building external agents/bots/clients, which covers part of the 'extend Capacities programmatically' story, but there is no evidence of a true in-app plugin architecture/SDK, plugin samples, or a plugin marketplace — the docs describe API/MCP client integration rather than installable plugins running inside the product. missing for 10: dedicated plugin SDK/framework, code samples for building in-app plugins, plugin distribution/marketplace docs.

   • [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
   • [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
   • [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
   • [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”

   proof ↗⚑ flag

   Poly—none0/10

   Evidence shows Poly ships an MCP server, a CLI, and an agent-skill file for its own CLI, but nothing documents a first-party extension API/SDK for developers to build their own Poly plugins — the 'plugin' references are about installing Poly's plugin into other agents (Claude, ChatGPT, VS Code), not the reverse. A direct probe for an OpenAPI/Swagger spec returned 404 on all candidate paths, and no developer SDK, plugin manifest format, or extension samples are mentioned anywhere in the docs pack.

   • [claimed-docs] “Use our plugin with leading agents like Claude, ChatGPT, and VS Code and make your file workflows insanely fast.”
   • [claimed-docs] “It automatically parses, transcribes, and indexes your files that make it up to 20x faster for an agent to read and understand them. Use our…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.poly.app/openapi.json, https://docs.poly.app/swagger.json, https://docs.poly.app/api/op…”
   • [probe] “official CLI documented at https://docs.poly.app/cli”
   • [probe] “official MCP server documented at https://docs.poly.app/integrations/using-mcp”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Capacities—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or where user data is physically stored; docs cover offline-first sync and AI opt-in privacy but never data location choice. Missing for 10: any documentation of region/residency selection, server location options, or data hosting jurisdiction controls.

   • [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”

   proof ↗⚑ flag

   Poly—none0/10

   No evidence in the pack addresses data residency, region selection, or storage location choice for Poly's cloud-hosted service; documentation focuses on features, sync, and MCP/CLI integrations without any regional/residency controls. Missing for 10: any mention of data center regions, residency options, or compliance-driven storage location settings.

   ⚑ flag

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

   weight 3 · round to Capacities
   Capacities✓fullclaimed8/10

   Capacities explicitly documents that AI features are opt-in and that no data is shared with third-party AI services unless a user activates AI features, directly addressing the training-data-prevention story. missing for 10: no independent/third-party audit or hands-on verification of the no-training-data claim beyond vendor documentation.

   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”

   proof ↗⚑ flag

   Poly—none0/10

   No evidence in the pack of any data-training opt-out, privacy policy, or model-training exclusion commitment from Poly; docs focus on file search/agent features, not data-usage privacy controls. Community comments raise general trust/security concerns but don't confirm or deny a training-opt-out policy, so this is an unaddressed gap rather than a dispute.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Capacities—none0/10

   Evidence covers AI opt-in privacy (docs-16), offline/export features, and API auth, but there is no documentation of data retention policies, deletion controls, or account/data-deletion mechanisms specific to AI usage.

   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”

   proof ↗⚑ flag

   Poly—none0/10

   The evidence pack covers file import, search, sharing, versioning, and MCP/CLI integrations, but contains no documentation on data retention policies, permanent deletion, or export/purge controls for an AI-native privacy-conscious user. Community comments raise general trust/security concerns but don't confirm or deny specific retention/deletion mechanisms. missing for 10: retention policy docs, account/file deletion controls, data export or purge guarantees, any first-party statement on how long data is kept or how to fully erase it.

   • [claimed-docs] “Even conflicting edits are preserved, so you can recover any version of any file at any time.”
   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it. You stay the owner,…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”

   proof ↗⚑ flag

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

   weight 2 · round to Capacities
   Capacities~partialclaimed4/10

   Capacities docs state that AI features are fully opt-in and no space data is shared with third-party AI services unless activated, which gives users control over AI-related data sharing, but there is no evidence of a general telemetry/usage-analytics opt-out setting for the app itself. Missing for 10: explicit documentation of a general telemetry/analytics opt-out toggle, independent confirmation that the app collects no usage data when opted out.

   • [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”

   proof ↗⚑ flag

   Poly—none0/10

   No evidence in the pack addresses telemetry, analytics, or usage-tracking opt-out settings for Poly; the docs and community discussion cover file syncing, search, MCP integrations, and general privacy/security concerns about filesystem access, not telemetry controls.

   ⚑ flag

Publish

1. researcherPublish selected notes as a browsable website — a digital garden with working links — without leaving the app

   weight 2 · round drawn
   Capacities—none0/10

   No evidence of any public-publishing or website/digital-garden export feature; Capacities offers only view-only sharing access, local export to Markdown/CSV, and APIs/MCP for integrations, none of which produce a browsable public website with working links.

   • [claimed-docs] “Grant others view-only access to notes”
   • [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
   • [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's evidence covers sharing individual files/folders via links or team drives (poly-docs-9, poly-docs-24, poly-docs-33) and journaling/Mind notes storage, but there is no mention of publishing a collection of notes as a browsable, interlinked website (digital garden) with working cross-links. Sharing appears to be file/folder link-based, not a rendered site with navigable note-to-note links.

   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it.”
   • [claimed-docs] “Share individual files with a link, or give a team its own storage space.”
   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it. You stay the owner,…”
   • [claimed-docs] “Journaling gives you a quiet place to document your day-to-day life. Write a few thoughts, attach files, or add the broader context behind a…”

   proof ↗⚑ flag

Collaboration

1. researcherShare a vault or space with collaborators and edit notes together without stepping on each other's changes

   weight 2 · round to Poly
   Capacities~partialclaimed3/10

   The only sharing capability documented is view-only access to notes for others (capacities-docs-28), not true multi-user collaborative editing or conflict-free simultaneous editing of a shared vault/space. There is no evidence of real-time co-editing, presence indicators, or conflict resolution mechanisms that would let collaborators edit together without stepping on each other's changes. Missing for 10: real-time collaborative editing support, multi-editor conflict resolution, shared-space edit permissions beyond view-only, and any community/hands-on corroboration of team editing.

   • [claimed-docs] “Grant others view-only access to notes”

   proof ↗⚑ flag

   Poly~partialclaimed5/10

   Poly supports sharing files/folders and creating team Shared Drives with members and roles, and it preserves conflicting edits so any version can be recovered, which addresses collaborative access and non-destructive conflict handling. However, this is file-versioning-based (conflicts are preserved as separate recoverable versions, not merged live), with no evidence of real-time co-editing, presence awareness, or seamless merge like a true multiplayer notes app. Missing for 10: real-time simultaneous editing support, live presence/cursor indicators, and conflict-free merge (vs. version preservation) for concurrent note edits.

   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it.”
   • [claimed-docs] “Share a file or folder when the content belongs to you and you want specific people — or anyone with a link — to see it. You stay the owner,…”
   • [claimed-docs] “Create a Shared Drive when the content belongs to a team rather than to a person. A Shared Drive is its own storage space with its own membe…”
   • [claimed-docs] “Even conflicting edits are preserved, so you can recover any version of any file at any time.”
   • [claimed-docs] “Share individual files with a link, or give a team its own storage space.”

   proof ↗⚑ flag

Sync

1. power-userAn official sync service keeps my notes updated across all my devices with end-to-end encryption the vendor can't read

   weight 3 · round drawn
   Capacities—none0/10

   There is evidence of offline-first sync ('changes get synchronized as soon as you're back online') but no mention anywhere of end-to-end encryption of sync data or a vendor-can't-read architecture; encryption claims are absent from docs, pricing, or community sources.

   • [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
   • [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”

   proof ↗⚑ flag

   Poly—none0/10

   Poly's docs describe file sync (desktop folder sync, Finder tag sync, sharing, MCP/CLI integrations) but nowhere claim end-to-end encryption that the vendor itself cannot read; in fact the architecture explicitly routes files through Poly's servers for indexing/search, and community comments explicitly worry that Poly's remote servers read and analyze all files, contradicting the premise of vendor-blind E2EE. No evidence of an E2EE sync mechanism exists in the pack.

   • [claimed-docs] “your Poly files appear as a real folder in Finder or Explorer, with files downloading on demand and syncing back automatically.”
   • [claimed-docs] “Finder tags sync bidirectionally with Poly tags, colors included.”
   • [community] “Hooking up the Internet to my filesystem is scary. What security measures are in place to ensure a compromise of your infrastructure doesn't…”
   • [community] “With Google Drive, I choose which files to upload. It doesn't have broad access to everything on my computer... your service, by nature, is …”
   • [probe] “PROBE runtime (recorded 2026-09-14): keyless JSON-RPC initialize POST to Poly's hosted MCP server https://mcp.poly.app/mcp returned HTTP 401…”

   proof ↗⚑ flag

2. power-userView a note's version history and restore earlier versions or recover deleted notes

   weight 2 · round to Poly
   Capacities—none0/10

   No evidence anywhere in the pack of a version history feature or a way to recover deleted notes; documentation covers export, offline sync, linking, AI, and API but never mentions version history or trash/recovery.

   ⚑ flag

   Poly✓fullclaimed7/10

   Poly's docs explicitly describe file-level version history and recovery: 'flashback mode' lets you see exactly what files looked like at any past point, and edits/conflicts are preserved so 'you can recover any version of any file at any time' (poly-docs-5, poly-docs-10). Since notes (journal entries, Mind files) are just files synced in Poly, this recovery/versioning applies to them too. Missing for 10: no independent/hands-on verification of the restore UX specifically for notes, and no explicit mention of undeleting a note versus just reverting content.

   • [claimed-docs] “Go into flashback mode at any time to see exactly what your files looked like at any point in the past, down to the millisecond.”
   • [claimed-docs] “Even conflicting edits are preserved, so you can recover any version of any file at any time.”
   • [claimed-docs] “New journal entries are Markdown files synced to your **Mind** folder.”

   proof ↗⚑ flag