Blocchi

Lineage and storage

Explain where a value came from, and decide what Blocchi manages, retains and keeps as history.

Lineage (`/app/data-plus/lineage`)

Useful lineage starts with the right question:

Which source produced this record? Use Explorer to trace a record back to the source and dataset that produced it.
Why did this value become canonical? On a Party's detail page, golden profiles keep the source identities, the winning value, its provenance and an explanation.

A single end-to-end source → transformation → Party graph is not yet a published experience, and Blocchi does not present it as complete.

Decide what stays at the source and what Blocchi manages. Access, ingestion, retention and history are separate decisions:

Policy explains the behavior per dataset.
Operations shows real usage by dataset: bytes, processing and retention.
Managed capacity covers policy, limits and metering for use cases that go beyond the base product's live mode.
Managed analytical history keeps history for analysis where it is enabled.

Last updated on

Useful lineage starts with the right question:

Which source produced this record? Use Explorer to trace a record back to the source and dataset that produced it.
Why did this value become canonical? On a Party's detail page, golden profiles keep the source identities, the winning value, its provenance and an explanation.

A single end-to-end source → transformation → Party graph is not yet a published experience, and Blocchi does not present it as complete.

Decide what stays at the source and what Blocchi manages. Access, ingestion, retention and history are separate decisions:

Policy explains the behavior per dataset.
Operations shows real usage by dataset: bytes, processing and retention.
Managed capacity covers policy, limits and metering for use cases that go beyond the base product's live mode.
Managed analytical history keeps history for analysis where it is enabled.