Check whether the outcome improved
Exercise supported dependency sequences
Import the same parent-dependent pair in each documented order or file sequence. Compare an already existing parent as a control. Record final source-to-destination identities and links, not just whether both records exist, because successful acceptance can still leave the dependent unlinked or attached through the wrong lookup value.
Check deferred and concurrent handling
Where deferred resolution or concurrent processing is supported, observe the dependent after the parent becomes available. Confirm the documented outcome and any unresolved state shown before that point. Keep source ordering and actual processing availability separate; a correctly sorted file does not prove workers resolve dependencies in that same order.
Verify genuinely unresolved references
Use a missing-parent fixture and inspect the failure or unresolved report. Confirm it points to the exact source reference and offers the supported recovery path. Retry a corrected case where appropriate and compare the final link, ensuring the process does not repeat unrelated accepted work or silently substitute a similarly named parent.
What to carry forward
Accept when supported sequences produce the intended links and missing references remain explicit and recoverable under the documented contract. Record untested concurrency or multi-file cases. A successful record count is insufficient if lookup-time behavior, final parent identity, or any deferred relationship resolution was not observed.
Technical background: PostgreSQL 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