Data Store¶
The Data Store view describes history available through the selected Forge server. ClickHouse is an implementation detail behind this product surface; Terminal queries it through Forge rather than connecting to the database.
Scope the view¶
Select an instance and then choose the current run, all runs, or a specific run where available. Search and domain filters apply to the scoped catalog.
Resources¶
The Resources view joins runtime declarations with persisted storage facts. A resource can be:
persisted: declared and backed by historical rows;
declared: cataloged for the run but no stored rows are currently found;
live-only: intentionally has no historical model.
Select a resource to inspect its exact key, contract, storage mapping, and lineage. Copy the resource key when using the REST or WebSocket API.
Tables¶
The Tables view exposes supported history tables and schema metadata. It is an operator inspection surface, not permission to depend on physical table names from an external client. Product integrations should prefer the resource and aggregation endpoints.
Preview queries¶
Terminal builds read-only, scoped previews for the current selection. Empty rows can mean the run did not publish the resource, the resource is live-only, or ingestion has not produced durable history. Use the Health view and project Debug evidence to distinguish these cases.
See Resources, Live Data, and History for the difference between a live resource and its optional history model.