Providers
Parable uses the word provider for three different things, and keeping them apart prevents most confusion. A Provider is an outside system that contributes data to a Workspace, such as GitHub, Linear, Slack, Google Workspace, or Workday. The Provider Pool is the queryable data a Workspace’s Providers produce. A model provider is an AI model service that Ponder uses to write its replies, such as Claude or Gemini on Parable’s own servers. Providers bring a company’s work data in; model providers are how Ponder reasons about it. A Provider Plugin describes how Parable authenticates to a Provider, which data streams it offers, and how its records become tables. A Provider connection is one Workspace’s configured copy: its chosen authentication strategy, credentials, settings, enabled data streams, and sync state. The plugin is shared by every Workspace; the connection belongs to one. A data stream is one collection of records, such as issues or users. Enabling a stream makes it eligible to sync, and rows appear only after the connection runs it successfully. Members open Providers from the Workspace sidebar to browse the directory, connect a Provider, repair connections that need attention, and request a missing Provider. A request does not create a connection, and a saved secret is never shown again. Each synced stream becomes a Provider Pool table namedproviders.<connector>.<table>, where the connector part is the Provider Plugin’s short name, as in providers.linear.issues. Field names are lowercase, and nested fields join with a double underscore, so assignee.email becomes assignee__email. Tables hold current state: read the whole table where _parable_deleted is false and _parable_observed is true, because the latest dt holds only the rows that changed that day. In a table of records that change, such as issues or pull requests, each row is the current state of one record, so do not deduplicate it by its key. Some event tables store an event again for each load that reads it. To read one row per event from such a table, keep the row with the latest dt, then the latest _parable_seal_id, for each key. The system columns are dt, _parable_observed, _parable_last_observed_at (when a load last contained the row), _parable_deleted, _parable_deleted_at, _parable_seal_id, and _parable_event_date on some event tables. There is no other system column, such as a sync time. Join people across Providers on their email columns, never on each Provider’s own id. Provider quality, under providers_quality, records each table’s checks, control limits, size, and freshness; a SKIPPED check is not a pass. The same SQL connection also reaches published Artifacts, Plot results, and the live Workspace Pool of members, roles, and connected Providers. A table of a Provider the Workspace has not connected, or of a stream it has not turned on, still answers SQL as an empty table with its declared columns, so a Parable runs in any Workspace. Before reading an empty result as no activity, check that the Provider is connected (workspace.providers), the stream is on (workspace.provider_connections, by platform_tap_name), and data has reached the Pool (workspace.stream_data). Then check recent rows in workspace.provider_refusals. A misspelled table still fails as unknown.
A person picks the model for each Message in the composer: Ponder, with its Simple, Standard and Strong effort levels, or another model with that model’s own effort levels. Parable serves every model in the list; a Workspace administrator orders and hides entries in Ponder models under Protection, AI processors, and the Workspace’s AI processor settings decide which models it can use. Every route requires zero data retention. Model providers receive a pseudonym, never a person’s Parable identity. Replies do not show what they cost.
None of these layers widens access. A query reads only the current Workspace under the person’s current access, a connection change affects only its Workspace, and a model choice changes how Ponder answers, not what it may do.
- Ask which Providers are connected and healthy, and which of their streams are on. Ponder reads
workspace.providers,workspace.provider_connections,workspace.stream_data, and the Provider quality summaries. It joins these tables by their ids; it does not infer a connection from a display name. - Before writing SQL, find the exact tables and columns with Pool search, which searches both Pools by name and description, then describe the selected table. A listed table is addressable but can still be empty, so check row counts. Read every query warning. If a warning names pending data or a source-permission index rebuild, report the last served snapshot and wait for processing before concluding that ingestion or Provider permissions are incomplete. Together, the catalog’s table and field descriptions, types, keys, and relationships reconstruct the queryable connector definition. Join that definition to
workspace.provider_connections.platform_tap_nameto learn whether the stream is enabled. Connector credentials, secret references, request headers, and internal storage locations are never queryable and are not needed to explain the served data. - When a connected, enabled stream is empty or missing parents, inspect
workspace.provider_refusalsbefore concluding that the Provider had no data. Always boundrun_started_at, usually to the period under investigation or the last 30 days, because retries leave historical rows and an unbounded read can exceed the query row limit. Filter byprovider_id,stream_idorplatform_tap_name, andparentwhen known. Report the latesthttp_status,error_code,category,outcome, andprovider_reason; never treat an old refusal as current when a later attempt succeeded. - Distinguish four outcomes: not connected, stream disabled, no load reached the Pool, and a Provider refusal. An empty successful stream is a fifth outcome. State which evidence supports the answer and what remains unknown.
- For a credential error, reconfigure the connection’s authentication; for a missing system, file a Provider request.
- To change how Ponder answers, pick another model or effort level in the composer before sending.
- If Ponder reports that execution is not enabled, contact Parable support. No model change fixes it.
- To name the Provider behind a person’s linked account, read connector_slug on providers.identity.account_associations, then join workspace.providers on connector_slug for its display name, taking each slug once because that table has one row per connection. Never hard-code a map from connector ids to names.