table) can declare three things to the people who
share it:
- An owner: the person who answers for the data. Ownership is accountability, not access. Sharing still decides who can read or edit.
- A record role:
recordwhen this dataset is the source of truth for its rows, ormirrorwhen it copies a record another system holds, such as “Attio people”. A mirror tells people where to fix a fact. - Row provenance: every row must say where its facts came from and when they were last checked. Once this is on, a write whose rows leave either column blank is refused, and the error names those rows.
table first, or in the
same request.
From the CLI
me, and must be a member
of the dataset’s organization. Each command has a --clear (or --off) form
that removes the declaration.
erdo datasets schema <slug> --declared prints the declarations after the
declared columns.
Row provenance
The source and checked-at columns default tosource_url and checked_at.
When the dataset has a declared schema, both columns must be in it; add them
with an add_column operation first. While the requirement is on, a schema
change that would drop either column is refused unless the same request turns
provenance off.
A value is blank when it is missing, empty or only whitespace. On a merge, a row
that already stores a source and a checked-at value keeps them, so an update
only needs the columns it changes. A new row always needs both.
REST and MCP
Send the declarations toPOST /v1/datasets/:datasetSlug/schema, the same
route that sets class and purpose. In MCP, use erdo_update_dataset_schema.
Omitted fields are left unchanged.
The response, the
declared_schema view of POST /v1/datasets/:datasetSlug/fetch,
and erdo_get_dataset_schema all carry the declarations under stewardship:
stewardship is absent when the dataset declares none of them.
