SYSE.34:7 - Conformance Checklist

• Old/new meaning and information-loss boundaries are explicit.
• All relevant writers/readers and engine-specific conditions are accounted for.
• Coexistence has a concrete authority and synchronization mechanism.
• Backfill cannot overwrite a later legitimate write with a stale observation.
• Partial failure, lost acknowledgement and replay have qualified behavior.
• A new reader starts only with the population and continuing invariant it needs.
• Executable return, data restore and later-event reconciliation are separately qualified.
• Contraction and permission to accept loss are not inferred from successful deployment.