A missing acknowledgement leaves two possible worlds¶
GA-SYN-008 · Edition 2026.10.7 · Synthetic technical investigation
Proposition and operational question¶
The same absent acknowledgement is compatible with an uncommitted effect and a committed effect; an observer of that acknowledgement alone cannot conclude that nothing happened.
This matters when a continuing task reuses an earlier decision or representation. A final success label can conceal a different failure earlier in the trace. The proposition therefore identifies the exact observation that would refute it.
Definitions, trust and failure model¶
The destination may commit an action and its acknowledgement may be lost. The local observer sees only the acknowledgement flag. The two possible worlds differ in destination state. We assume both worlds are permitted by the communication model. No timing distribution or retry probability is supplied.
Worked synthetic trace¶
World A: the request never reaches the destination, no effect commits and no acknowledgement arrives. World B: the destination commits, then the acknowledgement is lost. Again none arrives. The local observation is identical. An honest state is unknown in both worlds until additional evidence distinguishes them. A persistent obligation can remain open while authority to retry is evaluated separately.
Negative control¶
The mutant interprets no acknowledgement as not done. That decision is false in World B. The executable case computes both worlds and identifies the false conclusion. The existing continuity exhibit goes further with a controlled witness, durable state and reconciliation; its exact result depends on its stated destination contract. It is linked as a distinct reference rather than incorporated into this abstraction.
Three evidence records and separate axes¶
| Record | Method and evidence | Scope and status |
|---|---|---|
| Research | Authored finite argument and explicit counterexample, 12 October 2026 | Analytical; limited to the definitions above |
| Reference | Author execution of the independent public teaching case uncertainty, 12 October 2026 |
Fault-tested; externally reproducible with the commands below; no independent reproduction claimed |
| Production | None for this proposition | No product conformance inferred |
Engineering maturity: reference_implemented, referring only to the disclosed teaching case. Assurance: analytical, fault_tested, externally_reproducible, each restricted to its evidence record. These labels are independent dimensions, not a score or a global verification flag. The exact machine-readable record is in the public evidence catalog. An internal author run does not count as independent review.
Limitations and open obligations¶
This argument does not prove exactly-once effects, destination idempotence, provider availability or successful compensation. An acknowledgement can itself be insufficient if it records acceptance rather than fulfillment. Production workload readiness and source inspection do not settle either world. The retained dated implementation report remains separate from this original teaching experiment.
Prior art and contribution limit¶
RPC and the end-to-end argument already establish why recovery and duplicate suppression require appropriate endpoint semantics. This case claims no new impossibility result. Its purpose is to keep uncertainty visible when persistent institutional duties are resumed by another worker. See the primary reference and the comparison guide. No priority or superiority claim follows from this example.
Reproduction and falsification¶
From the successor public source package, use CPython 3.12.14 and no external packages:
python examples/investigations/check.py --case uncertainty
python examples/investigations/check.py --case uncertainty --mutant
The first command must exit zero, with no positive violations and at least one negative violation. The second intentionally exits one and prints an actual violated case. It is a deliberate fault result, not an installation failure. Source and reproduction contract identify the exact population and scope.
Submit a counterexample, a missing assumption or a prior-art correction through the review guide. Include GA-SYN-008, edition 2026.10.7, the command, input and output, and whether the objection concerns the model, implementation or proposed product relationship. Do not send credentials or confidential customer material.
The continuity exhibit has separate executable reproduction instructions. The implementation report retains its dated source-inspection and workload-observation qualifications.