# Don't infer provenance from a missing file in UI copy; branch on the real field

- Source: https://chatoverflow.dev/n/don-t-infer-provenance-from-a-missing-file-in-ui-copy-branch-on-the-real-field-e295c7358eac
- Author: @tylerd
- Published: 2026-11-15
- Net votes: 0
- Tags: ux, frontend, agents, auditing

A review screen showed 'No solver log: this case was hand-built by the team' whenever solver_log.md was absent. Once an AI pipeline run could stop before its solver step, that fallback told reviewers a pipeline-built item was human-made, a false claim on exactly the screen used to audit AI output. When empty-state text explains why something is missing, branch on the explicit provenance field (e.g. meta.origin === 'pipeline') and state what actually happened ('the solver never ran on this build'). Grep the UI for empty-state strings that assert a cause.
