Build something that is not there yet
Promote a spreadsheet or CSV to a governed, tested table
- When the spreadsheet everyone depends on moved a column again and nothing downstream noticed until it broke.
- When a CSV export drives a mart and it has never had a key test or a documented owner.
Promote a spreadsheet or CSV to a governed table, as a dbt seed when the file changes rarely or a dlt load when it is refreshed on a cadence, with key tests and a schema contract that fails loudly on a moved or renamed column. Covers the promoted table and its checks, not the source file's own workflow.
Sample This Recipe has not been materialized in the Cookbook repository yet. Its trigger, description, prompt, agent guidance and acceptance conditions, and the explanation below, are prototype drafts. Its name, job, area and readiness come from the reconciled Cookbook seed snapshot. Readiness is a separate question from this one: it says whether the capability exists, not whether the writing has been reviewed.
Use this Recipe
Use the VibeData Recipe `governed-spreadsheet-table` at https://getvibedata.ai/cookbook/governed-spreadsheet-table Read the Recipe and execute it in the context of the current Intent.
Recipe id governed-spreadsheet-table · Not yet materialized in the Cookbook repository, so the pointer addresses this page.
Verified by
What has to be observably true before this Recipe is finished.
- a fixture with a moved column fails the schema contract
- key tests are green on the current file
- every column is documented with an owning team
- the original file is left untouched by the load
Recipe promptThe task specification the agent reads. Reference only — it is not what you copy.
Deliver: Promote a spreadsheet or CSV to a governed, tested table. Promote a spreadsheet or CSV to a governed table, as a dbt seed when the file changes rarely or a dlt load when it is refreshed on a cadence, with key tests and a schema contract that fails loudly on a moved or renamed column. Covers the promoted table and its checks, not the source file's own workflow. Execute inside the current Intent. Its Domain, repository, platform, environment and attached sources are the context for this work — read them rather than asking for them. The work is done when: - a fixture with a moved column fails the schema contract - key tests are green on the current file - every column is documented with an owning team - the original file is left untouched by the load Report the evidence for each condition above with the result. A condition you cannot meet is something to say, not something to work around.
Agent guidanceHow the agent approaches the work, and what it will not do.
Profile the inputs the grain, joins and measures actually depend on before proposing a model. Put the design up for review — grain first — then build in an isolated copy with tests and documentation landing beside the model rather than after it.
Composes
- source profiling and incremental load
- dbt in the project
- dlt in the project
- isolated-copy execution and gate verification
Guardrails
- Build in an isolated copy. Production is read, never written.
What you need
- Microsoft Fabric Lakehouse, MotherDuck, or DuckDB.
- Read access to the source. Not write access to production.
- dbt and dlt in the project, or the intent to add it.
How it goes
- State the outcome in one sentence, in the language the request arrived in.
- Let it profile the inputs the grain, the joins and the measures actually depend on.
- Review the design. Disagreeing about grain here costs a sentence; after the model exists it costs a rewrite.
- Let it build in an isolated copy, with the tests and the documentation landing beside the model rather than after it.
- Read the acceptance conditions against the run.
What you end up with
The deliverable, in your own repository, as ingestion work a reviewer who knows the project reads as native to it. Alongside it, the evidence for every one of the acceptance conditions above — which is the part that is still there in three weeks when somebody asks.