registries / dataset
@ekairos-dataset
Domain data packaged for AI work. This registry will ship the UI that makes materialization observable — every component reads durable state from @ekairos/dataset.
| id | kind | title | status |
|---|---|---|---|
| rec_01 | tender | Open tender snapshot | materialized |
| rec_02 | tender | Supplier bid rollup | materialized |
| rec_03 | file | price-list.xlsx → rows | transforming |
| rec_04 | text | Pasted spec → structure | queued |
Domain query, file, or text
fromQuery snapshots live domain state; from / fromText pull files and raw input into the same build.
Rows or a single object
asRows for tabular work, first for one structured result. Sandbox-backed reactors handle the heavy parsing.
dataset_datasets + dataset_records
Output is domain state: datasets carry analysis and artifacts, records carry the materialized rows.
setup
Configure the namespace before the first table ships.
The per-domain manifest is already live. Items will publish into @ekairos-dataset as the dataset surfaces stabilize in the workbench.
{
"registries": {
"@ekairos-dataset": "https://registry.ekairos.dev/r/dataset/{name}.json"
}
}planned items
dataset-source-summary
DatasetSourceSummary
What fed the dataset: domain queries, files, and text sources with their analysis state.
shadcn add @ekairos-dataset/dataset-source-summary
dataset-rows-preview
DatasetRowsPreview
Rows and object preview with schema-aware empty states — the table that understands materialization.
shadcn add @ekairos-dataset/dataset-rows-preview
dataset-transform-panel
DatasetTransformPanel
Transform runs linked to sandbox execution and events, observable end to end.
shadcn add @ekairos-dataset/dataset-transform-panel
Materialization is already a runtime. This registry makes it visible.
dataset domain