Visualize Brains Summary

Return every dataset the caller may read, described from relational metadata.

The cheap counterpart of GET /visualize/brains: the same datasets, but only what an overview shows — name, sources, size, colors — built from relational metadata and the per-cognify-run count cache instead of one bounded graph read per dataset. The cost is one count query per cognify run whose count is not cached yet, not a graph fetch per dataset on every call, so a cold cache pays once per run and every later call pays nothing. /brains stays the call to make when the node and link arrays themselves are needed.

Response

{dataset_id: {"name", "source_names", "node_count", "node_set_colors"}}:

• name (str): the dataset’s name
• source_names (list[str]): its distinct node set names, sorted; empty when the data was ingested without node sets
• node_count (int): nodes in the dataset’s graph as of its latest cognify run — the whole graph, not only entity nodes, and 0 for a dataset that has never been cognified
• node_set_colors (dict[str, str]): node set colors from the same rule /brains uses. Same rule and same node sets give the same colors, but the two endpoints can be looking at different node sets — /brains takes them from a bounded graph fetch (and so sees sets that exist only in the graph), this takes them from a full relational scan — and where the sets differ the colors do too

Error Codes

• 409 Conflict: Payload could not be built (generic message; full detail is server-logged, not returned, to avoid leaking internals)

Notes

• Only datasets the caller has read permission on are included