Food Product
Describe a governed human-food product definition with versioned declarations, evidence and separately scoped lot and safety references.
Bundle → Layer → Finding → Questions Filled
7 bundles · 14 layers · 14 findings · 42 questions
Definition and applicability Establish what the food record identifies and which profile governs its assertions.
Product definition identity
Maintain stable namespace-qualified identity and distinct revisions. GTIN and local catalog codes are optional aliases with explicit issuer and scope.
Product definition identity
Maintain stable namespace-qualified identity and distinct revisions. GTIN and local catalog codes are optional aliases with explicit issuer and scope.
- Which master product definition and revision does this food record describe? identity
- Which trade-item codes, markets and package variants map to this definition without identifying a lot or pack? relationship
- How is identity retained for loose food, missing codes or ambiguous look-alike products? exception
Food class and applicable profile
Record intended human-food role and jurisdictional category with exceptions. Product classes are not the same as food vocabulary concepts or legal permissions.
Food class and applicable profile
Record intended human-food role and jurisdictional category with exceptions. Product classes are not the same as food vocabulary concepts or legal permissions.
- Which food category, physical form and intended human use apply under the selected market profile? classification
- Which responsible operator role and reviewer substantiate the selected classification and declarations? authority
- Which profile-specific exceptions or borderline classifications require specialist review before this record can be used? constraint
Composition and allergens Describe declared content and allergen assertions without inferring a complete recipe or safety.
Declared composition
Preserve the declared list and its ordering, quantities and qualifications. Do not infer a complete recipe from a label or require an ingredient list when an evidenced exception applies.
Declared composition
Preserve the declared list and its ordering, quantities and qualifications. Do not infer a complete recipe from a label or require an ingredient list when an evidenced exception applies.
- Which ingredient entries, compound components and additive roles are declared for this revision? composition
- What do any ingredient quantities measure and which basis or declaration exception accompanies them? measurement
- Which formulation and label evidence support this declaration without exposing an unapproved recipe? provenance
Allergen and advisory assertions
Keep intentional-content declarations, cross-contact advisories, absence claims and unknowns distinct. Missing statements are not absence evidence; changes remain revision and market scoped.
Allergen and advisory assertions
Keep intentional-content declarations, cross-contact advisories, absence claims and unknowns distinct. Missing statements are not absence evidence; changes remain revision and market scoped.
- Which allergen vocabulary and declaration rules apply to the selected food and market? requirement
- Which contains, precautionary or absence statements are actually evidenced and what scope does each claim cover? evidence
- How are a missing statement, conflicting label and newer allergen declaration represented without declaring the product safe? quality
Nutrition and reference basis Preserve qualified values and the basis required to interpret them.
Qualified nutrient values
Record component, amount, unit, analytical or calculation basis and provenance. Zero, missing, below quantification and calculated estimates remain different values.
Qualified nutrient values
Record component, amount, unit, analytical or calculation basis and provenance. Zero, missing, below quantification and calculated estimates remain different values.
- Which energy and nutrient values are declared with their component definitions and units? measurement
- Were the nutrient values measured, calculated or taken from reference data and which evidence supports that method? provenance
- Which detection limits, rounding, tolerances and conflicting nutrient values prevent a defensible comparison? validation
Serving and preparation basis
Keep as-sold and as-prepared declarations distinct, including edible portion, serving quantities and reference-intake population. Conversion is conditional on compatible evidence.
Serving and preparation basis
Keep as-sold and as-prepared declarations distinct, including edible portion, serving quantities and reference-intake population. Conversion is conditional on compatible evidence.
- Does each nutrient declaration concern food as sold, as prepared or an edible portion under stated preparation assumptions? definition
- Which serving quantity, servings per package and reference-intake basis accompany a per-portion declaration? measurement
- What prevents conversion between per-mass, per-volume and per-serving values for this product? constraint
Quantity and recognition Distinguish product declarations from observed pack evidence.
Declared quantity and package context
Declared net quantity is a product assertion; observed fill or package damage belongs to an identified sample or item. Preserve nominal and measured properties separately.
Declared quantity and package context
Declared net quantity is a product assertion; observed fill or package damage belongs to an identified sample or item. Preserve nominal and measured properties separately.
- Which net, drained or count quantity is declared for this package variant and in what units? measurement
- Which package hierarchy and product-change decision link this declaration to its trade-item identifier? relationship
- Which observed quantity or package condition differs from the declaration and where is its measurement evidence retained? quality
Recognition and label observation
Capture label readings and their source without treating barcode recognition, images or OCR as authentication or proof of the current formulation.
Recognition and label observation
Capture label readings and their source without treating barcode recognition, images or OCR as authentication or proof of the current formulation.
- Which observed label, barcode and package features support the proposed product match? evidence
- Which market, size, language or formulation differences could make a visually similar package a different product revision? validation
- How are transcription errors and unverified observations retained alongside the authoritative declaration? provenance
Durability and intended use Record condition-dependent declarations without operating on food or determining fitness.
Date-marking and storage declarations
Record the meaning and precision of markings and the storage assumptions behind them. Best-before and use-by are not interchangeable. An external lot supplies actual dates; missing history never implies safe condition.
Date-marking and storage declarations
Record the meaning and precision of markings and the storage assumptions behind them. Best-before and use-by are not interchangeable. An external lot supplies actual dates; missing history never implies safe condition.
- Which durability date type, precision and marking exception apply to this product profile? temporal
- Which unopened storage conditions and supporting shelf-life evidence qualify the declaration? constraint
- Which lot or item record supplies an actual marked date and storage observation without promoting it to every product instance? relationship
Intended use and handling conditions
Represent evidenced preparation and after-opening instructions as declarations. No generic cooking procedure, automated actuation or personalized suitability is provided.
Intended use and handling conditions
Represent evidenced preparation and after-opening instructions as declarations. No generic cooking procedure, automated actuation or personalized suitability is provided.
- Which preparation, after-opening and handling instructions are declared for the intended use? process
- Which intended-consumer restrictions or prerequisites limit the use declaration? constraint
- What happens when opening time, preparation state or required storage history is unknown or contradicted? exception
Traceability and safety links Keep external lot, origin and notice references precisely scoped.
Lot applicability and origin links
Carry scoped references to traceability and origin evidence. Origin claims, ingredient origin, manufacturing location and operator address are distinct; this is not a supply-chain ledger.
Lot applicability and origin links
Carry scoped references to traceability and origin evidence. Origin claims, ingredient origin, manufacturing location and operator address are distinct; this is not a supply-chain ledger.
- Which external lots are evidenced as instances of this product revision and where is that binding mastered? relationship
- Which origin or provenance statements are declared and what exactly do their locations describe? spatial
- Which traceability evidence can the authorized reviewer retrieve when a lot binding is missing or disputed? access
Safety notice applicability
Link attributed alerts, withdrawals and recalls with population, market and time scope. No notice found is only a search result, not a safe status. Unknown lot scope cannot be silently treated as unaffected.
Safety notice applicability
Link attributed alerts, withdrawals and recalls with population, market and time scope. No notice found is only a search result, not a safe status. Unknown lot scope cannot be silently treated as unaffected.
- Which external safety notices potentially apply to this product, market or linked lot as of the recorded check? state
- What evidence makes a notice applicable, inapplicable or unresolved for a particular product revision or lot? decision
- Which issuer update or closure changes the notice linkage without deleting its history or asserting that every item is safe? lifecycle
Evidence and revision assurance Govern evidence, change history and loss-aware projections.
Declaration evidence and claims
Record label, test and certification references with claim scope and access. A certificate, ontology code or provenance digest does not independently validate a safety, nutrition or marketing claim.
Declaration evidence and claims
Record label, test and certification references with claim scope and access. A certificate, ontology code or provenance digest does not independently validate a safety, nutrition or marketing claim.
- Which source artifacts and review decisions support each nutrition, origin or other declaration claim? evidence
- Who stewards the declaration and who controls access to restricted recipes, test reports and rights-bearing evidence? ownership
- Which retention, correction and lawful disposal rules apply to superseded evidence and personal contact details? retention
Revision and projection control
Separate recorded time, declaration effective time and production applicability. Preserve coexisting market variants. Export requires a pinned mapping and explicit loss report.
Revision and projection control
Separate recorded time, declaration effective time and production applicability. Preserve coexisting market variants. Export requires a pinned mapping and explicit loss report.
- Which declaration change supersedes a revision and which existing lots remain bound to the earlier one? lifecycle
- Which event, effective and observation times are known and which date-only values must retain their precision? temporal
- Which qualifiers would be lost in a consumer or trading-partner projection and when must export be refused? interoperability
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.OBJ.FOOD
- Domain
- PHY.OBJ.FOOD
- Industry
- Cross-industry
- Tags
- foodproductphy.obj.food
- Also called
- M4
What it is Filled
One persistent product-definition entity for food or drink intended for human consumption, including unprocessed harvested food and non-prepacked products. A revision is qualified by market, formulation, packaging and effective context. The root is neither a lot nor an individual pack. It records attributable assertions and unknowns rather than determining whether a particular item is safe to consume.
In scope
- Qualified product identity, category, market and responsible-role references
- Ingredient, allergen, nutrient, quantity, storage and use declarations with evidence and exceptions
- Recognition observations, external lot and recall applicability links, revision history and permitted projections
Out of scope
- Batch manufacture, genealogy, inventory, custody, shipping and individual physical-item lifecycles
- Recipe execution, food-facility control plans, laboratory operation, medical advice or individual suitability decisions
- Issuing recalls, broadcasting notices, regulatory approval, commercial offers and price or ownership transfer
- Animal feed, plants before harvest and medicinal products; disputed legal categories require profile review
Why it exists Filled
Describe a governed human-food product definition with versioned declarations, evidence and separately scoped lot and safety references.
Distinguishing features Derived, awaiting review
- Unlike WM-OBJ-002 Product Type / Catalog Item: Candidate alignment to generic product-definition identity. This food-specific entity owns declarations and applicability, not a competing generic catalog lifecycle. Neighbor binding requires a pinned revision.
- Unlike WM-OBJ-003 Tradable Offer / Commodity view: Legacy M3 inheritance is not carried forward. Price, offer, seller terms and transactions remain external. Food need not be currently offered for sale.
- Unlike WM-OBJ-001 Physical Item Instance and external lot master: Packs and lots retain their own identity, dates, observations and custody. Local links bind them to a product revision without copying their operational lifecycle.
- Unlike WM-MAT-001 Chemical Substance and FoodOn: Ingredients can be complex food materials, not only chemical substances. Use the appropriate vocabulary reference; do not force all ingredient entries into a substance class.
- Unlike WM-OBJ-005 Medicinal Product: Market-qualified regulatory classification decides borderline products. Ingestion alone does not decide food status; supplements and specialized foods need explicit profile review.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Deletion never destroys a referenced lot, item, notice or laboratory master and cannot rescind a recall.
- Deny nonpublic access unless purpose and role grants cover the requested fields.
- Authorized authority and emergency disclosure routes follow the adopted policy and applicable duties; record basis and scope, never treat this as automatic external-write permission.
May
- Resolve a product reference: Proposed operation, not implemented. Resolve exact qualified aliases and product revisions; never merge by name, image or ingredient similarity.
- Record an evidenced declaration: Proposed operation, not implemented. Append a locally reviewed declaration linked to its source; do not change the physical label, recipe or regulatory master.
- Compare food declarations: Proposed operation, not implemented. Compare compatible revisions and expose allergen, basis and identifier-review differences; do not assign a new GTIN or notify external parties.
- Project compatible nutrient values: Proposed operation, not implemented. Calculate a labeled local projection only when basis, units and necessary conversion evidence are explicit; do not turn estimates into laboratory measurements.
- Link a scoped safety notice: Proposed operation, not implemented. Record an existing notice and evidence for applicability or unresolved scope; do not issue, close, suppress or broadcast a recall.
- Prepare an authorized food projection: Proposed operation, not implemented. Create a local recipient-scoped export with pinned mapping, freshness and loss report. Refuse omission of required allergen, date or safety context.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Role-based product data steward with namespace and mandate; no named commercial owner is prescribed
Roles
- Product data steward
- Maintain namespace and revision bindings under documented authority.
- Declaration reviewer
- Check market applicability, label evidence, exceptions and conflicting assertions.
- Food safety reviewer
- Assess notice linkage and escalate uncertainty through authorized processes; do not infer individual safety.
- Evidence custodian
- Control rights, retention, integrity and access to supporting artifacts.
- Consumer-view reader
- Read authorized public declarations with freshness and unresolved-status context.
Links to other meta-models Filled
aligned
- WM-OBJ-002 - Candidate generic product-definition alignment; pin neighbor before integration.
- FoodOn - Concept references require ontology release and mapping review; no semantic-equivalence or import claim.
- INFOODS tagnames - Nutrient identifiers need a pinned table and component definition; mappings are not implemented.
- PROV-O 2013-04-30 - Evidence attribution and derivation concepts; no implemented ontology binding.
references
- WM-OBJ-003 - Optional market-view link; legacy M3 inheritance rejected because offers and pricing remain separately mastered.
- WM-OBJ-001 - Optional observed or serialized physical pack; its condition, custody and lifecycle are external.
- WM-MAT-001 - Optional chemical ingredient reference only when suitable; complex food ingredients need other vocabularies.
- External lot and traceability master - Namespace-qualified lot-to-revision evidence; no generic lot model identifier is invented.
- External safety notice master - Issuer-owned notice, scope and revisions; execution and notification remain outside this model.
neighbor
- WM-OBJ-002 Product Type / Catalog Item - Candidate alignment to generic product-definition identity. This food-specific entity owns declarations and applicability, not a competing generic catalog lifecycle. Neighbor binding requires a pinned revision.
- WM-OBJ-003 Tradable Offer / Commodity view - Legacy M3 inheritance is not carried forward. Price, offer, seller terms and transactions remain external. Food need not be currently offered for sale.
- WM-OBJ-001 Physical Item Instance and external lot master - Packs and lots retain their own identity, dates, observations and custody. Local links bind them to a product revision without copying their operational lifecycle.
- WM-MAT-001 Chemical Substance and FoodOn - Ingredients can be complex food materials, not only chemical substances. Use the appropriate vocabulary reference; do not force all ingredient entries into a substance class.
- WM-OBJ-005 Medicinal Product - Market-qualified regulatory classification decides borderline products. Ingestion alone does not decide food status; supplements and specialized foods need explicit profile review.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier with namespace
- Governed global identifier or persistent IRI
- Dimension-assigned UUID or ULID
Direct properties required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Resolve a product reference: Proposed operation, not implemented. Resolve exact qualified aliases and product revisions; never merge by name, image or ingredient similarity.
- Record an evidenced declaration: Proposed operation, not implemented. Append a locally reviewed declaration linked to its source; do not change the physical label, recipe or regulatory master.
- Compare food declarations: Proposed operation, not implemented. Compare compatible revisions and expose allergen, basis and identifier-review differences; do not assign a new GTIN or notify external parties.
- Project compatible nutrient values: Proposed operation, not implemented. Calculate a labeled local projection only when basis, units and necessary conversion evidence are explicit; do not turn estimates into laboratory measurements.
- Link a scoped safety notice: Proposed operation, not implemented. Record an existing notice and evidence for applicability or unresolved scope; do not issue, close, suppress or broadcast a recall.
- Prepare an authorized food projection: Proposed operation, not implemented. Create a local recipient-scoped export with pinned mapping, freshness and loss report. Refuse omission of required allergen, date or safety context.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
Context of use required Filled
- EU 1169/2011 consolidated 2025-04-01 is a selected label-information example; General Food Law is read as an original act, not verified current consolidation.
- FDA allergen information applies in its stated US scope and is not merged with EU allergen categories into a universal mandatory list.
- FoodOn covers a wider food/feed vocabulary than this model. INFOODS identifiers require independent component-definition and release checks.
Sources Filled
- Food information to consumers - European Union
- General Food Law - European Union
- GTIN Management Standard - GS1
- FoodOn: A farm to fork ontology - FoodOn project
- INFOODS Food Component Identifiers (Tagnames) - Food and Agriculture Organization
- Food Allergies - U.S. Food and Drug Administration
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Date and Time on the Internet: Timestamps - Internet Engineering Task Force
Open questions
- Verify source responses outside the sandbox, current consolidated law, applicable national measures, specialist food profiles and the full international Codex source.
- Pin vocabulary releases and neighbor models, develop nested schemas and test instances covering loose food, exemptions, coexisting formulations, conflicting allergen declarations, partial dates, uncertain storage and incomplete recall scope.
- Restore independent external review before any canonical or publishable-draft promotion.
- Current complete jurisdictional law and specialist profiles, including novel foods, supplements, infant food, alcohol and non-prepacked exceptions, are not exhaustively researched.
- Independent external review is absent under the single-provider waiver.
- Direct HTTP verification is not attempted under the owner-reported sandbox block; no HTTP response status is measured. Browser content access is a separate observation.
- Nested instance schemas, enumerations, pinned neighbor bindings, FoodOn and INFOODS release mappings and executable conformance fixtures remain incomplete.
- Facility controls, microbiological criteria, laboratory sampling design, hazard limits, food-contact packaging compliance and actual lot condition are delegated, not certified.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-obj-004-food-product/spec.yaml