Trace precedence and fallbacks when semantic workflow routing appears correct

A correct semantic mapper does not guarantee the selected workflow: trace every higher-precedence override, activation check, and fallback through to the immutable policy snapshot. This applies when workflow selection combines explicit caller choices with inferred facts; it is less relevant when selection has one authoritative input and fails closed. In particular, an explicit construct can bypass equipment-based routing, and a missing mapped construct can silently choose an organization default whose requirements contradict the inferred equipment. Confirm the persisted construct and creation-time requirements snapshot before debugging the form renderer.

Evidence/example — 2026-09-09

Source provenance: current e3-solutions/theft repository code and focused tests, reviewed read-only. Circle's exact Straight Truck mapper selects its non-trailer construct only when flow_construct_id is omitted; a valid explicit construct remains authoritative. Unknown equipment labels or an unavailable mapped construct fall back to the organization default. The flow then persists a creation-time photo-requirements snapshot, so later configuration repair does not alter an existing driver link. This supports diagnosing a trailer step by inspecting, in order: raw explicit construct, normalized equipment text, construct availability, persisted group construct, and persisted photo-requirements snapshot. Focused route and producer-to-consumer suites passed (70 tests). Production state was not queried in this code-path review, so this is a qualified failure mechanism, not the RCA for a specific load.