{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:31:25Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 15.0, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09561-e85b-7082-a7b0-abc9b0539c08\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Nasi kandar\nSense to describe: (none recorded)\nDomain code: PHY.MAT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 reg", "usd": 0.0, "recall": true }, "codex": { "seconds": 68.5, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09561-e857-7561-8151-f4e4943e7c5d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Nasi kandar\nRegistry id: vr.tr.nasi-kandar\nPlane / domain: PHY / PHY.MAT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:56:08+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:30+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q3520299", "registryId": "vr.tr.nasi-kandar", "name": "Nasi kandar", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.MAT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q3520299/", "model": { "registry_id": "vr.tr.nasi-kandar", "name": "Nasi kandar", "purpose": "Enable an agent to recognise nasi kandar, describe a particular serving, and assess its suitability and condition from evidence about its rice, curries, accompaniments and handling.", "definition": "Nasi kandar is a Malaysian rice meal associated especially with Penang's Indian Muslim community, consisting of steamed rice served with selected curries and side dishes, often with several curry gravies combined over the rice.", "scope_statement": "This model owns nasi kandar as a prepared meal type and its physical servings under vr.tr.nasi-kandar, including component selection, gravy application, provenance and serving condition.", "in_scope": [ "Identification as nasi kandar and evidence supporting that identification", "Rice base, selected curries, gravies and accompaniments", "Assembly choices and component quantities in an actual serving", "Ingredient traceability and dietary suitability of the complete plate", "Condition at assembly, service, takeaway and subsequent consumption" ], "out_of_scope": [ "Restaurant businesses, ownership and certification systems", "Standalone recipes and production processes for individual curries", "Cultivation and supply chains of rice, spices and livestock", "Malaysian cuisine and Indian Muslim culinary heritage as whole traditions", "Chemical substance identity, purity grades and physical constants" ], "distinguishing_features": [ "Look for a steamed-rice meal accompanied by selected curries and sides, with identification grounded in the Penang Indian Muslim culinary tradition. [Tourism Malaysia](https://www.malaysia.travel/explore/lunch-like-a-true-malaysian)", "Record whether rice and accompaniments were prepared separately and assembled for service; distinguish that arrangement from a rice dish defined by cooking its principal ingredients together.", "Use vendor identification and preparation evidence alongside appearance when distinguishing nasi kandar from other mixed-rice meals; rice with curry alone is insufficient evidence.", "Treat the actual selection of curries and sides as serving-level variation rather than assuming a single compulsory protein or fixed plate.", "Distinguish a nasi kandar serving from other food sold by a restaurant carrying nasi kandar in its name." ], "characteristics": [ { "name": "Identification evidence", "kind": "relation", "unit_or_values": "Links to menu designation, preparer account and culinary reference", "why_it_matters": "Supports recognition where several rice-and-curry meals look similar." }, { "name": "Rice preparation", "kind": "category", "unit_or_values": "Plain steamed; seasoned steamed; other documented preparation; unknown", "why_it_matters": "Describes the base without assuming all servings use an identical recipe." }, { "name": "Selected accompaniments", "kind": "relation", "unit_or_values": "Serving-specific list of curries, fried items, vegetables and other sides", "why_it_matters": "Determines what the serving actually contains." }, { "name": "Gravy composition and placement", "kind": "category", "unit_or_values": "Named gravy or gravies; mixed or separate; over rice or alongside; unknown", "why_it_matters": "Captures assembly choices and ingredients introduced independently of solid toppings." }, { "name": "Component quantities", "kind": "measurement", "unit_or_values": "g per rice, gravy and accompaniment component; count where relevant", "why_it_matters": "Allows comparison of portions and defensible serving-specific estimates." }, { "name": "Dietary suitability evidence", "kind": "state", "unit_or_values": "For each requirement: supported; contradicted; unresolved, with evidence", "why_it_matters": "Prevents assumptions based on the dish name or visible toppings." }, { "name": "Component handling history", "kind": "relation", "unit_or_values": "Rice and accompaniment batches linked to preparation, holding, assembly and storage records", "why_it_matters": "An assembled plate can combine components with different histories." }, { "name": "Serving temperature", "kind": "measurement", "unit_or_values": "Degrees Celsius by component, with observation time", "why_it_matters": "Provides evidence for condition assessment against applicable handling guidance." }, { "name": "Rice and topping texture", "kind": "state", "unit_or_values": "Observed rice firmness and gravy absorption; observed crispness of fried components", "why_it_matters": "Helps assess whether the served or transported meal meets the requested eating quality." } ], "affordances": [ "Identify a candidate serving using its designation, preparation and component evidence.", "Assemble a requested combination of rice, curries, gravies and sides.", "Compare servings while accounting for different toppings and quantities.", "Check a proposed selection against dietary requirements using complete ingredient and handling evidence.", "Assess whether holding, transport or reheating is appropriate using component histories and applicable guidance.", "Trace an uncertain ingredient or condition back to the relevant curry, gravy or rice batch." ], "agent_conduct": { "may": [ "Describe nasi kandar, its history with Penang's Indian Muslim community and its typical dishes.", "List curries and allergens such as seafood on request." ], "must_not": [ "Label a stall or dish halal without the certifying authority's approval.", "Omit seafood, egg or nut content when describing dishes for sale.", "Erase the dish's Indian Muslim origins in Penang.", "Advise holding curries at warm temperatures for long periods." ], "requires_human": [ "Changing food served to diners with religious or medical restrictions." ] }, "ethics": { "considerations": [ "Nasi kandar is heritage of Penang's Indian Muslim community.", "Halal status matters to Muslim diners and must be honest." ], "affected_parties": [ "Muslim diners", "Diners with allergies", "Stall owners" ] }, "owners": { "steward": "The stall or restaurant that serves it.", "master_systems": [] }, "visual_identification": [ "A plate of white rice flooded with several mixed curry gravies.", "Served with fried chicken, fish, egg or vegetables chosen from a counter." ], "failure_modes_and_hazards": [ "Curries held warm for many hours can grow harmful bacteria.", "Seafood curries are a risk for people with shellfish allergies." ], "what_it_is_for": [ "Nasi kandar is served in Malaysian eateries and food stalls, particularly in Penang and Indian Muslim food settings.", "Customers select curries and accompaniments to make a rice-based meal whose ingredients vary between servings.", "Dietary suitability and food condition depend on the selected dishes and their preparation and holding history." ], "standards_and_regulation": [ "The General Principles of Food Hygiene, issued by the Codex Alimentarius Commission, provide a food hygiene framework applicable to preparing and serving this meal." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q3520299: Nasi kandar", "url": "https://www.wikidata.org/wiki/Q3520299", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Nasi kandar", "url": "https://en.wikipedia.org/wiki/Nasi_kandar", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "meal-identity", "name": "Meal identity", "description": "Establish whether the candidate is nasi kandar and distinguish the meal from its vendor and neighbouring dishes.", "rationale": "A visual match to rice with curry does not establish the named culinary identity.", "layers": [ { "id": "culinary-identification", "name": "Culinary identification", "description": "Connect the serving's name and preparation to evidence about the meal tradition.", "findings": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Record who identifies the meal as nasi kandar and what supports that designation.", "questions": [ { "text": "Does the menu or preparer explicitly identify this serving as nasi kandar?", "kind": "definition", "id": "designation-evidence-q01" }, { "text": "What account of its preparation or culinary provenance supports that identification?", "kind": "provenance", "id": "designation-evidence-q02" } ] } ] }, { "id": "neighbouring-meal-boundaries", "name": "Neighbouring meal boundaries", "description": "Separate the registered meal from similar rice dishes and restaurant-level labels.", "findings": [ { "id": "boundary-evidence", "name": "Boundary evidence", "description": "Resolve identification through preparation and naming evidence rather than a single topping.", "questions": [ { "text": "What evidence distinguishes this candidate from nasi campur, nasi padang or another rice-and-curry meal?", "kind": "boundary", "id": "boundary-evidence-q01" }, { "text": "Does nasi kandar name the food being modelled, or only the establishment selling it?", "kind": "boundary", "id": "boundary-evidence-q02" } ] } ] } ] }, { "id": "rice-and-accompaniments", "name": "Rice and accompaniments", "description": "Describe the edible components present in a particular serving.", "rationale": "The dish name does not specify a fixed ingredient list or portion.", "layers": [ { "id": "rice-base", "name": "Rice base", "description": "Record the preparation and quantity of rice receiving the selected accompaniments.", "findings": [ { "id": "rice-specification", "name": "Rice specification", "description": "Identify the actual rice base without imposing an unsupported universal recipe.", "questions": [ { "text": "How was the rice prepared, and which seasonings or additions does it contain?", "kind": "definition", "id": "rice-specification-q01" }, { "text": "What mass of cooked rice is present in this serving?", "kind": "measurement", "id": "rice-specification-q02" } ] } ] }, { "id": "selected-sides", "name": "Selected sides", "description": "Resolve the chosen curries, fried items, vegetables and other accompaniments.", "findings": [ { "id": "accompaniment-inventory", "name": "Accompaniment inventory", "description": "Represent the actual plate rather than all items available at the counter.", "questions": [ { "text": "Which named accompaniments were included, and what are their principal ingredients?", "kind": "definition", "id": "accompaniment-inventory-q01" }, { "text": "What quantity of each accompaniment was served, including whether measured mass includes bones or shells?", "kind": "measurement", "id": "accompaniment-inventory-q02" } ] } ] } ] }, { "id": "gravy-and-assembly", "name": "Gravy and assembly", "description": "Capture gravy selection and how separately prepared components become one serving.", "rationale": "Gravy can change composition and eating quality without changing the visible solid toppings.", "layers": [ { "id": "gravy-selection", "name": "Gravy selection", "description": "Identify each gravy added independently of its associated meat or vegetable dish.", "findings": [ { "id": "gravy-traceability", "name": "Gravy traceability", "description": "Keep the origins of combined gravies recoverable.", "questions": [ { "text": "Which curry batches supplied the gravies added to this rice?", "kind": "provenance", "id": "gravy-traceability-q01" }, { "text": "Were gravies combined, and what amount or documented serving measure of each was used?", "kind": "measurement", "id": "gravy-traceability-q02" }, { "text": "Does the requested gravy selection introduce ingredients absent from the chosen solid accompaniments?", "kind": "boundary", "id": "gravy-traceability-q03" } ] } ] }, { "id": "serving-configuration", "name": "Serving configuration", "description": "Record placement, separation and the customer's requested assembly.", "findings": [ { "id": "assembly-request", "name": "Assembly request", "description": "Translate a serving request into explicit component and gravy placement.", "questions": [ { "text": "Should each gravy be applied over the rice, kept separate or omitted?", "kind": "action", "id": "assembly-request-q01" }, { "text": "What does the preparer mean by any local gravy-quantity term used in the order?", "kind": "definition", "id": "assembly-request-q02" } ] } ] } ] }, { "id": "ingredient-suitability", "name": "Ingredient suitability", "description": "Evaluate the complete serving against declared dietary requirements.", "rationale": "Visible toppings, culinary association and restaurant naming cannot establish the suitability of every gravy and side.", "layers": [ { "id": "ingredient-resolution", "name": "Ingredient resolution", "description": "Trace ingredients through rice, curry bases, gravies and garnishes.", "findings": [ { "id": "complete-serving-ingredients", "name": "Complete serving ingredients", "description": "Include ingredients that are not identifiable by looking at the plate.", "questions": [ { "text": "What ingredient evidence is available for every selected gravy, side and rice preparation?", "kind": "provenance", "id": "complete-serving-ingredients-q01" }, { "text": "Which ingredients remain unresolved for the eater's stated restrictions?", "kind": "boundary", "id": "complete-serving-ingredients-q02" } ] } ] }, { "id": "preparation-and-claims", "name": "Preparation and claims", "description": "Connect suitability claims to their scope and to shared preparation or serving practices.", "findings": [ { "id": "suitability-decision", "name": "Suitability decision", "description": "Distinguish documented suitability from assumptions about a dish or vendor.", "questions": [ { "text": "What evidence supports any halal or other dietary claim, and does it cover this serving's components?", "kind": "provenance", "id": "suitability-decision-q01" }, { "text": "Are shared ladles, utensils or cooking media relevant to the stated restriction?", "kind": "boundary", "id": "suitability-decision-q02" }, { "text": "Which selection changes or further checks are needed before fulfilling the dietary request?", "kind": "action", "id": "suitability-decision-q03" } ] } ] } ] }, { "id": "serving-condition", "name": "Serving condition", "description": "Assess the assembled meal through component histories and changes after gravy application.", "rationale": "Fresh assembly does not establish when the rice and curries were prepared, and transport can alter their condition.", "layers": [ { "id": "component-time-and-temperature", "name": "Component time and temperature", "description": "Retain separate handling evidence for rice, curries and other selected components.", "findings": [ { "id": "handling-evidence", "name": "Handling evidence", "description": "Support a handling decision without assigning a universal shelf life to nasi kandar.", "questions": [ { "text": "When were the rice and selected accompaniments prepared, and what holding or storage history is recorded?", "kind": "provenance", "id": "handling-evidence-q01" }, { "text": "What component temperatures were measured, where and at what times?", "kind": "measurement", "id": "handling-evidence-q02" }, { "text": "Under applicable guidance, does the documented history support serving, continued storage or reheating?", "kind": "action", "id": "handling-evidence-q03" } ] } ] }, { "id": "quality-after-assembly", "name": "Quality after assembly", "description": "Observe changes to rice and toppings during service or takeaway.", "findings": [ { "id": "gravy-contact-quality", "name": "Gravy contact quality", "description": "Assess the requested eating quality using the actual duration and arrangement of component contact.", "questions": [ { "text": "How long has gravy contacted the rice and any fried accompaniments?", "kind": "measurement", "id": "gravy-contact-quality-q01" }, { "text": "What rice texture, gravy absorption and topping crispness are observed at consumption?", "kind": "measurement", "id": "gravy-contact-quality-q02" }, { "text": "Would separately packing gravy or fried components better satisfy this takeaway order?", "kind": "action", "id": "gravy-contact-quality-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is a prepared meal category, not a single chemical substance or material with fixed composition.", "There is no single recipe or portion size from which dependable nutritional measurements can be inferred.", "Historical origin details and claims about named regional subtypes require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Nasi kandar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Sold in Indian Muslim restaurants and food stalls as a customizable meal.", "Served with selected accompaniments such as chicken, beef, fish, squid, eggs and vegetables." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Nasi kandar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Cooked rice and accompaniments can become unsafe through improper storage or holding.", "Allergens depend on the selected dishes and may include fish, shellfish, eggs, milk and peanuts.", "Shared serving utensils can transfer allergens between dishes." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Nasi kandar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Closely associated with Penang but sold throughout Malaysia.", "Available curries, accompaniments and gravy combinations vary between establishments." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Nasi kandar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Nasi campur", "difference": "A broader mixed-rice meal category with selected side dishes; nasi kandar specifically belongs to the Malaysian Indian Muslim rice-and-curry tradition." }, { "name": "Nasi lemak", "difference": "Defined by rice cooked with coconut milk, whereas nasi kandar is defined by its rice-and-curry serving tradition." }, { "name": "Biryani", "difference": "Defined by a seasoned rice preparation, often cooked with meat; nasi kandar generally combines separately cooked rice with selected curries and accompaniments." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Nasi kandar this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which documented criteria distinguish nasi kandar from neighbouring mixed-rice traditions when vendor naming and preparation evidence disagree?", "How do practitioners treat seasoned-rice, single-gravy and meat-free versions when defining the meal's boundaries?", "Which local terms for gravy mixing and quantity have consistent meanings, and which require vendor-specific interpretation?", "What component-level ingredient and shared-utensil evidence can vendors reliably provide for a particular serving?", "Which jurisdiction-specific handling guidance and measured component histories are needed to support storage or reheating decisions?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 15, "questions": 29 } }