Sui Move Source Style

Make each file clearly communicate what it owns, who may change it, and how its state is created, updated, and retired, without requiring the reader to trace unrelated modules or call sites.

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

Apply the standard

1. Establish the package's edition, compiler and dependency pins, publication status, local instructions, and existing section vocabulary. Context is complete when each is known or recorded as an evidence gap.
2. Inspect every changed declaration and function in production and test code, including observable evaluation, abort, mutation, transfer, and emission order.
3. Read every matching reference below, then apply all relevant rules while preserving target behavior and published compatibility.
4. Finish only when every changed file has been checked for ownership, organization, imports, names, visibility, abilities, signatures, errors, syntax, locals, API vocabulary, documentation, and test-only seams.