[
  {
    "@id": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/class/ontology"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/ontology",
    "https://atomicdata.dev/properties/shortname": "integrations-catalog",
    "https://atomicdata.dev/properties/description": "The plugin catalog for this repository's integrations: visibility flags and card copy per entry. The data-browser fetches this file at runtime from GitHub Pages (https://ontola.github.io/atomic-plugins/integrations/catalog.json by default, configurable in Settings > Integration), not from the connected server. At the pinned atomic-server it reads `shortname`, `experimental`, `enabled` and `requires-api-plugins` of every entry, to decide whether to offer the 'Show experimental plugins' toggle, and renders a card under 'Drive apps' only for an entry with `app-module` (name, emoji, description, version; see integrations/README.md, 'Publishing a drive app', and integrations/READINESS.md). Where `shortname` equals a package directory under integrations/ (money, notion, pets), the entry's `version` must equal that package's (integrations/README.md, 'Version and catalog entry'). Flip `experimental` to `false` once its package.json `atomicCertification.support` has left \"experimental\" — see integrations/README.md.",
    "https://atomicdata.dev/properties/classes": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/properties": [
      "https://atomicdata.dev/integrations/properties/experimental",
      "https://atomicdata.dev/integrations/properties/enabled",
      "https://atomicdata.dev/integrations/properties/capabilities",
      "https://atomicdata.dev/integrations/properties/events",
      "https://atomicdata.dev/integrations/properties/limitation",
      "https://atomicdata.dev/integrations/properties/keywords",
      "https://atomicdata.dev/integrations/properties/requires-api-plugins",
      "https://atomicdata.dev/integrations/properties/platform",
      "https://atomicdata.dev/integrations/properties/pluginUrl",
      "https://atomicdata.dev/integrations/properties/version",
      "https://atomicdata.dev/integrations/properties/app-module",
      "https://atomicdata.dev/integrations/properties/app-module-integrity",
      "https://atomicdata.dev/integrations/properties/app-row-name",
      "https://atomicdata.dev/integrations/properties/app-row-name-plural",
      "https://atomicdata.dev/integrations/properties/requires"
    ]
  },
  {
    "@id": "https://atomicdata.dev/integrations/classes/PluginCatalogEntry",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Class"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "plugin-catalog-entry",
    "https://atomicdata.dev/properties/description": "One integration's visibility gate and, for a bundled one, its card copy.",
    "https://atomicdata.dev/properties/requires": [
      "https://atomicdata.dev/properties/shortname",
      "https://atomicdata.dev/integrations/properties/experimental",
      "https://atomicdata.dev/integrations/properties/enabled"
    ],
    "https://atomicdata.dev/properties/recommends": [
      "https://atomicdata.dev/properties/name",
      "https://atomicdata.dev/properties/emoji",
      "https://atomicdata.dev/properties/description",
      "https://atomicdata.dev/integrations/properties/capabilities",
      "https://atomicdata.dev/integrations/properties/events",
      "https://atomicdata.dev/integrations/properties/limitation",
      "https://atomicdata.dev/integrations/properties/keywords",
      "https://atomicdata.dev/integrations/properties/requires-api-plugins",
      "https://atomicdata.dev/integrations/properties/platform",
      "https://atomicdata.dev/integrations/properties/pluginUrl",
      "https://atomicdata.dev/integrations/properties/version",
      "https://atomicdata.dev/integrations/properties/app-module",
      "https://atomicdata.dev/integrations/properties/app-module-integrity",
      "https://atomicdata.dev/integrations/properties/app-row-name",
      "https://atomicdata.dev/integrations/properties/app-row-name-plural",
      "https://atomicdata.dev/integrations/properties/requires"
    ]
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/experimental",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "experimental",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/boolean",
    "https://atomicdata.dev/properties/description": "True until this integration's advertised capabilities have current live evidence. An experimental entry is hidden from the Integrations page unless the visitor turns on 'Show experimental plugins'. Only meaningful when `enabled` is true."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/enabled",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "enabled",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/boolean",
    "https://atomicdata.dev/properties/description": "Whether this integration can be offered at all. False, same as omitting the entry entirely, means the Integrations page never offers it, even with 'Show experimental plugins' on."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/capabilities",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "capabilities",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "What this bundled integration's sync or import can actually do, shown on its Integrations page card."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/events",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "events",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "How and when this bundled integration exchanges data, shown on its Integrations page card."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/limitation",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "limitation",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "The supported scope and caveats, shown in the card's 'Supported scope' details."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/keywords",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "keywords",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "Extra space-separated search terms matched against the Integrations page search box, alongside name and description."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/requires-api-plugins",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "requires-api-plugins",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/boolean",
    "https://atomicdata.dev/properties/description": "True if this integration's card was meant to appear only once a visitor also enabled 'Show API plugins'. atomic-server removed that toggle with the LocalThought flow (c707ca4ed); at the pin, entries with this flag are not offered and do not count towards showing the 'Show experimental plugins' toggle."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/platform",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "platform",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "The integration-proxy platform id this integration connects through (for example `todoist`). Nothing reads it at the pin: its reader was the generic LocalThought setup dialog, which atomic-server removed with the LocalThought flow (c707ca4ed). Kept as a record of the provider the entry is for; a drive app names its platform in its own code when it calls `store.proxy.connect`."
  },
  {
    "https://atomicdata.dev/properties/localId": "calendar",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "calendar",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Google Calendar",
    "https://atomicdata.dev/properties/emoji": "🗓️",
    "https://atomicdata.dev/properties/description": "A drive app that imports one Google calendar's events and sends the edits you review back to Google.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Imports one calendar's single (non-recurring) events with title, description, location, start and end into the app's table, as rows of the shared Event class (event-v1, ontola/atomic-plugins#177), shown as an agenda and a week in the app and as a month through the table's own Calendar view, where all-day events spanning several days cover each of their days. Edits to those five fields are listed for review and sent to Google only when you approve them, each with If-Match (refused if the event changed in Google since it was read) and sendUpdates=none. A field changed on both sides waits until you pick a side. Added as a view of another Event table, it shows that table's events, read only, and offers Sync this table to Google Calendar: once you allow it to edit that table's rows (the host's Allow editing, which then also covers the Google event id, ETag, link and sync baseline the app keeps on each row), it imports one calendar into that table and syncs it the same way; the calendar choice is kept under the app, and the table's own rows stay local. Declared scope: three Google Calendar operations through the integration proxy (list calendars, list events, patch an event), with the Google scopes calendar.calendarlist.readonly and calendar.events; the app holds no token and sends nothing else.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps, connect Google Calendar through the host's consent bar and choose a calendar. It syncs when opened and on Sync now; Send sends the reviewed edits. Nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "One calendar per table, up to 25,000 events per scan. Recurring events (series and instances) and cancelled events are not imported; an imported event cancelled in Google is reported, never deleted. No creating or deleting events in Google. On a table that isn't the app's own, rows are never deleted (Allow editing doesn't cover it) and the table's existing rows are not uploaded. Waits for the stable ontology domain. Mock-tested only: not yet verified against a live Google account.",
    "https://atomicdata.dev/integrations/properties/keywords": "google calendar events agenda week month schedule drive app two-way review",
    "https://atomicdata.dev/integrations/properties/version": "0.3.2",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Event",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Events",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/calendar/0.3.2/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-n7ZsDzZd12auROdJND0P7VEOKoEjsITs24bmQ5wTInXF2qFug4VIrvY+LyONzQdY"
  },
  {
    "https://atomicdata.dev/properties/localId": "todoist",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "todoist",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Todoist",
    "https://atomicdata.dev/properties/emoji": "✅",
    "https://atomicdata.dev/properties/description": "Bring the active tasks of one Todoist account into an Issues table, read-only.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Imports the connected account's active tasks into the app's table as rows of the shared Issue class (issue-v1: title, task/v1 status, body and due date), with the Todoist priority, project, task id and presence as extra columns, so other views of that class can read them. A task that stops appearing in Todoist's active list is looked up by id once and marked completed, deleted, unavailable or unconfirmed, with when it was last seen; only completed closes it. No row is ever removed.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps and connect Todoist through the host's consent bar. Tasks refresh whenever the app is opened and on Sync now. Nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "Read-only: the proxy's Todoist access is data:read, so closing, editing or creating a task here is not sent to Todoist, and a local edit to an imported column is overwritten at the next sync. Active tasks only: a task completed before the first import is never imported. A task gone from the active list is never assumed completed: when Todoist's by-id check answers 404 or fails, the row keeps its last known values and says so. Added as a view of another Issue table, the app imports nothing. One account per app. Waits for the stable ontology domain. Declared, and tested against a synthetic fixture only: not verified against a live Todoist account (#46), including what Todoist answers by id for a completed task.",
    "https://atomicdata.dev/integrations/properties/keywords": "todoist tasks todo projects issues read-only drive app",
    "https://atomicdata.dev/integrations/properties/version": "0.3.0",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Issue",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Issues",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/todoist/0.3.0/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-D2ZK9Jdtxmjg61MOPcqmpO29Z13mieObEDt3mY/PQ//RZ9WdheVxz8b5HlQ9SPj9"
  },
  {
    "https://atomicdata.dev/properties/localId": "google-keep",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "google-keep",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": true,
    "https://atomicdata.dev/properties/name": "Google Keep",
    "https://atomicdata.dev/properties/emoji": "📝",
    "https://atomicdata.dev/properties/description": "Sync your Google Keep notes and lists with a table in your drive, both ways, while the app is open.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Imports the connected account's Google Keep notes (not those in Keep's trash) into the app's own table, one row per note: the title as Name and the body as Description, a list note as a Markdown checklist (- [ ] / - [x], one level of child items). Every minute while the app is open in anyone's browser it syncs both ways: a change in Keep updates its row, an edited row is sent to Keep, a row added here becomes a new note. A note changed on both sides is held as a conflict until you pick a version. A note trashed or deleted in Keep is marked so and its row kept. A row deleted here is neither imported again nor deleted in Keep unless you choose to.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps and connect Google Keep through the host's consent bar. The app syncs when it is opened, on Sync now and every minute while it stays open; two open browsers take turns. Nothing runs while no one has it open.",
    "https://atomicdata.dev/integrations/properties/limitation": "Google offers the Keep API to Google Workspace accounts only; a personal Google account cannot connect (Google refuses the scope). The API has no update: an edited note is sent as a new note and the old one deleted, losing its colour, labels, pins and reminders, so a note that is shared or has an attachment is never replaced and its edit is held back instead. Images and drawings are not imported. One Google account per table. Declared, and tested against a synthetic fixture only: not verified against a live Workspace account.",
    "https://atomicdata.dev/integrations/properties/keywords": "google keep notes lists checklists two-way sync drive app workspace",
    "https://atomicdata.dev/integrations/properties/version": "0.1.0",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Note",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Notes",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/google-keep/0.1.0/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-3OzvVJHaPQWxKk7FF6VqMHg4QnFxFwObW40SiIqcFssjUhJ0U2KzJqEPMVLj5G8+"
  },
  {
    "https://atomicdata.dev/properties/localId": "google-tasks",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "google-tasks",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Google Tasks",
    "https://atomicdata.dev/properties/emoji": "☑️",
    "https://atomicdata.dev/properties/description": "Bring the Google Tasks lists you tick into an Issues table, read-only.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Imports the tasks of the Google task lists you tick (completed and hidden ones included) into the app's table as rows of the shared Issue class (issue-v1: title, task/v1 status, notes as the body, and the due day as an exact date), with the task list, the parent task of a subtask, the Google task id and presence as extra columns, so other views of that class can read them. A task that leaves its list is looked up by id once and marked deleted, unavailable or unconfirmed, with when it was last seen; a task completed in Google is closed here because Google still lists it. No row is ever removed.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps, connect Google Tasks through the host's consent bar and tick the task lists to import. Tasks refresh whenever the app is opened, on Sync now and after you tick or untick a list. Nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "Read-only: the proxy's Google Tasks access is the tasks.readonly scope, so closing, editing or creating a task here is not sent to Google, and a local edit to an imported column is overwritten at the next sync. Subtasks are imported flat, with the parent task's id as a column. A task gone from its list is never assumed completed: when Google's by-id check answers 404 or fails, the row keeps its last known values and says so; at most 50 such checks run per sync. Added as a view of another Issue table, the app imports nothing. One account per app. Waits for the stable ontology domain. Declared, and tested against a synthetic fixture only: not verified against a live Google account (Decision Inbox Q-098), including what Google answers by id for a deleted task.",
    "https://atomicdata.dev/integrations/properties/keywords": "google tasks todo task lists issues read-only drive app",
    "https://atomicdata.dev/integrations/properties/version": "0.1.1",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Issue",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Issues",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/google-tasks/0.1.1/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-hSUbnUwhdFQuB5F7Xbh3MHkl0bfupa1R1A2btYKX2FQmIFBsSC3J5i8btnNs6/tq"
  },
  {
    "@id": "https://atomicdata.dev/integrations/catalog/money",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "money",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Bank statements",
    "https://atomicdata.dev/properties/emoji": "🏦",
    "https://atomicdata.dev/properties/description": "Import bank transactions from MT940 and camt.053 statement exports, and read them as a ledger in the Money drive app.",
    "https://atomicdata.dev/integrations/properties/capabilities": "The importer checks that each statement's opening balance, transactions and closing balance add up, previews which transactions are new or already imported with exact amounts, dates, references and the bank's own descriptions, and writes nothing until you apply the host's review. It writes a Bank transactions table and an Imported statements table (one row per statement, with its opening and closing balance). The Money app shows the Bank transactions table as a ledger per account and currency, with the latest closing balance from a stored statement, search, period and direction filters, your own category and note per transaction, and an import from inside the app through the same review. A row missing its account, currency, amount or value date is listed as incomplete, with a way to the row, and counted in no balance, total or import check.",
    "https://atomicdata.dev/integrations/properties/events": "Upload an MT940 or camt.053 statement when you need it, on the importer's Import tab or from the Money app. No bank token and no live bank connection; nothing runs in the background.",
    "https://atomicdata.dev/integrations/properties/limitation": "MT940 (up to 512 KB) and camt.053 XML (up to 5 MB) files only, up to 500 transactions per file. No CSV or PDF, no payment initiation or live bank sync; bank-specific formats may need additional support. Installed from Drive apps, the Money app imports statements into its own table of the shared Bank transaction class; on another table of that class, or to save a category or note on the importer's table, it first needs you to allow it to edit the table. Waits for the stable ontology domain. Declared, and tested with synthetic statement files only at this version.",
    "https://atomicdata.dev/integrations/properties/keywords": "bank bunq banking finance accounting statement mt940 camt camt.053 iso20022 xml sepa import swift",
    "https://atomicdata.dev/integrations/properties/version": "0.4.6",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Bank transaction",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Bank transactions",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/money/0.4.6/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-0E72FPeJt5Nsb/hUYlm2SPVUuiZXKljMkhR2rHx+4vrIIeX20h/I+W0pcRwJtC5u"
  },
  {
    "https://atomicdata.dev/properties/localId": "moneybird",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "moneybird",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Moneybird",
    "https://atomicdata.dev/properties/emoji": "🐦",
    "https://atomicdata.dev/properties/description": "Import the contacts, hours and financial mutations of one Moneybird administration, read-only.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Imports, per chosen collection: the contacts of one administration (archived ones included) into a typed table; this year's time entries into a Time entries table of the shared time-entry-v1 class (start, end, billable, project and person links), so the Clockify timesheets app shows them in its week grid; this year's financial mutations into a Bank transactions table of the shared bank-transaction-v1 class (account IBAN, currency, exact amount string, date, description, reference), so the Money app shows them in its ledger. Added through Add view on a time-entry-v1 or bank-transaction-v1 table of your own, it can sync that table instead, after Allow editing. Invoices, ledger accounts and the other collections are not imported.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps, connect Moneybird through the host's consent bar, choose an administration and tick what to import. The chosen collections refresh whenever the app is opened and on Sync now, each on its own: one that fails is reported next to the others. Nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "Read-only: nothing is written back to Moneybird. One administration per app. Hours and mutations cover this calendar year only; Moneybird answers at most 100 mutations per request, so a day with 100 or more is refused rather than imported incompletely. Tested against a synthetic fixture, not a real Moneybird account. Waits for the stable ontology domain.",
    "https://atomicdata.dev/integrations/properties/keywords": "moneybird bookkeeping accounting invoices contacts hours time entries financial mutations bank transactions ledger finance administration drive app",
    "https://atomicdata.dev/integrations/properties/version": "0.3.0",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Contact",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Contacts",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/moneybird/0.3.0/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-vj2Y6emubJtyxLmP67WliYKzI22tRcnmFqI8dLjR4gjsQQvNJ08/iLIfX7XVs1Lt"
  },
  {
    "https://atomicdata.dev/properties/localId": "timesheets",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "timesheets",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Clockify",
    "https://atomicdata.dev/properties/emoji": "⏱️",
    "https://atomicdata.dev/properties/description": "A drive app that brings your Clockify time entries into a week view and a table of its own, and sends edits you review back to Clockify.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Reads your own time entries in one workspace over a rolling 7- or 30-day look-back, keeps what each read saw in an observation log in the drive, and shows a week grid, the entries by day and hours per project. Completed entries become rows in the app's table, as the shared Time entry class (time-entry-v1, ontola/atomic-plugins#177): start, end, billable, and project and person as links to rows of the app's own Projects and People tables. Added as a view of another Time entry table, it shows that table's entries, read only, and offers Sync this table to Clockify: once you allow it to edit that table's rows (the host's Allow editing, which then also covers the Clockify entry id and sync bookkeeping the app keeps on each row), it adds your Clockify entries to that table as rows and syncs them the same way, with that table's workspace, look-back and observation log kept under the app; the table's own rows stay local, and no row of it is ever deleted. A timeline shows overlapping entries and work over a break as conflicts, and time no read has covered as not loaded, never as not worked. A sync-status card heads every view: the last sync and its counts, whether edits here go back to Clockify after a review or stay in Atomic, changes waiting or refused, rows left out and why, and the next step for time not loaded. An entry's description, project, billable flag, start and end can be edited in the app or in the table, or the entry deleted; a time range can be marked as worked on a project or as not worked, which trims, splits, extends or creates entries over exactly that range; and a conflict can be resolved by keeping one project, marking it not worked, or removing a duplicate. Each change is listed under Changes to send and written to Clockify only when sent, after a fresh read, and confirmed by a read afterwards. If Clockify changed the same field, Clockify's value is kept; a new entry is not created where Clockify has time by then. With the app open on two devices or in two tabs, one sends at a time, and range edits made on each without seeing the other's are shown as a conflict between your edits and held until one is chosen.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps, connect Clockify through the host's consent bar (the API key is entered at the integration proxy, never in the drive), then choose a workspace and a look-back. It syncs when opened and on Sync now; nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "Write-back is declared, not verified: it is tested against the mock proxy only, and no write has been made to a live Clockify account through the app. Changes are found only while the app is open; a row deleted in the table is not noticed. Running timers, locked entries, breaks and entries with custom field values cannot be edited. Coordination between two open copies is advisory (the drive has no compare-and-swap), so two copies starting to send in the same moment can still both send, at worst creating a duplicate that the app then offers to remove; it has been tested with simulated devices only, not with two real browsers. The same field edited directly on two devices keeps the later edit. No tags, tasks, rates or custom fields. Tested against a mock proxy modelled on Clockify behaviour checked against a live account (2026-09-24); the app itself has not run against a live account or the real integration proxy. On a table that isn't the app's own, rows are never deleted (Allow editing doesn't cover it): a row whose entry is deleted in Clockify is kept, unsynced, for you to delete, and the table's existing rows are not uploaded. Waits for the stable ontology domain.",
    "https://atomicdata.dev/integrations/properties/keywords": "clockify time tracking timesheet week hours projects conflicts drive app",
    "https://atomicdata.dev/integrations/properties/version": "0.8.4",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Time entry",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Time entries",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/timesheets/0.8.4/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-lvGEgIVWKrew56+XdM/y/aALluk0I5MB9jJvavrBIZ8EXjLaR8xckdI2pbgVRoqr"
  },
  {
    "@id": "https://atomicdata.dev/integrations/catalog/notion",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "notion",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Notion",
    "https://atomicdata.dev/properties/emoji": "📓",
    "https://atomicdata.dev/properties/description": "A drive app that brings the Notion databases you share with it into a table, where you browse and edit the rows, and sends your edits back to Notion after you review them.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Reads every Notion data source shared with the connection into one table in the drive, through Devonian lenses: plain title and text, number, checkbox, URL, email, phone, and select, status and multi-select options as the table's own select columns (one tag per Notion option, with its name and colour; a rename in Notion renames the tag and leaves the rows as they are). You browse and edit the rows with the table's own views. Edits to those fields, made anywhere in Atomic, are found when the app opens by comparing each row with the baseline kept on it, listed under Review changes, and sent to Notion only after you press Send, one page update each. A field changed both here and in Notion waits for Keep mine or Use Notion's. The app itself is a small sync-status view: which databases the table syncs with and how many rows each has, the last sync, Sync now, Open table, sync details listing what could not be read, and Disconnect, which removes only this app's access; the rows stay.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps, then connect Notion through the host's consent bar. It syncs when opened if the last sync is older than 15 minutes, and on Sync now; unsent edits are listed whenever it opens. Nothing is sent without a review, and nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "Only existing pages are updated: rows added here are not created in Notion, and nothing is deleted on either side; a page removed or archived in Notion is left in place here. Formatted text is imported as plain text, without the formatting, is listed as a warning, and is never overwritten. Other property types (dates, people, relations, formulas and more) are not imported. A status or select cell given more than one option in the table is held back in the review, since Notion's take one. Notion has no conditional page updates, so an edit made in Notion in the moment between the check and the send is overwritten. All shared databases go into one table. Mock-tested only: not yet verified against live Notion or the real integration proxy.",
    "https://atomicdata.dev/integrations/properties/keywords": "notion database table rows pages two-way review sync status drive app devonian",
    "https://atomicdata.dev/integrations/properties/version": "0.5.6",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Page",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Pages",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/notion/0.5.6/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-V6bF3044M8UBxiX6zSdfyDoKSCUP2OO7UPKwD/5OhyYBZxAKhtSFpPIRtOqaNKYZ"
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/pluginUrl",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "plugin-url",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "Where this integration's source can be fetched from, for entries not bundled as a local package.json in this folder. Optional — omitted for integrations developed in this repo."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/version",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "version",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "The version of this integration currently published in this repository, mirrored from its package.json (see integrations/README.md). Omitted for an entry with no local package.json, such as one reached through the generic LocalThought/Devonian bridge or fetched from pluginUrl. A host compares this against what an installation has pinned to offer an update."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/requires",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "requires",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/json",
    "https://atomicdata.dev/properties/description": "What this plugin needs from the node, derived from its manifest and never written by hand: a sorted JSON array such as [\"persistent-host\", \"plugin-routes:read-only\", \"public-origin\", \"wasm-sandbox\"], with `plugin-routes:<level>`, `operator-listener:<name>` and `operator-sidecar:<name>` for the gated surfaces of docs/design/server-plugin-routes.md section 0. The same list the host puts on each /plugin-catalog entry (atomic-server#1732), so a client can compare it with the node's `hostFeatures` without parsing manifests. Required on the entry of a package whose manifest is version 3 or needs the plugin-routes feature; integrations/tooling/catalog-requires.mjs checks it and writes it."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/app-module",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "app-module",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "URL of the built ES module for exactly this entry's `version`, which a host installs as a drive app's entry point. Distinct from `pluginUrl`, which links to source. For an app built in this repo it is `https://ontola.github.io/atomic-plugins/apps/<shortname>/<version>/ui.js`: `integrations/<shortname>/app/build.mjs`'s output, committed at `apps/<shortname>/<version>/ui.js` and served by GitHub Pages from `main`. A version file on `main` is never changed or deleted, so a changed build needs a new version. A relative URL resolves against this catalog's own URL. See integrations/README.md, 'Publishing a drive app'."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/app-module-integrity",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "app-module-integrity",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "Subresource Integrity hash (`sha384-` plus base64) of the `app-module` bytes. A host refuses to install or update from a module that does not match. `integrations/tooling/apps.mjs check` keeps it equal to the committed module and to a fresh build."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/app-row-name",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "app-row-name",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "What one row in the installed app's table is called, singular (for example 'Pet'). Optional; the app may rename it itself."
  },
  {
    "@id": "https://atomicdata.dev/integrations/properties/app-row-name-plural",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/classes/Property"
    ],
    "https://atomicdata.dev/properties/parent": "https://atomicdata.dev/integrations/ontology/catalog",
    "https://atomicdata.dev/properties/shortname": "app-row-name-plural",
    "https://atomicdata.dev/properties/datatype": "https://atomicdata.dev/datatypes/string",
    "https://atomicdata.dev/properties/description": "What the installed app's table and its rows are called, plural (for example 'Pets'). Optional; given together with `app-row-name`."
  },
  {
    "https://atomicdata.dev/properties/localId": "pets",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "pets",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": true,
    "https://atomicdata.dev/properties/name": "Pets",
    "https://atomicdata.dev/properties/emoji": "🐾",
    "https://atomicdata.dev/properties/description": "A demo drive app: connect the Pets demo provider and import its pets into a table.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Connects through the integration proxy, with no account or key (the demo provider is a static, read-only API on GitHub Pages), and imports every pet it lists into a Pets table, with typed columns (age, vaccinated, weight, updated at). Re-syncing updates changed pets and writes nothing when nothing changed.",
    "https://atomicdata.dev/integrations/properties/events": "Connect once, then Sync now whenever you want the latest pets. Nothing runs in the background.",
    "https://atomicdata.dev/integrations/properties/limitation": "Demo provider only, not a real account. Import only: nothing is written back. Keep the browser open while syncing.",
    "https://atomicdata.dev/integrations/properties/keywords": "pets demo example sample drive app ontology test touch points integration proxy",
    "https://atomicdata.dev/integrations/properties/version": "0.1.6",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/pets/0.1.6/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-e/5WWgkiT8NhNEqenqqVQED18CWs4IpWH4sCQtBnKfaHJrMZfCs340nsJyRCRMew",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Pet",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Pets"
  },
  {
    "https://atomicdata.dev/properties/localId": "issue-tracker",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "issue-tracker",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "GitHub issues",
    "https://atomicdata.dev/properties/emoji": "🐙",
    "https://atomicdata.dev/properties/description": "A drive app that keeps one GitHub repository's issues on a board, two-way, with every change to GitHub reviewed before it is sent.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Imports one repository's issues and comments into the app's table, shown as a board (Todo, Doing, Blocked, Done) or a list, with search and a label filter. The rows are of the shared Issue class (issue-v1: title, task/v1 status and body), so other views of that class can read them. Title, description (Markdown), status and comments sync both ways; Doing and Blocked are the atomic:doing and atomic:blocked labels on GitHub. A change bound for GitHub waits in Review and send until you approve exactly that change. A field changed on both sides pauses sync until you pick a side. An issue gone from GitHub can be kept here only or removed from the board. Added as a view of another Issue table, it offers Sync this table to GitHub: once you allow it to edit that table's rows (the host's Allow editing, which then also covers the GitHub issue number, source, sync baseline and import key the app keeps on each row), it imports one repository into that table and syncs it the same way; the repository choice and sync state are kept under the app, and the table's own rows stay local until you publish them.",
    "https://atomicdata.dev/integrations/properties/events": "Install from Drive apps, connect GitHub through the host's consent bar and choose a repository. It syncs when opened, on Sync now and after each edit made in the app; nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "One repository per table: the app's own table, and each other Issue table it was asked to sync. On a table that isn't the app's own, rows are never deleted (Allow editing doesn't cover it, so Remove from board isn't offered there), the table itself is never written, and syncing pauses when the grant is taken back. A row added to the table outside the app stays local until you choose Publish to GitHub on it. A status other than exactly one of Todo, Doing, Blocked and Done is shown as it is and not synced. Labels and assignees are shown read-only; milestones and pull requests are not synced, and deletions are never sent to GitHub. One syncing view per app is assumed: two tabs or devices are not guarded. A new issue or comment whose send got no answer is never sent twice: you link it to the issue it became on GitHub, or send it again once GitHub shows no match. Waits for the stable ontology domain. Mock-tested only: not yet verified against live GitHub or the real integration proxy.",
    "https://atomicdata.dev/integrations/properties/keywords": "github issues board kanban tracker two-way review drive app devonian",
    "https://atomicdata.dev/integrations/properties/version": "0.4.2",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Issue",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Issues",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/issue-tracker/0.4.2/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-2TJpf6UAo2+4bc4M4Xz8uBB16daHf0FDg2apni18SfcvbP+dAZ9Kfe+5w9b9hgAF"
  },
  {
    "https://atomicdata.dev/properties/localId": "open-cloud-mesh",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "open-cloud-mesh",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Open Cloud Mesh",
    "https://atomicdata.dev/properties/description": "Receive files shared over Open Cloud Mesh 1.5 by servers you allow: signed shares are fetched into a folder you pick, and acknowledged.",
    "https://atomicdata.dev/integrations/properties/limitation": "Experimental. Receiving only, with legacy shared-secret access to absolute WebDAV URIs; no sending, WebDAV serving, token exchange or invites. The received file is a copy taken when the share arrives. Needs a host with plugin routes at read-write; not tested against a real Nextcloud or ownCloud server.",
    "https://atomicdata.dev/integrations/properties/requires": [
      "persistent-host",
      "plugin-routes:read-write",
      "public-origin",
      "wasm-sandbox"
    ]
  },
  {
    "https://atomicdata.dev/properties/localId": "fediverse",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "fediverse",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Fediverse",
    "https://atomicdata.dev/properties/description": "One ActivityPub actor for your drive: others can find it, follow it, receive your posts and reply.",
    "https://atomicdata.dev/integrations/properties/capabilities": "WebFinger and NodeInfo discovery; public posts under a folder you choose as an outbox; follows accepted automatically and kept as resources; posts you publish delivered to followers, signed by a key the server holds; replies to your posts stored as Messages.",
    "https://atomicdata.dev/integrations/properties/limitation": "Declared, not verified beyond one opt-in round trip (follow, Accept, a post, a reply, unfollow) with each of Mastodon 4.7.3 and Akkoma 3.20.1 on loopback with test certificates (Akkoma names the actor without a non-default port: the host routes WebFinger only for acct: resources); GoToSocial cannot follow it yet (per-actor inboxes, signed key fetches). Needs an atomic-server with auth: atomic routes, the signer's inbox in request.caller and WebFinger rels (branch claude/plugin-fediverse-host, in pin candidate16) and plugin routes at read-write. Delivers only to HTTPS shared inboxes at /inbox, to at most 100 inboxes per post; no Update or Delete of posts, no media, no account migration.",
    "https://atomicdata.dev/integrations/properties/requires": [
      "persistent-host",
      "plugin-routes:read-write",
      "public-origin",
      "wasm-sandbox"
    ]
  },
  {
    "@id": "https://atomicdata.dev/integrations/catalog/willow-drop",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "willow-drop",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Willow drop",
    "https://atomicdata.dev/properties/emoji": "🌳",
    "https://atomicdata.dev/properties/description": "Import the entries of a Willow'25 drop file into a Willow entries table, after checking each entry's Meadowcap authorisation and, where the drop carries it, its payload.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Preview namespace, subspace, path, timestamp, payload digest and payload length as exact strings; payloads up to 65,536 bytes are stored as UTF-8 text or base64. An entry is left out when a newer entry in the same drop has its path or a prefix of it, or when the table already holds a newer entry at the same path.",
    "https://atomicdata.dev/integrations/properties/events": "Upload a drop file, raw or base64-encoded, when you need it. No network access, no secrets and no live Willow sync.",
    "https://atomicdata.dev/integrations/properties/limitation": "Declared, not verified: up to 1,000 entries and 5,000,000 bytes (5 MB) per drop; sandbox fuel use per entry has not been measured. Only drops written by willow25 0.7.9 have been tested. Capabilities with delegations and partial payloads are refused, and an imported entry does not remove existing rows whose path it prunes. Timestamps are read as the Willow data model recommends (TAI microseconds since J2000); willow25 0.7.9, via hifitime, reads the same value 86,432.184 s later, which is being reported upstream. The raw timestamp is kept alongside.",
    "https://atomicdata.dev/integrations/properties/keywords": "willow willow25 meadowcap drop sideload earthstar p2p local-first import",
    "https://atomicdata.dev/integrations/properties/version": "0.1.0"
  },
  {
    "@id": "https://atomicdata.dev/integrations/remotestorage",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "remotestorage",
    "https://atomicdata.dev/properties/name": "remoteStorage",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/description": "Use this drive as a remoteStorage server: apps you approve per category (read, or read and write) store their documents as Atomic Files in a folder you choose, and anyone can read what they put under /public/.",
    "https://atomicdata.dev/integrations/properties/capabilities": "WebFinger discovery for name@<installation host>, the OAuth implicit grant through AtomicServer's consent page with per-category r/rw scopes, GET/HEAD/PUT/DELETE with ETags, If-Match and If-None-Match, JSON-LD folder listings, public documents without a token, CORS for browser apps. Also imports JSON text exports as reviewed text documents.",
    "https://atomicdata.dev/integrations/properties/limitation": "Declared, not verified in production: up to 1,000 documents per storage (every listing and write reads them all), 16 MiB per document; no byte ranges, no token in query parameters, no PKCE code flow. An app is not told when you deny access. A preconditioned write is checked just before it is applied, not inside the commit. Needs a server built with the plugin-routes feature at --plugin-routes read-write with a routes origin, and an AtomicServer that includes the claude/plugin-remotestorage-host changes (atomic-server 59ddfe7 or later).",
    "https://atomicdata.dev/integrations/properties/keywords": "remotestorage unhosted webfinger oauth storage sync",
    "https://atomicdata.dev/integrations/properties/version": "0.3.0",
    "https://atomicdata.dev/integrations/properties/requires": [
      "persistent-host",
      "plugin-routes:read-write",
      "public-origin",
      "wasm-sandbox"
    ]
  },
  {
    "@id": "https://atomicdata.dev/integrations/catalog/willow",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "willow",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Willow export",
    "https://atomicdata.dev/properties/emoji": "🌳",
    "https://atomicdata.dev/properties/description": "Serve selected public resources as a Willow'25 drop whose entries the server signs with this installation's own subspace key, in a communal namespace you choose.",
    "https://atomicdata.dev/integrations/properties/capabilities": "One public URL answers the drop: each selected resource's chosen properties as a JSON-AD payload at path prefix plus subject, timestamped by its last commit (microseconds of TAI since J2000), with a communal Meadowcap capability and the server's Ed25519 signature. Unchanged resources give the same bytes.",
    "https://atomicdata.dev/integrations/properties/events": "Anyone who fetches the URL gets the drop as it is then. No live Willow sync (WGPS), no network access and no secrets.",
    "https://atomicdata.dev/integrations/properties/limitation": "Declared, not verified: up to 32 resources and 32 properties, 65,536-byte payloads. Needs a server built with plugin routes at read-write, and host support that is not in a released server yet. Only public resources and communal namespaces; no owned namespaces, delegations or live sync.",
    "https://atomicdata.dev/integrations/properties/keywords": "willow willow25 meadowcap drop sideload export p2p local-first",
    "https://atomicdata.dev/integrations/properties/version": "0.3.0",
    "https://atomicdata.dev/integrations/properties/requires": [
      "persistent-host",
      "plugin-routes:read-write",
      "public-origin",
      "wasm-sandbox"
    ]
  },
  {
    "https://atomicdata.dev/properties/localId": "learning",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "learning",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": false,
    "https://atomicdata.dev/properties/name": "Leerboom",
    "https://atomicdata.dev/properties/emoji": "🌳",
    "https://atomicdata.dev/properties/description": "A drive app that shows a learning tree: skills with the skills they need, the lessons for each, and what to learn next, worked out from what you say you master.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Shows any table of the shared Skill class (skill-v1) as a layered dependency graph. A skill is mastered, available or not yet due; the last is only advice, and every skill can be opened. Per skill it lists lessons (the shared Lesson class, lesson-v1) with an icon per format, offers \"I master this\", which writes a Mastery row (mastery-v1) to a table the app keeps in your drive, and \"Path to this goal\", which highlights the unmastered skills on the way and suggests the next logical steps. \"Load starter tree\" adds about 30 skills of mathematics and physics (Dutch) to the table, with placeholder lessons. Trees from different tables or drives can be linked by marking skills as equivalent. No account, network or provider.",
    "https://atomicdata.dev/integrations/properties/events": "Add it as a view to a Skill table, or open it and load the starter tree. Mastery is written when you press \"I master this\". Nothing runs while the app is closed.",
    "https://atomicdata.dev/integrations/properties/limitation": "Declared, not verified: unit-tested against a fake host store only, with no host E2E run yet. Mastery is self-reported; there are no assessments, attempts, credentials or attested results. The starter lessons name no material yet (every content link is a TODO). Mastery rows inherit the rights of the App in your drive, so install it in a drive that is yours. On a Skill table the app did not make, loading the starter tree needs the host's Allow editing. Waits for the stable ontology domain.",
    "https://atomicdata.dev/integrations/properties/keywords": "learning tree leerboom skills lessons mastery curriculum education mathematics physics drive app",
    "https://atomicdata.dev/integrations/properties/version": "0.1.0",
    "https://atomicdata.dev/integrations/properties/app-row-name": "Skill",
    "https://atomicdata.dev/integrations/properties/app-row-name-plural": "Skills",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/learning/0.1.0/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-hshL47qBYLNL6M0RWOs+paY+RpJ//1Sxo0AkHWpl2h71DQ8rQkjk05cUeX/dGZXw"
  },
  {
    "https://atomicdata.dev/properties/localId": "google-keep-view",
    "https://atomicdata.dev/properties/isA": [
      "https://atomicdata.dev/integrations/classes/PluginCatalogEntry"
    ],
    "https://atomicdata.dev/properties/shortname": "google-keep-view",
    "https://atomicdata.dev/properties/name": "Google Keep View",
    "https://atomicdata.dev/properties/emoji": "☑️",
    "https://atomicdata.dev/integrations/properties/experimental": true,
    "https://atomicdata.dev/integrations/properties/enabled": true,
    "https://atomicdata.dev/properties/description": "A familiar card and checklist view for imported Keep lists and synced notes, with unchecked items first.",
    "https://atomicdata.dev/integrations/properties/capabilities": "Shows imported checklist tables with their own text and boolean Checked or Done columns, as well as the Google Keep sync app’s notes. Preserves Position and nesting where present. Search notes and items, switch grid/list layout, expand completed items and follow the host theme. On a checklist table, Allow editing lets you tick its actual Checked or Done column.",
    "https://atomicdata.dev/integrations/properties/events": "Install Google Keep View separately from the Google Keep connection app and open it once after importing notes. It discovers compatible tables and makes itself available under Add view on them. Reopen or Refresh after another import. Table subscriptions refresh rows; no provider calls or background sync.",
    "https://atomicdata.dev/integrations/properties/limitation": "Imported tables need a typed text column (Array item, Text or Name) and boolean Checked or Done column. The standalone and notes-table views are read-only; ticking requires adding the view to the checklist table and allowing row edits. Does not add, delete, rename or reorder rows. Sending edits to Google remains controlled by the importer or sync app. Synthetic tests only; no live Google evidence.",
    "https://atomicdata.dev/integrations/properties/keywords": "google keep view checklist notes cards unchecked completed",
    "https://atomicdata.dev/integrations/properties/version": "0.2.0",
    "https://atomicdata.dev/integrations/properties/app-module": "https://ontola.github.io/atomic-plugins/apps/google-keep-view/0.2.0/ui.js",
    "https://atomicdata.dev/integrations/properties/app-module-integrity": "sha384-iMQ7lCjJtodxpsCI1or++HQ6QPs72ooMDWU1cDTBvP7hQjz8M4GYmuLOqYTfHSey"
  }
]
