{ "model": { "rank": 4477, "code": "thing-q107293", "model_id": "vr.tr.pitchfork", "name": "pitchfork", "purpose": "Enable an AI agent to recognise a pitchfork, assess its condition and suitability for handling loose agricultural material, and determine appropriate use and care.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q107293/", "tier": 2, "score": 75, "payload": { "layer": "wikidata", "aliases": [ "garden fork", "broadfork", "weeding fork", "winnowing fork", "hayfork" ], "aliasCount": 5, "merged": 5, "knownIn": 75, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.pitchfork", "source": { "dataset": "wikidata", "item": "Q107293", "url": "https://www.wikidata.org/wiki/Q107293", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:18:43Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.3, "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: 01a087d1-b99d-7f83-a96b-f8be862055b9\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: pitchfork\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 regist", "usd": 0, "recall": true }, "codex": { "seconds": 59.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: 01a087d1-b9aa-7211-a306-c11dcdc9c9fa\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: pitchfork\nRegistry id: vr.tr.pitchfork\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCont" } } }, "metaModel": { "id": "THING-Q107293", "registryId": "vr.tr.pitchfork", "name": "pitchfork", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q107293/", "model": { "registry_id": "vr.tr.pitchfork", "name": "pitchfork", "purpose": "Enable an AI agent to recognise a pitchfork, assess its condition and suitability for handling loose agricultural material, and determine appropriate use and care.", "definition": "A pitchfork is a long-handled, manually operated agricultural tool with projecting tines used to lift, turn and move loose material such as hay, straw or manure.", "scope_statement": "This model owns the pitchfork as a kind of manually powered agricultural fork, including its tined head, handle, material-handling action, task suitability and serviceability; product specifications and individual condition observations are evidence recorded against this kind.", "in_scope": [ "Recognition of the agricultural hand-tool sense of pitchfork", "Tine geometry, head construction, handle and head-to-handle attachment", "Lifting, carrying short distances, tossing and spreading compatible loose material", "Human effort, grip, balance and control during handling", "Condition, failure indicators, cleaning, repair and storage" ], "out_of_scope": [ "Powered loaders, tractor-mounted forks and their attachment systems", "Digging forks whose primary purpose is penetrating and loosening soil", "Rakes, shovels and other tools with different load-engagement surfaces", "Hay, straw, manure and other handled materials as independently modelled things", "Agricultural work planning and livestock management", "Pitchfork as a publication name, symbol or software-related term" ], "distinguishing_features": [ "Has a handle supporting a forked working head whose separated tines engage material while leaving gaps through which smaller particles can fall.", "Is intended primarily to lift or toss loose agricultural material, rather than dig and lever compacted soil; ambiguous garden-fork products require intended-use evidence.", "Retains a load through tine support and engagement with the material, unlike a shovel's substantially continuous blade.", "Supports lifting material on projecting tines, unlike a rake whose tooth arrangement primarily serves drawing or gathering material across a surface.", "Is directly held and powered by a person, distinguishing it from a vehicle-mounted agricultural fork attachment." ], "characteristics": [ { "name": "Declared fork type and intended material", "kind": "category", "unit_or_values": "Recorded designation and material, such as hay, straw or manure; unresolved where terminology overlaps", "why_it_matters": "Connects recognition and task selection to documented use rather than a name or tine count alone." }, { "name": "Tine count", "kind": "measurement", "unit_or_values": "Integer count", "why_it_matters": "Contributes to load support and separation without independently determining tool identity." }, { "name": "Tine geometry", "kind": "measurement", "unit_or_values": "Length, spacing and cross-sectional dimensions in mm; curvature and tip profile recorded separately", "why_it_matters": "Helps assess penetration, retention and release of the intended material." }, { "name": "Working-head width", "kind": "measurement", "unit_or_values": "mm across the outermost tines", "why_it_matters": "Affects the material engaged per stroke and clearance in confined spaces." }, { "name": "Handle length and grip form", "kind": "category", "unit_or_values": "Length recorded in mm; grip form recorded as straight, D-grip, other documented form or unknown", "why_it_matters": "Affects reach, hand placement and control during lifting and release." }, { "name": "Tool mass", "kind": "measurement", "unit_or_values": "kg", "why_it_matters": "Adds to the effort required for each loaded movement." }, { "name": "Head-to-handle attachment", "kind": "category", "unit_or_values": "Observed socket, tang, integral construction or other documented attachment, with fastening details", "why_it_matters": "Determines where to inspect for looseness and what replacement parts may be compatible." }, { "name": "Working condition", "kind": "state", "unit_or_values": "Unassessed, apparently serviceable, requires assessment or withdrawn from use; supporting defects recorded", "why_it_matters": "Separates an observation of condition from a justified decision about use." }, { "name": "Applicable use and repair instructions", "kind": "relation", "unit_or_values": "Identified manufacturer or other authoritative instructions tied to the relevant construction or product", "why_it_matters": "Provides evidence for intended use, limitations and permissible maintenance." } ], "affordances": [ "Identify whether an observed fork belongs to the agricultural pitchfork kind.", "Assess whether its tine arrangement suits a specified loose material and handling action.", "Evaluate grip, reach and available clearance for a proposed lift or toss.", "Inspect tines, handle and attachment before assigning a serviceability state.", "Select supported cleaning, storage or component-replacement actions.", "Withhold use when defects or uncertain suitability prevent a justified handling decision." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-material-fit", "name": "Identity and material fit", "description": "Establishes which agricultural fork sense is represented and how it engages its intended material.", "rationale": "Pitchfork terminology overlaps with other forks, so recognition needs both physical and intended-use evidence.", "layers": [ { "id": "agricultural-fork-boundary", "name": "Agricultural fork boundary", "description": "Distinguishes loose-material handling from soil working and powered attachment use.", "findings": [ { "id": "intended-handling-action", "name": "Intended handling action", "description": "Record evidence that the tool is intended for lifting or tossing loose material, including conflicting designations.", "questions": [ { "text": "What documented or observed intended action identifies this tool as a pitchfork?", "kind": "definition", "id": "intended-handling-action-q01" }, { "text": "Does its primary purpose place it with digging forks, rakes or powered fork attachments instead?", "kind": "boundary", "id": "intended-handling-action-q02" } ] } ] }, { "id": "load-engagement", "name": "Load engagement", "description": "Relates tine arrangement to the physical behaviour of the handled material.", "findings": [ { "id": "retention-and-release-fit", "name": "Retention and release fit", "description": "Record whether the material can be engaged, supported and released by this tine arrangement without assuming a universal carrying capacity.", "questions": [ { "text": "Which materials are specified for this fork, and where is that specification recorded?", "kind": "provenance", "id": "retention-and-release-fit-q01" }, { "text": "How do the material's particle size, fibre entanglement and moisture affect slipping through, clinging to or releasing from the tines?", "kind": "measurement", "id": "retention-and-release-fit-q02" } ] } ] } ] }, { "id": "tines-and-load-path", "name": "Tines and load path", "description": "Describes the working head and the connections that transmit a supported load to the user's hands.", "rationale": "Pitchfork performance and failure depend on tine geometry and the integrity of the head-to-handle connection.", "layers": [ { "id": "working-head-geometry", "name": "Working-head geometry", "description": "Captures the shape and arrangement of the tines that enter and support material.", "findings": [ { "id": "tine-array-profile", "name": "Tine array profile", "description": "Record tine count, length, spacing, curvature, tip form and head width as a combined working profile.", "questions": [ { "text": "What are the tine count, tine lengths, clear gaps and total working-head width?", "kind": "measurement", "id": "tine-array-profile-q01" }, { "text": "What curvature, cross-section and tip profile distinguish this head from a soil-working fork head?", "kind": "boundary", "id": "tine-array-profile-q02" } ] } ] }, { "id": "head-handle-connection", "name": "Head-handle connection", "description": "Captures how forces pass from the tines through the head and attachment into the handle.", "findings": [ { "id": "attachment-and-material-evidence", "name": "Attachment and material evidence", "description": "Record component materials, attachment form and fastening details, distinguishing visible observations from documented construction claims.", "questions": [ { "text": "How is the head connected to the handle, and which joints or fasteners carry the load?", "kind": "definition", "id": "attachment-and-material-evidence-q01" }, { "text": "What evidence establishes the tine and handle materials and any claimed heat treatment or protective finish?", "kind": "provenance", "id": "attachment-and-material-evidence-q02" } ] } ] } ] }, { "id": "manual-handling-and-control", "name": "Manual handling and control", "description": "Represents the person-powered cycle of engaging, lifting, moving and releasing material.", "rationale": "A pitchfork has no independent drive or control system; controllability comes from hand placement, leverage and the load's behaviour.", "layers": [ { "id": "grip-reach-and-balance", "name": "Grip, reach and balance", "description": "Relates handle dimensions and load position to the intended movement.", "findings": [ { "id": "loaded-handling-fit", "name": "Loaded handling fit", "description": "Record tool dimensions, mass and intended hand positions alongside the task, without assigning an unsupported safe load.", "questions": [ { "text": "What are the handle length, overall length, tool mass and available grip positions?", "kind": "measurement", "id": "loaded-handling-fit-q01" }, { "text": "Can the intended user engage, lift and release the proposed material with controlled hand placement and reach?", "kind": "action", "id": "loaded-handling-fit-q02" } ] } ] }, { "id": "movement-and-release-envelope", "name": "Movement and release envelope", "description": "Captures clearance for projecting tines, handle movement and discharged material.", "findings": [ { "id": "controlled-transfer", "name": "Controlled transfer", "description": "Record the intended transfer path and conditions that could cause tine contact, snagging or uncontrolled release.", "questions": [ { "text": "Where will the tines, handle and released material travel during the proposed lift or toss?", "kind": "measurement", "id": "controlled-transfer-q01" }, { "text": "What repositioning or change of handling action is needed to keep that path clear of people, animals and obstacles?", "kind": "action", "id": "controlled-transfer-q02" } ] } ] } ] }, { "id": "serviceability-and-care", "name": "Serviceability and care", "description": "Supports inspection, withdrawal, maintenance and storage decisions for a pointed agricultural hand tool.", "rationale": "Bent or cracked tines, damaged handles and loose attachments directly undermine load control and can expose users to the working points.", "layers": [ { "id": "defects-and-use-decision", "name": "Defects and use decision", "description": "Connects observed defects with a justified decision about further handling.", "findings": [ { "id": "tine-handle-and-joint-integrity", "name": "Tine, handle and joint integrity", "description": "Record deformation, cracks, corrosion, handle splitting or splintering, and movement at the attachment, including uncertainty about hidden damage.", "questions": [ { "text": "Which tines, handle areas or attachment points show damage, abnormal movement or deterioration?", "kind": "measurement", "id": "tine-handle-and-joint-integrity-q01" }, { "text": "Does the available inspection evidence support continued use, further assessment or withdrawal?", "kind": "action", "id": "tine-handle-and-joint-integrity-q02" } ] } ] }, { "id": "cleaning-repair-and-storage", "name": "Cleaning, repair and storage", "description": "Determines appropriate care for the component materials and exposed tine points.", "findings": [ { "id": "supported-care-actions", "name": "Supported care actions", "description": "Record cleaning needs after material handling, compatible replacement components and storage arrangements that control access to the tines.", "questions": [ { "text": "Which instructions support cleaning, corrosion treatment, handle replacement or other repairs for this construction?", "kind": "provenance", "id": "supported-care-actions-q01" }, { "text": "How should this fork be cleaned and secured between uses so residues, moisture and exposed points are addressed?", "kind": "action", "id": "supported-care-actions-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": [ "This describes the hand-tool sense, not a musical, mathematical or symbolic use of the name.", "Tine counts are indicative of common traditional designs, not defining limits; modern bedding forks may have many more tines.", "Terminology overlaps across hay, manure, bedding and garden forks; no pitchfork-specific standard or universal identifier is asserted here." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of pitchfork 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": [ "Hay fork", "Manure fork" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of pitchfork 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": [ "Lifting and loading loose hay or straw", "Distributing livestock bedding", "Removing manure mixed with bedding", "Turning and moving coarse compost materials" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of pitchfork 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": "Tine count on conventional hay forks", "typical_range": "2-3", "unit": "tines" }, { "quantity": "Tine count on conventional manure forks", "typical_range": "4-6", "unit": "tines" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of pitchfork 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": [ "Pointed tines can cause puncture injuries during use, carrying or storage.", "A cracked or splintered handle can fail under load or injure the hands.", "A loose head-to-handle connection can allow the head to detach.", "Tines can bend or break when used to pry or lift excessive loads.", "Repeated lifting and twisting can strain the back and shoulders." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of pitchfork 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": [ "Names such as hay fork, manure fork and dung fork vary with locality and intended material.", "Pitchfork is sometimes used broadly for agricultural forks, while other usage reserves it primarily for forks used with hay or straw." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of pitchfork 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": "Garden fork", "difference": "A garden fork has stout tines designed primarily to penetrate and loosen soil; a pitchfork primarily lifts loose material." }, { "name": "Rake", "difference": "A rake primarily draws or levels material with a transverse row of teeth, whereas a pitchfork supports and lifts material on projecting tines." }, { "name": "Shovel", "difference": "A shovel supports material on a continuous blade; a pitchfork uses separated tines." }, { "name": "Powered bale fork", "difference": "A powered bale fork is a machine attachment for handling bales, rather than a manually operated long-handled tool." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of pitchfork this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend pitchfork to include manure forks and other agricultural material forks, or a narrower hay-and-straw fork sense?", "Which existing Vercy models cover agricultural hand tools or forks, and what should this model inherit or link to?", "What sourced dimension ranges and tine configurations distinguish documented pitchfork variants without turning typical features into mandatory boundaries?", "Which standards, if any, specifically apply to these hand tools in the relevant jurisdictions, and what do they require or test?", "What authoritative criteria govern withdrawal, tine straightening, handle replacement and return to use for different constructions?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "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 pitchfork, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a pitchfork, assess its condition and suitability for handling loose agricultural material, and determine appropriate use and care.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: garden fork, broadfork, weeding fork, winnowing fork, hayfork.", "5 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 75 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 pitchfork, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "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": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "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": [ "garden fork", "broadfork", "weeding fork", "winnowing fork", "hayfork" ] } ], "standing": "Described in 75 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 5 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 pitchfork from another, and a pitchfork 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 pitchfork, 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 pitchfork, 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 pitchfork 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 pitchfork, 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 pitchfork, 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 pitchfork 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 pitchfork 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 pitchfork, 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 pitchfork, 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 pitchfork 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 pitchfork from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a pitchfork, 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 pitchfork, 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 pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a pitchfork is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a pitchfork, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a pitchfork, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a pitchfork is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a pitchfork, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a pitchfork, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a pitchfork is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a pitchfork, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a pitchfork, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a pitchfork is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a pitchfork is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a pitchfork, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a pitchfork, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a pitchfork is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a pitchfork, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a pitchfork, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a pitchfork 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 pitchfork 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 pitchfork between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a pitchfork, 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 pitchfork, 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 pitchfork 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 pitchfork, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a pitchfork 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 pitchfork, 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 pitchfork, 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 pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What pitchfork is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does pitchfork perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise pitchfork, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How pitchfork is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does pitchfork have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does pitchfork need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about pitchfork is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about pitchfork hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern pitchfork, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a pitchfork 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 pitchfork and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a pitchfork, 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 pitchfork, 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 pitchfork 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 pitchfork is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a pitchfork, 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 pitchfork, 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 pitchfork is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }