Cells

A Cell is the intersection of row and column — and more than a value. Every cell carries five things:

• Value — the actual result.
• Status — pending, running, succeeded, failed, skipped (by the domino rule).
• Origin — which tool, which provider, which inputs, which run produced this value.
• Cost — what this value cost, charged only on success.
• History — every previous version of this value, who or what wrote it, and when.

”Why does this value say what it says?”

That question is always answerable. Clicking a cell opens its origin: which enrichment provider delivered, which prompt ran on an AI column, which import brought the original value, or which earlier value was overwritten and by whom — user, agent or a workflow run. This replaces the silent overwriting that used to make values disappear without explanation.

Recomputing

Every cell can be re-run on its own without re-running the whole table — with a cost preview (dry run) before any chargeable run. A re-run never silently overwrites an already successful cell; failed cells can be re-triggered deliberately, and automatic retries stay limited to technical errors (timeout, network) — content failures (an empty AI answer, say) require your deliberate retry.

Cells are therefore your table’s audit log: every external write (a sending enrollment, a CRM update) mirrors its ID, its status and any errors back into the cell — the same cell that carries the value.

See also: Columns define what a cell computes; Runs are the receipt of the run behind it.