Populate
Every Parable is built for every Provider that could feed it, and a Provider the Workspace has not connected reads as an empty table. Populating a Parable means telling each reader what their Workspace lacks and how to connect it, with ImproveParable on a visual and PopulateParable over the Home content (see the Panes Power), and nothing more.- Declare the groups once. The Home Page’s Perception names the Parable’s Providers in groups (see the Perceptions Power): a title, a description, Required to Populate or Improves the Parable, and at least, at most or exactly one Provider. A group is a kind of data, such as Ticketing, Code or People, so a Workspace with Jira is never asked for Linear; a Provider can be in several groups. Put every Provider that the Parable’s Plots read in a group: a Pane whose Plots read only Providers that no group names offers no Improve this…, and Prepare does not find that Provider for you.
- Let the panel list them. ImproveParable, PopulateParable and Contextual Ponder’s Improve this… open one panel that lists each group’s missing Providers with Connect and folds the connected ones; a visual with no unmet group that still offers a Provider shows no prompt (a group with more connected than its rule allows offers none), and never list a Provider as missing yourself.
- Emphasize what the Pane needs, until the groups are declared. Before the Home Page declares groups, name the groups a Pane needs most in emphasis, such as People on adoption by team, so they lead. Declared groups keep the order the Home Page gives them, Required to Populate first, and emphasis changes nothing.
- Never claim data the Workspace does not have. Where a Provider is missing, show a designed empty state or the connect prompt, never a zero, an “Unknown team” row, or a headline that counts rows the Parable could not read.