Data, catalogs and contracts
Keep product definitions, runtime records and chain state connected without making them interchangeable.
Catalog authority
Item, recipe and facility definitions are published through PostgreSQL public.definition. CSV files are seed inputs; example arrays in planning JSON are not the complete runtime catalog. Public definition snapshots and internal consumers must agree after a catalog update.
A published item encyclopedia should be generated from a verified release snapshot, with a version, rather than silently reflecting an arbitrary live database or copying sample data.
Gno modules
The current realm source directories include admin, craft, equipment, game_vault, game_world, item, personal_world and user. Use each module’s gnomod.toml as the authoritative import path. A source module list does not prove which revision is deployed to a network.
Contract calls must keep wrappers, public APIs, storage semantics and downstream consumers aligned. Archived acr, chunk or block documentation does not establish a current call contract.
Safe integration
Use package exports rather than another package’s source or build internals. Validate both producers and consumers when changing a payload, enum or protocol. A generated type alone does not prove the serializer, server and client agree.