catalogue
The good as a described market class
goodDefinition`: name, description, brand reference, origin declaration, lifecycle status · `variantStructure`: variants (size, colour, flavour) and their relation to the base good
This meta-model describes items in their market aspect: the good as a saleable class with its classification codes, identifiers, units of measure, packaging hierarchy and batch structure. It is its own model because market-facing description evolves on catalogue time (assortments, codes, pack changes) independently of both the chemistry of matter (M1) and the life of individual instances (M2), and because exchange models across the catalogue need a stable good identity to transact against.
The good as a described market class
goodDefinition`: name, description, brand reference, origin declaration, lifecycle status · `variantStructure`: variants (size, colour, flavour) and their relation to the base good
How the market names and codes the good
identifierAssignment`: identifier scheme assignments at each packaging level · `classificationCoding`: classification codes from one or more schemes with validity periods
How the good is quantified and packed
packagingHierarchy`: each, inner pack, case, pallet levels and their containment · `unitOfMeasure`: net content, sale units and measure codes
Bounded production populations of the good
batchLot`: batches with production references, date ranges and recall status
Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.
Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.
Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.
CRUD procedures and interface bindings are not declared in this legacy version.
Each good record is stewarded by its seller or holder as established in the catalogue's S1 ownership model; syndication and lookup by other parties happen only under grants issued through S1/S2, with S4 providing the audit trail.