{ "model": { "rank": 5344, "code": "thing-q219239", "model_id": "vr.tr.recipe", "name": "recipe", "purpose": "Enable an agent to recognise a culinary recipe, assess whether its instructions are usable in a given kitchen context, and decide whether to execute, scale, adapt or seek clarification.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q219239/", "tier": 2, "score": 68, "payload": { "layer": "wikidata", "aliases": [ "Wikibooks Cookbook article", "wild food recipe", "family recipe", "recipe for jam/confiture", "Cookstrip", "vegan recipe" ], "aliasCount": 6, "merged": 6, "knownIn": 68, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q219239", "url": "https://www.wikidata.org/wiki/Q219239", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:10:35Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.1, "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: 01a08838-1d0a-7de0-8554-b90653f29e4b\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: recipe\nSense to describe: (none recorded)\nDomain code: INF.KNW\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 register", "usd": 0, "recall": true }, "codex": { "seconds": 61.4, "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: 01a08838-1d14-7ef3-b979-0a6cfaa9b377\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: recipe\nRegistry id: vr.tr.recipe\nPlane / domain: INF / INF.KNW\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext fo" } } }, "metaModel": { "id": "THING-Q219239", "registryId": "vr.tr.recipe", "name": "recipe", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q219239/", "model": { "registry_id": "vr.tr.recipe", "name": "recipe", "purpose": "Enable an agent to recognise a culinary recipe, assess whether its instructions are usable in a given kitchen context, and decide whether to execute, scale, adapt or seek clarification.", "definition": "A recipe is a specification of ingredients or materials and operations intended to produce a particular preparation, most commonly a food or drink.", "scope_statement": "This model owns recipe as an information object specifying ingredients and preparation instructions for an intended food or drink outcome, including its variants and evidence of testing; the culinary sense is provisional because the registry records no definition.", "in_scope": [ "Intended dish or drink, recipe identity and version", "Ingredients, quantities, preparation states and functional roles", "Preparation steps, dependencies, timings and completion cues", "Required equipment, operating conditions and expected yield", "Documented substitutions, scaling limits and execution feedback" ], "out_of_scope": [ "The prepared food or drink as a physical item", "A particular cooking session and its resource consumption", "Ingredient inventories, purchasing and supply chains", "A cook's skills, credentials and personal preferences", "Cookbooks and publishing platforms as collections or services", "Industrial formulations, laboratory protocols and metaphorical recipes pending registry sense resolution" ], "distinguishing_features": [ "Specifies how ingredients are transformed into an intended food or drink outcome; a menu description primarily identifies what is served.", "Connects ingredient requirements with preparation instructions; an ingredient list alone leaves the transformation unspecified.", "Can guide repeated executions; a cooking-session record describes what happened on one occasion.", "Targets a particular preparation or adaptable family of preparations; a technique guide can teach a method without specifying a complete outcome.", "Exists independently of its resulting dish: one recipe can produce multiple batches, and one dish can have multiple recipes." ], "characteristics": [ { "name": "Intended culinary outcome", "kind": "relation", "unit_or_values": "Named food, drink or component, with distinguishing sensory or structural targets", "why_it_matters": "Gives the agent a basis for recognising the recipe and evaluating the result." }, { "name": "Declared yield", "kind": "measurement", "unit_or_values": "Servings, item count, mass or volume, with serving size where available", "why_it_matters": "Anchors ingredient quantities and exposes ambiguity when scaling." }, { "name": "Ingredient specification", "kind": "relation", "unit_or_values": "Ingredient identity, amount, unit, preparation state, role and optionality", "why_it_matters": "Determines what must be available and which substitutions could change the outcome." }, { "name": "Instruction completeness", "kind": "state", "unit_or_values": "Unassessed; explicit enough for the intended cook; dependent on tacit knowledge; blocked by missing information", "why_it_matters": "Helps the agent distinguish executable instructions from instructions requiring clarification." }, { "name": "Preparation duration", "kind": "measurement", "unit_or_values": "Minutes or hours, separating active work, unattended processing, waiting and total elapsed time", "why_it_matters": "Supports scheduling without assuming that all step durations are additive." }, { "name": "Equipment and vessel requirements", "kind": "relation", "unit_or_values": "Tool type, vessel dimensions or capacity, heat source and relevant operating mode", "why_it_matters": "Makes kitchen compatibility and equipment-dependent adjustments assessable." }, { "name": "Process endpoints", "kind": "category", "unit_or_values": "Time-based, temperature-based, sensory, dimensional or combined criteria, each attached to a step", "why_it_matters": "Distinguishes a suggested duration from evidence that a transformation is complete." }, { "name": "Testing evidence", "kind": "state", "unit_or_values": "Unknown; author-reported trial; documented trial; repeated documented trials, with conditions and outcomes", "why_it_matters": "Separates a written proposal from a recipe supported by recorded execution." }, { "name": "Variant relationship", "kind": "relation", "unit_or_values": "Source recipe or version and documented changes to ingredients, method, equipment or yield", "why_it_matters": "Preserves the basis for adaptations and prevents test results from being attributed to the wrong version." } ], "affordances": [ "Check ingredient and equipment readiness and identify missing specifications before preparation.", "Build a preparation schedule from step dependencies, active work and waiting periods.", "Scale quantities while flagging vessel, timing and process assumptions that require reassessment.", "Propose substitutions with explicit effects, evidence and unresolved constraints.", "Guide preparation using step-specific completion cues and clarification points.", "Compare a recorded result with the recipe's targets and retain changes as a traceable variant." ] }, "sources": [], "structure": { "bundles": [ { "id": "culinary-identity-and-lineage", "name": "Culinary identity and lineage", "description": "Identifies what preparation the recipe specifies and which expression or adaptation is being assessed.", "rationale": "A dish name alone cannot distinguish recipes with different methods, quantities or testing histories.", "layers": [ { "id": "intended-preparation", "name": "Intended preparation", "description": "Defines the recipe's culinary target and its boundary within a larger meal.", "findings": [ { "id": "outcome-and-component-boundary", "name": "Outcome and component boundary", "description": "Record the intended food or drink and whether the instructions produce a complete preparation or a component requiring another recipe.", "questions": [ { "text": "What food or drink should these instructions produce, and which qualities distinguish the intended result?", "kind": "definition", "id": "outcome-and-component-boundary-q01" }, { "text": "Does the recipe finish a serveable preparation or depend on separately specified components such as dough, stock or sauce?", "kind": "boundary", "id": "outcome-and-component-boundary-q02" } ] } ] }, { "id": "recipe-source-and-version", "name": "Recipe source and version", "description": "Connects the assessed instructions to their origin and subsequent changes.", "findings": [ { "id": "attributed-instructions-and-adaptations", "name": "Attributed instructions and adaptations", "description": "Record the source of the instructions and distinguish transcription, translation and culinary modification.", "questions": [ { "text": "Who supplied or published this recipe, and which dated text, recording or version contains the instructions being assessed?", "kind": "provenance", "id": "attributed-instructions-and-adaptations-q01" }, { "text": "Which ingredients, quantities or steps differ from the source recipe, and what reason is recorded for each change?", "kind": "provenance", "id": "attributed-instructions-and-adaptations-q02" } ] } ] } ] }, { "id": "ingredients-and-yield", "name": "Ingredients and yield", "description": "Specifies inputs in relation to the quantity and form of the expected output.", "rationale": "Ingredient amounts are only actionable when their units, preparation states and yield basis are understood.", "layers": [ { "id": "ingredient-meaning", "name": "Ingredient meaning", "description": "Resolves what each ingredient instruction actually requires.", "findings": [ { "id": "quantity-state-and-role", "name": "Quantity, state and role", "description": "Record amounts alongside the ingredient form and measurement stage, retaining explicit uncertainty such as an unspecified cup size.", "questions": [ { "text": "For each ingredient, what amount and unit are specified, and is it measured before or after trimming, draining, chopping or cooking?", "kind": "measurement", "id": "quantity-state-and-role-q01" }, { "text": "Which ingredient properties and roles constrain its use, such as fat content, thickening function or garnish-only status?", "kind": "definition", "id": "quantity-state-and-role-q02" } ] } ] }, { "id": "yield-and-portions", "name": "Yield and portions", "description": "Establishes the output basis against which quantities can be interpreted.", "findings": [ { "id": "declared-output-basis", "name": "Declared output basis", "description": "Separate item count, finished mass or volume and serving claims, including dependencies on portion size or processing loss.", "questions": [ { "text": "What finished quantity is expected, in items, mass or volume, and how is any stated serving count defined?", "kind": "measurement", "id": "declared-output-basis-q01" }, { "text": "Does the declared yield include optional toppings, discarded liquid or components supplied by another recipe?", "kind": "boundary", "id": "declared-output-basis-q02" } ] } ] } ] }, { "id": "preparation-logic-and-endpoints", "name": "Preparation logic and endpoints", "description": "Represents how inputs move through preparation steps toward an assessable result.", "rationale": "A sequence of verbs and durations may conceal dependencies, intermediate states and decisions that determine whether cooking succeeds.", "layers": [ { "id": "step-dependencies", "name": "Step dependencies", "description": "Makes sequencing, parallel work and intermediate preparations explicit.", "findings": [ { "id": "transformation-sequence", "name": "Transformation sequence", "description": "Connect each step to its inputs, resulting intermediate preparation and prerequisites, including divided ingredients.", "questions": [ { "text": "What must already be prepared before each step begins, and which steps can run concurrently?", "kind": "action", "id": "transformation-sequence-q01" }, { "text": "Where are ingredients divided, reserved, combined or discarded, and can each portion be followed through the instructions?", "kind": "definition", "id": "transformation-sequence-q02" } ] } ] }, { "id": "timing-and-completion", "name": "Timing and completion", "description": "Separates elapsed-time guidance from observable criteria for moving to the next step.", "findings": [ { "id": "step-endpoint-criteria", "name": "Step endpoint criteria", "description": "Record timing ranges, temperature measurement locations and sensory cues without treating an unspecified cue as an objective threshold.", "questions": [ { "text": "Which steps specify time, temperature, texture, colour or volume-change endpoints, and how should each be observed or measured?", "kind": "measurement", "id": "step-endpoint-criteria-q01" }, { "text": "What should the cook do when the stated time has elapsed but the stated completion cue has not been reached?", "kind": "action", "id": "step-endpoint-criteria-q02" } ] } ] } ] }, { "id": "kitchen-fit-and-adaptation", "name": "Kitchen fit and adaptation", "description": "Assesses whether the recipe can be used with available equipment, batch size and ingredient alternatives.", "rationale": "Changing quantities or kitchen conditions can change the preparation process as well as the shopping list.", "layers": [ { "id": "equipment-and-batch-geometry", "name": "Equipment and batch geometry", "description": "Captures equipment assumptions that affect capacity, heating and handling.", "findings": [ { "id": "vessel-and-operating-conditions", "name": "Vessel and operating conditions", "description": "Record vessel dimensions, fill depth, equipment mode and batch arrangement where specified or identified as unresolved.", "questions": [ { "text": "Which vessel sizes, equipment modes and batch arrangements are specified, and which remain unstated?", "kind": "measurement", "id": "vessel-and-operating-conditions-q01" }, { "text": "If the available equipment or desired yield differs, which quantities can be recalculated and which process settings require a trial or clarification?", "kind": "action", "id": "vessel-and-operating-conditions-q02" } ] } ] }, { "id": "substitution-and-variation", "name": "Substitution and variation", "description": "Separates documented alternatives from proposed changes.", "findings": [ { "id": "adaptation-basis-and-effects", "name": "Adaptation basis and effects", "description": "Record why a substitution is proposed, which ingredient function it must preserve and what evidence supports the resulting variant.", "questions": [ { "text": "Which substitutions or omissions are documented as tested, and under what ingredient quantities and preparation conditions?", "kind": "provenance", "id": "adaptation-basis-and-effects-q01" }, { "text": "What changes to flavour, structure, timing or suitability must be assessed before recommending an untested substitution?", "kind": "action", "id": "adaptation-basis-and-effects-q02" } ] } ] } ] }, { "id": "suitability-and-reproducibility", "name": "Suitability and reproducibility", "description": "Connects recipe-use claims and expected outcomes to evidence and unresolved limits.", "rationale": "An agent needs to distinguish culinary success, user suitability and supported handling instructions before recommending execution.", "layers": [ { "id": "dietary-and-handling-claims", "name": "Dietary and handling claims", "description": "Captures ingredient-dependent suitability claims and the evidential basis of handling instructions.", "findings": [ { "id": "claim-conditions-and-evidence", "name": "Claim conditions and evidence", "description": "Record dietary, allergen, storage and reheating claims with their conditions and sources, leaving unsupported claims unresolved.", "questions": [ { "text": "Which dietary or allergen-related claims are made, and what ingredient-label or preparation-context information is needed to assess them?", "kind": "boundary", "id": "claim-conditions-and-evidence-q01" }, { "text": "What sources support any safety-critical preparation, cooling, storage or reheating instructions for this recipe and its stated conditions?", "kind": "provenance", "id": "claim-conditions-and-evidence-q02" } ] } ] }, { "id": "execution-evidence", "name": "Execution evidence", "description": "Links trials to the precise recipe version and intended result.", "findings": [ { "id": "tested-outcomes-and-failure-signals", "name": "Tested outcomes and failure signals", "description": "Record trial conditions, departures from instructions and observed outcomes so that reproducibility can be assessed without generalising from undocumented success.", "questions": [ { "text": "Which trials used this recipe version, and what equipment, ingredient differences or procedural deviations were recorded?", "kind": "provenance", "id": "tested-outcomes-and-failure-signals-q01" }, { "text": "Which observations establish an acceptable result, and which indicate a failure requiring revision or another trial?", "kind": "measurement", "id": "tested-outcomes-and-failure-signals-q02" } ] } ] } ] }, { "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": [ "No sense is recorded; this description treats recipe as procedural information, primarily culinary, while acknowledging material and industrial uses.", "The entry should not be treated as a discipline or field of knowledge.", "No universal recipe identifier or cross-domain recipe standard is asserted; industrial standards and food regulations require application-specific research." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of recipe this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Cooking recipe", "Baking recipe", "Beverage recipe", "Preserving recipe", "Standardized food-service recipe", "Industrial process recipe" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of recipe this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Schema.org Recipe", "value_or_pattern": "Recipe", "note": "A structured-data type for describing culinary recipes, not a scheme assigning unique recipe identifiers." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of recipe 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": [ "Communicating cooking knowledge in households, cookbooks and digital collections", "Producing consistent dishes across food-service staff and locations", "Planning ingredient purchasing, portion yields and production costs", "Documenting culinary traditions and adaptations", "Specifying repeatable material preparations and manufacturing operations" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of recipe this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Ingredient mass", "typical_range": "Recipe-dependent", "unit": "g or kg" }, { "quantity": "Ingredient volume", "typical_range": "Recipe-dependent", "unit": "mL or L; customary spoon and cup measures also occur" }, { "quantity": "Process duration", "typical_range": "Operation-dependent", "unit": "s, min or h" }, { "quantity": "Process temperature", "typical_range": "Operation-dependent", "unit": "°C or °F" }, { "quantity": "Yield", "typical_range": "Recipe-dependent", "unit": "portions, item count, mass or volume" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of recipe 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": [ "Ambiguous quantities, ingredient descriptions or endpoints make results inconsistent.", "Omitted steps or unstated assumptions about equipment and skill prevent successful reproduction.", "Changing batch size without adjusting heat transfer, timing or equipment capacity changes the result.", "Inadequate processing, cooling or storage instructions can create food-safety hazards.", "Ingredient substitutions can alter allergen exposure, texture, chemical reactions or preservation effectiveness." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of recipe 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": [ "Measurement conventions differ, including metric mass, customary volumes and differing definitions of a cup or tablespoon.", "Ingredient names, availability and composition vary between regions.", "Recipes sharing a dish name may represent distinct regional or household traditions." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of recipe 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": "Procedure", "difference": "A procedure specifies actions generally; a recipe characteristically combines specified inputs with operations to produce a preparation." }, { "name": "Formula", "difference": "A formula can specify composition or proportions without the operational instructions normally associated with a recipe." }, { "name": "Dish", "difference": "A dish is a prepared food or culinary category; a recipe is information for making it." }, { "name": "Cookbook", "difference": "A cookbook is a publication that typically contains multiple recipes and supporting material." }, { "name": "Algorithm", "difference": "An algorithm specifies an effective computational procedure; a recipe may depend on sensory judgment and tacit practical knowledge." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of recipe this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.recipe cover only culinary recipes, or also technical formulations and other procedural uses of the word?", "Does an existing Vercy world model already own recipe or an equivalent concept that this entry should reference?", "What minimum combination of ingredients, method and intended outcome distinguishes a recipe from a preparation note while accommodating oral and tacit-knowledge traditions?", "Which conventions should govern ambiguous household units, unspecified serving sizes and ingredient-dependent mass-to-volume conversions?", "What evidence is sufficient to label a recipe, scaled batch or substitution as tested, and which suitability or handling claims require separate authoritative support?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a recipe, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a culinary recipe, assess whether its instructions are usable in a given kitchen context, and decide whether to execute, scale, adapt or seek clarification.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Wikibooks Cookbook article, wild food recipe, family recipe, recipe for jam/confiture, Cookstrip, vegan recipe.", "6 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 68 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a recipe, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says" ], "howItIsRecognised": [], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Wikibooks Cookbook article", "wild food recipe", "family recipe", "recipe for jam/confiture", "Cookstrip", "vegan recipe" ] } ], "standing": "Described in 68 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 6 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one recipe from another, and a recipe from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a recipe sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a recipe from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a recipe passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a recipe between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a recipe, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a recipe is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a recipe says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a recipe contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a recipe and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What recipe studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does recipe take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does recipe establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where recipe is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark recipe as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place recipe, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a recipe came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a recipe and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a recipe is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a recipe, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a recipe, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a recipe is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }