Lineage canvas

The collection Lineage tab mounts the Lineage explorer (?tab=downstream). It has two top-level tabs that keep their state when you switch between them: Catalog map and Investigation. Every read re-validates seeds, nodes, and relationships before releasing a response (409 LINEAGE_SOURCE_CHANGED if a source changed mid-read) and makes no model or indexing calls while browsing.

Catalog map

Opening Lineage without choosing a document shows the Catalog map: each current document in the collection is one box (up to 200 drawn from up to 2,000 considered), grouped by theme, tender family, or linked cluster, and joined by up to 800 links:

• Link kinds: Cross-reference (stored assertion, such as “see Appendix C”), Amendment (stored assertion where an addendum amends a clause), Shared entities, and Shared field values.
• Side panels: Document (pages, passages, entities, relationships, Investigate, and Open source), Insights (most connected, unlinked, most amended, and hub/bridge roles), Entities, Themes (GraphRAG communities), and the Knowledge layers strip linking to the Knowledge tab.

Investigation and three views

Opening Lineage from a document row (or clicking Investigate in the Catalog map) opens Investigation. Switch between Graph, Document breakdown, and Table:

• Node types: document, chunk (Smart Bite), entity, and occurrence.
• Connection types: containment, extracted assertion, heuristic inference, resolved membership, shared field values, and semantic similarity.
• Bounds: Discovery returns up to 40 candidates; neighborhoods return up to 80 nodes and 120 edges; the in-session graph holds up to 200 nodes and 320 edges across up to 5 collections.
• Grounded questions: Select nodes or relationship sources, preview the bounded answer scope (at most 8 Smart Bites across 6 documents), and ask a grounded question using the workspace’s grounded-answer model.

Time travel, Value over time, and Change activity

When temporal cursors are enabled (BUNDATA_TEMPORAL_GRAPH_CURSORS) in a stored workspace, Lineage separates two axes of time:

• True at (valid time): Which facts held in the world at that UTC instant (trueAt in the URL).
• As known at (system time): What Bundata had recorded by that UTC instant (knownAt in the URL).

Time-travel inspection includes:

1. Entity profile and Value over time: Selecting an entity shows its canonical name, aliases, masked identity keys, cited summary, facts grouped by relation, and—for single-valued relations such as a contract fee, amount, or deadline—a Value over time step chart (POST /api/w/:wsId/lineage/value-series) across valid time as known at the system-time cursor, with keyboard navigation and RTL support.
2. History map: Plots every recorded version of an entity’s facts or a single relationship withvalid time on the horizontal axis and recorded system time on the vertical axis (distinguishing first records, corrections, world changes, and retractions).
3. Changes and themes (How much changed activity chart and What changed diff):
   • How much changed (POST /api/w/:wsId/lineage/activity and /api/w/:wsId/temporal-graph/activity): A stacked bar chart (and screen-reader table) counting asserted, closed, retracted, and corrected facts per UTC Day (last 30 days), Week (last 26 weeks, starting Monday), or Month (last 12 months) along either valid time (What changed in the world) or system time (What Bundata learned). Clicking or pressing Enter on a bar compares that exact period.
   • What changed: Lists up to 100 fact changes between two chosen times.
   • Themes: Stored GraphRAG community reports whose facts hold at True at, with Focus on canvas to highlight or load member entities.