Parable Pool

parables.{parable}.{plot}

SELECT *
FROM parables.spend.tool_costs
LIMIT 10

​

The address of a Parable

​

Plots the Workspace cannot serve

​

Plots that are views

​

Build on materialized results

SELECT
  cost.provider,
  cost.month,
  cost.amount
FROM parables.spend.tool_costs AS cost
WHERE cost.month >= DATE '2026-01-01'
ORDER BY cost.month DESC

​

Read the Parable beside a Platform Parable’s tab

SELECT c.change, c.kind, c.title, p.name AS parable
FROM subject.changes AS c
CROSS JOIN subject.parable AS p
ORDER BY c.kind, c.title

​

Rows about the Parable beside the tab

• About the Parable beside the tab. A read returns the rows about the subject and about its Pieces, and only those that the reader can read. The reader must read the subject, as for the subject relations. For a row about a Piece, the reader’s Pieces tree must also list that Piece: Peeking lists Pages only.
• One item, one subject. An item of parables.{parable}.{pane} shows only when each of its rows in the reader’s layers is about such a subject, so a row about another Parable never lends a field to it.
• No subject, no rows. A read with no subject returns no row of such a Pane, by either name. This is a Plot read outside a tab, such as a Page of the Platform Parable opened on its own.
• A Refresh reads none. A Refresh has no Parable beside it, so it reads no row about a subject.
• Older definitions do not remove the rule. A Pane remains subject-bound when either the definition on screen or its current definition declares rows about a Parable. After removal, the newest accepted live definition of that Pane keeps its subject rule. Ordinary removed Panes keep their existing reads. If the retained type cannot be checked, that Pane’s Preferences do not read; unrelated Panes and Pane data keep their own rules.
• Never across Workspaces. A shared read checks each contributing copy’s current Pane, including its exact upstream Release. A subject-bound Pane contributes no rows, including rows saved before it declared subjects. A missing or deleted current Pane also contributes no rows. Older shared reads therefore lose retained ordinary rows from that Pane, but the rows remain stored.
• Never through workspace.preferences. workspace.preferences, and SQL that reads the stored rows directly, return no row of such a Pane, also for Publishing or Primary on the composed Platform Parable.

SELECT r.id, r.notes, r.signer
FROM parables.proofs.reviews AS r
ORDER BY r.id

​

Read a Platform Parable’s Plots

SELECT
  p.team,
  date_trunc('week', a.date) AS week,
  sum(a.core_metrics__lines_of_code__added) AS lines_added
FROM providers.claude.claude_code_analytics AS a
JOIN parables.perceptions.people AS p
  ON p.email = lower(a.actor__email_address)
GROUP BY p.team, date_trunc('week', a.date)

• A published Version reads the Release of the Platform Parable that was the newest in the Workspace when the Version was published. A view of the Platform Parable runs the SQL of that Release, so a later Release does not change what the view reads.
• The next publish reads the newest Release. The publish is refused if the SQL does not plan against it.
• Changes read the newest Release.
• Latest reads, for a Pipeline of the Platform Parable, its newest Refresh whose output has the same columns as that Pipeline in the Release the read reads. Any Release with those columns can have made that Refresh. So when a later Release keeps a Pipeline’s columns and refreshes, the reading Parable shows the rows of the later Release, and the answer names that Release.
• A Refresh of the reading Parable reads the Refresh of the Platform Parable that it recorded when it ran.

x-parable-releases: <Parable id>:<Version id>, ...
x-parable-refreshes: <Parable id>:<Refresh id or latest>, ...

• x-parable-releases names every Release that made rows the read read. A view’s rows come from the Release the read reads, and a Pipeline’s rows from the Release that made its Refresh. So the answer names a Parable twice when those are two Releases. Do not send this answer back as a request header: a request names the Release the read reads, each Parable once.
• x-parable-refreshes names the Refresh read of each Parable.
• meta.parableReads lists the same reads, one for each Release and Refresh.

• the Release it reads was retracted. A Retract is refused while the Version that a Workspace reads now reads that Release (Platform Parables);
• the Parable it reads is no longer a Platform Parable. A Parable stays a Platform Parable while other Parables’ published Versions read it, so only an older Version or Changes get this refusal;
• a header names a Release that the read does not read;
• a Refresh of the reading Parable reads a Plot that a newer Release of the Platform Parable changed. Publish the reading Parable again to read the newest Release.