Blue Heron Rides daily release
The operations lead needs a release review for rides-r42. Bronze trips contains an unfinished trip, missing rider and fare values, and a valid zero-rider trip. Deliver accepted silver detail, one gold row per route, a retry audit and reconciled publication totals. The daily job must publish after quality succeeds, use explicit production target configuration and support a repair without replaying successful ingestion.
Blue Heron Rides has reviewed release rides-r42 for its daily route mart. Before promotion, the operations lead wants evidence that the output excludes incomplete measurements, preserves zero-rider trips and remains stable when the publication task retries after a commit.
Build persistent silver and gold tables, replay the gold write with replacement semantics and save a reconciliation report. A successful SQL cell is not enough: the published trip and fare totals must agree with the accepted detail. The last step asks you to use that evidence in a production release decision involving dependencies, target configuration and a failed task. The browser does not deploy a bundle or schedule a cloud job. You are building the data checks that such a workflow needs and choosing how to promote and recover it without changing the reviewed transformation code.