A city 311 medallion flow must ensure SLA metrics never read uncleansed tickets. How should stages be ordered?

Correct municipal medallion ordering is bronze land → silver cleanse → gold publish so consumers never read uncleansed tickets. For city 311 SLA metrics, gold must reflect tickets that have already passed cleansing and quality rules; sequencing stages with dependencies enforces that guarantee. Bronze preserves raw landing, silver applies cleanses and expectations, and gold serves SLA boards only after those steps succeed.

Sequencing silver cleanse before bronze land runs cleansing before any raw 311 tickets have landed, so bronze then lands uncleansed tickets after the cleanse step and gold publishes them without effective quality enforcement, so SLA metrics cannot be guaranteed to read only cleansed tickets.

Sequencing bronze land, then gold publish, then silver cleanse publishes gold SLA marts before cleansing, deduplication, and quarantine finish, so SLA metrics read uncleansed tickets even though they read gold, which defeats the guarantee that gold reflects cleansed data.

Sequencing gold publish, then silver cleanse, then bronze land reverses lineage entirely by building SLA aggregates before landing and cleansing any tickets, so gold has no cleansed source to reflect and SLA metrics cannot be limited to cleansed tickets.

Exam caveat: some architectures read silver for semi-curated apps; the exam point is that SLA/gold consumers that require cleansed tickets must be downstream of silver cleanse, not parallel or upstream. Operational check: land a deliberately dirty 311 batch, confirm it appears in bronze, confirm silver cleanse quarantines or fixes it, and verify gold SLA aggregates never include the uncleansed ticket_id.