Record identity and ownership
Last updated
Persist records by stable identity, not UI position. For a weapon/profile editor, the record should be keyed by a stable weapon/profile ID. Primary/secondary/menu positions are views of that identity, not storage owners.
Store with each record:
magic or valid/copied marker;
schema version;
stable identity;
logical length;
field values;
optional checksum or metadata if supported by the design.
Keep immutable factory data separate from editable persistent records so reset/copy operations have a trustworthy source.
Last updated

