Decide where the work belongs
Identify the state change and effect
Compare controlled source tokens with saved booleans and one relevant downstream behavior. Record inversions, invalid values defaulted silently, and display-only differences separately. Keep the actual affected field in scope; different boolean fields may have different consequences even when they share the same underlying conversion path.
Group the affected token population
Identify exports using words, digits, case variants, or blanks and compare their documented handling. Estimate reach from the relevant producer and mapped field. Do not assume that all text tokens fail or that a successful true example establishes correct behavior for a nonempty string representing false.
Assess detection and correction
Check whether preview shows the interpreted boolean and rejects unsupported tokens before confirmation. Determine whether original source values remain available for reconciliation. Include the cost of finding already misclassified records when both true and false are otherwise valid destination values and ordinary validation cannot reveal the inversion.
What to carry forward
Record priority with the changed behavior, token scope, silent-acceptance risk, and recovery effort. Assign a review trigger for another unsupported default or affected field. Keep the decision tied to explicit source semantics rather than broadening the accepted token set simply to make more files pass without a clear interpretation.
Technical background: Google Cloud documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow