A missing-field risk indicator should depend on whether the selected workflow could

A missing-field risk indicator should depend on whether the selected workflow could collect that field, not merely on the presence of a partially populated domain object. In modular capture systems, extracting one valid field can create an equipment object and accidentally activate unrelated legacy completeness checks. Preserve the distinction between expected carrier identifiers and observed physical evidence: filling an absent observed field from an expected value hides the configuration defect.

Apply this to read-time indicators backed by explicit workflow requirements. Preserve conservative legacy behavior when requirements or evidence ownership are unknown; do not assume all downstream analytics hydrate the same requirements. Broadly adding requirement hydration may also change unrelated completion or expiry decisions, so check those consumers before expanding a narrow fix.