{ "model": { "rank": 5170, "code": "thing-q193142", "model_id": "vr.tr.file", "name": "file", "purpose": "Enable an agent to recognise a material-removal file, assess its working condition and suitability, and determine how it may be used and maintained.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q193142/", "tier": 2, "score": 69, "payload": { "layer": "wikidata", "aliases": [ "triangular file", "nail file", "murça (lime)", "diamond file", "saw files", "riffler file" ], "aliasCount": 6, "merged": 6, "knownIn": 69, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.file", "source": { "dataset": "wikidata", "item": "Q193142", "url": "https://www.wikidata.org/wiki/Q193142", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:49:10Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 16.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: 01a08824-a20c-7911-973c-4fea4fb9bd87\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: file\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 registered", "usd": 0, "recall": true }, "codex": { "seconds": 53.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: 01a08824-a1ff-7f01-b535-257dc3569ff5\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: file\nRegistry id: vr.tr.file\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for th" } } }, "metaModel": { "id": "THING-Q193142", "registryId": "vr.tr.file", "name": "file", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q193142/", "model": { "registry_id": "vr.tr.file", "name": "file", "purpose": "Enable an agent to recognise a material-removal file, assess its working condition and suitability, and determine how it may be used and maintained.", "definition": "A file is a material-removal tool with a working surface of cutting teeth or bonded abrasive particles, usually operated by hand to shape, size, deburr or finish a workpiece.", "scope_statement": "This model provisionally interprets file in PHY / PHY.OBJ as a physical filing tool with a toothed or abrasive working surface, covering the tool kind and the properties needed to assess individual examples; the intended registry sense remains unconfirmed.", "in_scope": [ "Hand files and file elements designed for guided or powered filing", "Working-face geometry, tooth pattern or abrasive surface, and cutting direction", "Compatibility with workpiece materials and required finish", "Tang, handle, mounting interface and force transmission", "Wear, clogging, damage, cleaning and storage" ], "out_of_scope": [ "Digital files and their storage formats", "Document folders and collections of records", "Complete powered filing machines and their drive systems", "Workpieces and the manufacturing processes that specify their final geometry", "Grinding wheels, abrasive sheets, saws and milling cutters", "Rasp-specific requirements pending confirmation of the registry boundary" ], "distinguishing_features": [ "Its working surface removes material through successive filing strokes; a saw primarily cuts a kerf using teeth along an edge or cutting band.", "The shape of its working faces determines access to flats, holes, grooves or internal corners, unlike an abrasive sheet whose support largely determines its working shape.", "A conventional toothed file presents rows or patterns of cutting teeth on a working face; individually raised rasp teeth require an explicit subtype or neighbouring-model decision.", "A tang, integral grip or machine mounting interface transmits the filing force; the file element is distinct from any mechanism that drives it.", "The name refers here to a physical material-removal tool rather than an information object or document container." ], "characteristics": [ { "name": "Working-surface technology", "kind": "category", "unit_or_values": "Toothed metal; bonded abrasive; other documented construction; unknown", "why_it_matters": "Determines the relevant cutting, compatibility, cleaning and wear questions." }, { "name": "Cross-section and longitudinal profile", "kind": "category", "unit_or_values": "Flat, round, half-round, square, triangular or other documented section; parallel or tapered", "why_it_matters": "Determines which surfaces and confined features the file can reach and shape." }, { "name": "Working dimensions", "kind": "measurement", "unit_or_values": "Working length, width, thickness or diameter in mm, with measurement locations stated", "why_it_matters": "Supports access, fit and stroke-clearance decisions without confusing working length with overall length." }, { "name": "Cut designation", "kind": "category", "unit_or_values": "Manufacturer or standard designation, including tooth pattern and coarseness; unknown if unverified", "why_it_matters": "Supports selection for removal rate and finish while preserving differences between grading systems." }, { "name": "Cutting and non-cutting faces", "kind": "category", "unit_or_values": "Face-by-face map of toothed, abrasive and safe surfaces", "why_it_matters": "Determines whether adjacent workpiece surfaces can be protected during filing." }, { "name": "Workpiece compatibility", "kind": "relation", "unit_or_values": "Documented compatible materials and material conditions, with exclusions", "why_it_matters": "Prevents selecting a file that cuts poorly, loads rapidly or damages the intended surface." }, { "name": "Grip or mounting condition", "kind": "state", "unit_or_values": "Secure; loose; missing required handle; damaged; incompatible; unassessed", "why_it_matters": "Determines whether filing forces can be applied with controlled retention." }, { "name": "Working-surface condition", "kind": "state", "unit_or_values": "Sharp; worn; loaded; pinned with embedded material; chipped; corroded; unassessed", "why_it_matters": "Supports cleaning, restricted-use and replacement decisions." } ], "affordances": [ "Select a file for a particular material, feature geometry and finish requirement.", "Orient its cutting and safe faces to shape a target surface while protecting adjacent surfaces.", "Fit and verify a compatible handle or machine mounting.", "Inspect the working surface and retention interface before use.", "Clean accumulated material using a method appropriate to the working surface.", "Withdraw, replace or segregate a file when damage or contamination makes it unsuitable." ] }, "sources": [], "structure": { "bundles": [ { "id": "file-identity-and-boundaries", "name": "File identity and boundaries", "description": "Establish the physical filing-tool sense and separate the tool kind from neighbouring tools and product records.", "rationale": "The registry name lacks a definition and can refer to unrelated physical and informational things.", "layers": [ { "id": "filing-tool-sense", "name": "Filing-tool sense", "description": "Identify the operating role that makes an item a file.", "findings": [ { "id": "material-removal-by-filing", "name": "Material removal by filing", "description": "Record evidence that the item is intended to remove material through a filing action using a working face.", "questions": [ { "text": "Does the registry source identify a material-removal tool, and what definition supports that interpretation?", "kind": "definition", "id": "material-removal-by-filing-q01" }, { "text": "What observable working surface and intended motion distinguish this item from a saw, abrasive sheet or other cutting tool?", "kind": "boundary", "id": "material-removal-by-filing-q02" } ] } ] }, { "id": "file-family-membership", "name": "File family membership", "description": "Resolve subtype coverage and distinguish class information from a specific product or unit.", "findings": [ { "id": "subtypes-and-neighbouring-tools", "name": "Subtypes and neighbouring tools", "description": "Record whether abrasive files, needle files, rotary-labelled tools and rasps belong within this entry or require links to neighbouring models.", "questions": [ { "text": "Which file subtypes are explicitly covered by the registry source, and which remain uncertain?", "kind": "boundary", "id": "subtypes-and-neighbouring-tools-q01" }, { "text": "Does a supplied name identify a file kind, a manufacturer's product designation or an individual tool?", "kind": "provenance", "id": "subtypes-and-neighbouring-tools-q02" } ] } ] } ] }, { "id": "working-geometry-and-cut", "name": "Working geometry and cut", "description": "Describe the surfaces that contact the workpiece and how their geometry constrains filing.", "rationale": "A file must fit the feature being worked and expose an appropriate cutting surface without damaging neighbouring faces.", "layers": [ { "id": "section-profile-and-access", "name": "Section, profile and access", "description": "Capture cross-section, taper and usable working dimensions.", "findings": [ { "id": "feature-fit", "name": "Feature fit", "description": "Relate the file's measured geometry to the opening, corner, curve or flat it must work.", "questions": [ { "text": "What are the working length and cross-sectional dimensions in mm, and where along any taper were they measured?", "kind": "measurement", "id": "feature-fit-q01" }, { "text": "Can the working section enter the target feature and complete the required stroke without unintended contact?", "kind": "action", "id": "feature-fit-q02" } ] } ] }, { "id": "cutting-face-layout", "name": "Cutting-face layout", "description": "Capture tooth or abrasive construction, cut designation and non-cutting faces.", "findings": [ { "id": "surface-cut-and-safe-faces", "name": "Surface cut and safe faces", "description": "Map the working faces and retain the source-specific meaning of tooth pattern, coarseness or abrasive grade.", "questions": [ { "text": "Which manufacturer documentation or issuing-body standard defines the stated cut or abrasive grade?", "kind": "provenance", "id": "surface-cut-and-safe-faces-q01" }, { "text": "Which faces and edges cut, which are intentionally safe, and what cutting direction is specified?", "kind": "definition", "id": "surface-cut-and-safe-faces-q02" } ] } ] } ] }, { "id": "workpiece-fit-and-operation", "name": "Workpiece fit and operation", "description": "Connect file selection and handling to the material, desired result and means of applying force.", "rationale": "Matching the tool's shape alone does not establish that it can cut the material or be operated with adequate control.", "layers": [ { "id": "material-and-finish-selection", "name": "Material and finish selection", "description": "Assess compatibility with the workpiece material and intended filing result.", "findings": [ { "id": "cutting-suitability", "name": "Cutting suitability", "description": "Record supported material applications and the evidence needed to judge removal and finish performance.", "questions": [ { "text": "What documented guidance supports using this working-surface construction on the workpiece's material and hardness condition?", "kind": "provenance", "id": "cutting-suitability-q01" }, { "text": "What removal allowance and surface-finish acceptance criteria must the selected file satisfy?", "kind": "measurement", "id": "cutting-suitability-q02" } ] } ] }, { "id": "handling-and-stroke-control", "name": "Handling and stroke control", "description": "Assess the grip or mounting interface and the permitted filing motion.", "findings": [ { "id": "retention-and-force-path", "name": "Retention and force path", "description": "Record how the file is held, whether its interface is secure and what operating limits apply to that form.", "questions": [ { "text": "Does this file require a separate handle or machine holder, and is the fitted interface compatible and secure?", "kind": "action", "id": "retention-and-force-path-q01" }, { "text": "What guidance specifies cutting stroke, applied pressure and, for a driven file, permitted stroke or speed?", "kind": "provenance", "id": "retention-and-force-path-q02" } ] } ] } ] }, { "id": "file-condition-and-care", "name": "File condition and care", "description": "Assess cutting-surface deterioration, retained debris and serviceability.", "rationale": "Embedded chips, worn cutting surfaces and damaged retention features change both the achievable finish and the appropriate next action.", "layers": [ { "id": "wear-loading-and-damage", "name": "Wear, loading and damage", "description": "Distinguish removable accumulation from deterioration that cleaning cannot remedy.", "findings": [ { "id": "serviceability-assessment", "name": "Serviceability assessment", "description": "Record tooth or abrasive condition, embedded material, body damage and observed cutting behaviour.", "questions": [ { "text": "Is poor cutting associated with retained chips, worn teeth or abrasive, surface damage, or an unsuitable workpiece material?", "kind": "definition", "id": "serviceability-assessment-q01" }, { "text": "What inspection or controlled trial supports cleaning, continued use, restricted use or withdrawal?", "kind": "action", "id": "serviceability-assessment-q02" } ] } ] }, { "id": "cleaning-and-preservation", "name": "Cleaning and preservation", "description": "Determine care methods that preserve the particular working surface and prevent harmful contamination.", "findings": [ { "id": "construction-specific-care", "name": "Construction-specific care", "description": "Tie cleaning, corrosion protection and storage choices to the file construction and subsequent workpiece use.", "questions": [ { "text": "Which cleaning method is supported for this tooth pattern or abrasive construction without damaging the working surface?", "kind": "action", "id": "construction-specific-care-q01" }, { "text": "How should the file be stored or segregated to prevent cutting-face damage, corrosion and transfer of retained workpiece material?", "kind": "action", "id": "construction-specific-care-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": [ "The tool sense is inferred from the physical-object domain and batch context; no recorded sense explicitly confirms it.", "The length range is approximate and describes common workshop hand files, not every variety.", "Applicable dimensional standards and cut-grade specifications require verification; none are asserted here." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of file 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": [ "Flat file", "Half-round file", "Round file", "Square file", "Triangular file", "Needle file" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of file 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": [ "Deburring cut metal edges.", "Fitting mating parts by controlled removal of small amounts of material.", "Shaping slots, holes and curved surfaces.", "Sharpening suitable saw teeth and cutting tools.", "Finishing small components in jewellery and precision work." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of file 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": "Working body length, generally excluding the tang", "typical_range": "100-350 for common workshop hand files; miniature and specialist files fall outside this range", "unit": "mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of file 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": [ "Chips lodged between teeth can scratch the workpiece and reduce cutting effectiveness.", "Worn or damaged teeth reduce cutting performance.", "Hardened file bodies can fracture if bent, struck or used as pry bars.", "An exposed tang on a file intended for a handle can puncture the hand.", "Sharp workpiece edges, swarf and filing dust can cause injury or exposure hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of file 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": [ "Swiss-pattern and American-pattern files use different conventions for describing cut coarseness; their grades should not be assumed equivalent.", "Nominal file lengths may be sold in millimetres or inches." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of file 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": "Rasp", "difference": "A rasp generally has individually raised, separated teeth, whereas a conventional file has rows of cut teeth; terminology sometimes groups rasps within files." }, { "name": "Abrasive stone", "difference": "A stone removes material through abrasive grains in its body rather than the cut teeth of a conventional file; diamond-coated files blur this boundary." }, { "name": "Burr", "difference": "A rotary burr cuts while rotating in a powered spindle, whereas a hand file normally cuts during linear strokes." }, { "name": "Computer file", "difference": "A computer file is a named collection of stored digital data, not a physical material-removal tool." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of file this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the original registry source confirm the material-removal tool sense of file?", "Does the registry include rasps, abrasive files and powered file elements within this thing, or assign them to neighbouring entries?", "Which issuing-body standards define applicable file dimensions, cut designations and testing methods, and how do manufacturer grading systems relate to them?", "What authoritative guidance establishes material compatibility and operating limits for each included file construction?", "Which observable wear, damage and retention conditions justify withdrawal, and which can be resolved by documented maintenance?" ], "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 file, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a material-removal file, assess its working condition and suitability, and determine how it may be used and maintained.", "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: triangular file, nail file, murça (lime), diamond file, saw files, riffler file.", "6 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 69 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 file, 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": [ "triangular file", "nail file", "murça (lime)", "diamond file", "saw files", "riffler file" ] } ], "standing": "Described in 69 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 file from another, and a file 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 file, 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 file, 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 file 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 file, 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 file, 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 file 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 file 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 file, 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 file, 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 file 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 file from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a file, 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 file, 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 file 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 file 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 file, 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 file, 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 file 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 file is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a file, 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 file, 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 file 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 file is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a file, 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 file, 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 file 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 file 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 file is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a file, 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 file, 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 file 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 file 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 file, 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 file, 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 file 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 file 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 file between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a file, 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 file, 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 file 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 file, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a file 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 file, 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 file, 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 file 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 file 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 file 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 file, 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 file 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 file 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 file 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 file 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 file 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 file, 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 file 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 file and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a file, 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 file, 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 file 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 file is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a file, 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 file, 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 file 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 } } } }