Build something that is not there yet
Gate a consumer pipeline on upstream data readiness instead of a clock
- When the mart runs at a fixed hour whether or not the upstream load actually finished.
- When a consumer pipeline has started against a partial load more than once and nobody catches it until the numbers look wrong.
Gate a consumer pipeline's first stage on a producer's recorded readiness through an agreed cutoff, with a bounded timeout and an explicit admit or fail branch, instead of starting on a fixed schedule. Covers the readiness gate and its branches, not an on-demand backfill's own logic.
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.
Review planned Recipe
At least one capability or object type this Recipe needs is not supported yet.
Read the VibeData Recipe `readiness-gated-orchestration` at https://getvibedata.ai/cookbook/readiness-gated-orchestration At least one capability or object type this Recipe needs is not supported yet. Treat it as a reference, not as work to execute.
Recipe id readiness-gated-orchestration · 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.
- the consumer starts only once the producer's readiness record covers the agreed cutoff
- a wait past the bounded timeout fails loudly instead of running on partial data
- an on-demand backfill runs against an explicit historical cutoff
- the admit and fail branches are both exercised in the sandbox
Recipe promptThe task specification the agent reads. Reference only — it is not what you copy.
Deliver: Gate a consumer pipeline on upstream data readiness instead of a clock. Gate a consumer pipeline's first stage on a producer's recorded readiness through an agreed cutoff, with a bounded timeout and an explicit admit or fail branch, instead of starting on a fixed schedule. Covers the readiness gate and its branches, not an on-demand backfill's own logic. 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: - the consumer starts only once the producer's readiness record covers the agreed cutoff - a wait past the bounded timeout fails loudly instead of running on partial data - an on-demand backfill runs against an explicit historical cutoff - the admit and fail branches are both exercised in the sandbox 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
- job scheduling and run evidence
- dbt in the project
- isolated-copy execution and gate verification
Asks first
Semantic decisions the Intent cannot supply. Never context Studio already holds.
- which Fabric target this work lands on, when the Domain carries both a Lakehouse and a Warehouse
Guardrails
- Build in an isolated copy. Production is read, never written.
- At least one capability this Recipe needs is not supported yet. Say so and stop rather than substituting a different approach.
What you need
- Microsoft Fabric Lakehouse, or Microsoft Fabric Warehouse.
- The jobs you want sequenced, and somewhere they are allowed to run.
- dbt 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 orchestration 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.