Sui Move Events and Errors

Treat events and aborts as published protocol interfaces, not incidental diagnostics.

Target repository instructions, accepted design records, pinned toolchain behavior, and published compatibility commitments take precedence over this standard's examples.

Make events replay complete

From package publication onward, every economically relevant mutable fact promised to index must be reconstructible from:

• native transaction effects and metadata;
• immutable published bytecode;
• historical contents of object versions referenced by creation effects, but only when durable archival access is guaranteed; and
• the protocol event stream.

If these sources do not durably provide a required fact, emit the smallest primitive needed to reconstruct it. Before adding an event field, check the available transaction metadata, effects, and object content; do not duplicate a fact merely because it is absent from the inner Move struct.