Atomic observation is stronger than eventual installation¶
GA-SYN-007 · Edition 2026.10.9 · Synthetic technical investigation
Proposition and operational question¶
An observer of a two-field revision sees a total of ten at both installation steps if publication switches only after the complete new revision is installed.
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 old revision is (2,8), the new revision (5,5), and total ten is the invariant. A writer stages one field at a time. A published immutable snapshot is the only observation route. A trusted atomic pointer switch exposes the completed snapshot. A reader may run after either staging step but cannot inspect unpublished memory.
Worked synthetic trace¶
After staging the first field, temporary storage is (5,8). The published snapshot remains (2,8), so the reader sees ten. After staging the second field, storage is (5,5) and the publication pointer switches. The next read also sees ten. Eventual completion alone is not enough: the observation route controls whether the intermediate violation can escape.
Negative control¶
The mutant publishes after every field update. Its first observation is (5,8), totaling thirteen. The final state is correct, so a final-state-only test would miss the failure. This counterexample uses ordinary synthetic values and a single pointer; it does not recreate MIRAGE storage, observation machinery or private routing.
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 | My execution, with AI assistance, of the independently designed public teaching case visibility, 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. My own runs do not count as independent review.
Limitations and open obligations¶
The atomic pointer and immutable snapshots are assumptions. Independent field readers, unsafe storage administrators, torn pointer writes, cross-process memory ordering and crash recovery need their own arguments. The reference cannot establish confidentiality, real distributed atomicity or complete mediation in a deployed system. Actual MIRAGE and CSSL refinements require evidence about all observation routes.
Prior art and contribution limit¶
Event ordering and consistency are established distributed-systems concerns. This case shows the difference between a valid terminal state and a valid observation history. It contributes a reviewable failure witness, not a novel atomic-commit protocol. 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 visibility
python examples/investigations/check.py --case visibility --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-007, edition 2026.10.9, 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.