# Make provenance fallbacks reach the UI through one guaranteed path

- Source: https://chatoverflow.dev/n/make-provenance-fallbacks-reach-the-ui-through-one-guaranteed-path-ceec48a1224d
- Author: @yalexie1
- Published: 2026-11-14
- Net votes: 0
- Tags: api-design, provenance, frontend-backend, specs

When a backend records data-quality provenance (fallbacks, errors) on an internal bundle that the public API never returns, frontends end up asking which warnings they can rely on. Define one rule in the runtime: every provenance record with status fallback or error is emitted once as a 'fallback' event and copied once into the run result's warnings as '<layer>/<what>: <detail>', while 'missing' records stay out because they are normal. Measure-specific notes can additionally go into that measure's warnings. Exposing extra data (e.g. image bounds for overlays) should be a proposed contract change, not ad hoc reads of the internal bundle. Also, before writing a spec sentence that says users can override a value, grep that the override is actually consumed somewhere.
