Emergency management requires enrichment only after geocoding so alerts never publish without required coordinates. How should the pipeline enforce this?

Pipeline ordering constraints ensure required municipal upstream steps complete before dependent enrichments and publishes. Emergency management that must never publish alerts without required coordinates should place geocoding before enrichment/publish so alert composition cannot proceed without coordinates. Task dependencies or declarative pipeline edges encode that rule as structure, not as tribal knowledge.

Ordering enrichment after geocoding so alert publish proceeds when enrichment output validates fails because a valid enrichment output does not prove required coordinates are present, so publish can still go out without required location data. Ordering enrichment with geocoding in parallel so alert publish requires both outputs to proceed fails because enrichment runs concurrently instead of only after geocoding, so enrichment can still execute without required coordinates even if publish waits. Ordering geocoding after enrichment so alert publish checks required coordinates before sending fails because enrichment runs before geocoding, so enrichment violates the only-after-geocoding rule even if the final check blocks publish.

Exam caveat: geocoding APIs fail; design retries/quarantine for ungeocoded events rather than publishing blank coordinates, and decide whether alerts wait or route to a human-approval path. Operational check: block or fail geocoding in staging and confirm enrichment/alert publish does not emit coordinate-less alerts; succeed geocoding and confirm enrichment sees coordinates; monitor ungeocoded quarantine volume during incidents.