{ "model": { "rank": 5108, "code": "thing-q186713", "model_id": "vr.tr.simple-machine", "name": "simple machine", "purpose": "Enable an AI agent to recognise a simple machine, assess how it transmits force and motion, and determine whether a proposed use is mechanically feasible and safe.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q186713/", "tier": 2, "score": 70, "payload": { "layer": "wikidata", "aliases": [ "reach extender" ], "aliasCount": 1, "merged": 1, "knownIn": 70, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q186713", "url": "https://www.wikidata.org/wiki/Q186713", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:41:00Z", "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: 01a0881c-f957-78b2-a4bb-7a19bffae49d\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: simple machine\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 ", "usd": 0, "recall": true }, "codex": { "seconds": 65.2, "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: 01a0881c-f949-7a21-816a-a8a7e401a9fd\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: simple machine\nRegistry id: vr.tr.simple-machine\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } } }, "metaModel": { "id": "THING-Q186713", "registryId": "vr.tr.simple-machine", "name": "simple machine", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q186713/", "model": { "registry_id": "vr.tr.simple-machine", "name": "simple machine", "purpose": "Enable an AI agent to recognise a simple machine, assess how it transmits force and motion, and determine whether a proposed use is mechanically feasible and safe.", "definition": "A simple machine is an elementary mechanical device that changes the magnitude or direction of an applied force through its geometry, exchanging force for displacement without increasing the available mechanical work.", "scope_statement": "This model owns the registered kind vr.tr.simple-machine in PHY / PHY.OBJ: elementary mechanical arrangements conventionally classified as lever, wheel and axle, pulley, inclined plane, wedge, or screw, including the geometry, constraints, and operating conditions needed to assess their use.", "in_scope": [ "The six conventional simple-machine families and the physical arrangements that instantiate them", "Effort, load, support, contact, and motion relationships", "Mechanical advantage, displacement trade-offs, work transfer, and frictional losses", "Configuration-dependent operating limits and mechanical condition", "Use as an elementary mechanism within a larger machine" ], "out_of_scope": [ "Complete compound machines and coordination between their constituent mechanisms", "Motors, engines, and other sources of input energy", "Product ranges, manufacturer catalogues, and individual asset administration", "Detailed structural design and material constitutive models", "Application-specific lifting, transport, or manufacturing procedures" ], "distinguishing_features": [ "An arrangement must have identifiable effort and load interactions connected by geometry and constraints; merely being a rigid object does not establish a simple-machine role.", "Its elementary operating principle must be describable through a conventional simple-machine family; commercial simplicity or few parts alone is insufficient.", "It redirects force or exchanges force or torque against displacement or rotation without supplying energy independently.", "A complete device containing several coordinated elementary mechanisms is assessed as a compound machine, while its constituent simple-machine roles remain identifiable.", "Classification depends on use and configuration: the same bar can serve as a lever when supported at a fulcrum or remain an unconfigured structural member." ], "characteristics": [ { "name": "Simple-machine family", "kind": "category", "unit_or_values": "lever | wheel-and-axle | pulley | inclined-plane | wedge | screw; multiple roles may be recorded", "why_it_matters": "Selects the relevant geometry, motion constraints, and performance relationships." }, { "name": "Effort-load-support arrangement", "kind": "relation", "unit_or_values": "Identified input, output, fulcrum or support, contacts, and force directions", "why_it_matters": "Makes classification and force analysis depend on the actual configuration." }, { "name": "Effective geometry", "kind": "measurement", "unit_or_values": "Perpendicular moment arms, radii, travel lengths, rise, and screw lead in m; angles in degrees or rad", "why_it_matters": "Determines the ideal relationship between input and output motion and effort." }, { "name": "Input effort and output resistance", "kind": "measurement", "unit_or_values": "Force in N or torque in N·m, with direction and operating condition", "why_it_matters": "Distinguishes the required effort from the load and supports comparison with operating limits." }, { "name": "Motion ratio", "kind": "measurement", "unit_or_values": "Input travel/output travel, dimensionless for matched motion types; m/revolution for rotary-to-linear motion", "why_it_matters": "Exposes the displacement cost of force multiplication." }, { "name": "Mechanical advantage", "kind": "measurement", "unit_or_values": "Dimensionless output-force/input-force ratio with measurement points and ideal or actual basis stated", "why_it_matters": "Prevents an ambiguous advantage value from being used across different configurations or motion types." }, { "name": "Energy-transfer efficiency", "kind": "measurement", "unit_or_values": "Useful output work/input work, dimensionless or %, over a stated operation", "why_it_matters": "Separates ideal geometric predictions from friction and other losses." }, { "name": "Backdriving behaviour", "kind": "state", "unit_or_values": "backdrivable | holds under specified conditions | separately restrained | unassessed", "why_it_matters": "Determines whether removing effort can allow the load to move." }, { "name": "Condition of load-bearing interfaces", "kind": "state", "unit_or_values": "serviceable | worn | deformed | cracked | seized | loose | unassessed, with affected interface", "why_it_matters": "Connects observable condition to loss of support, altered motion, or failure." }, { "name": "Verified operating envelope", "kind": "relation", "unit_or_values": "Configuration linked to documented force or torque limits, travel limits, support requirements, and evidence", "why_it_matters": "Prevents geometry-based calculations from being mistaken for proof of load capacity." } ], "affordances": [ "Classify an observed arrangement by tracing effort, load, support, and permitted motion.", "Estimate ideal effort and travel requirements from a stated configuration.", "Compare measured performance with ideal predictions to identify losses or configuration errors.", "Assess whether a load can backdrive the mechanism or requires independent restraint.", "Identify inspection and maintenance needs at pivots, threads, grooves, edges, and supporting contacts.", "Determine whether available evidence supports a proposed load and configuration or requires further verification." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-mechanism-boundary", "name": "Identity and mechanism boundary", "description": "Establishes which simple-machine role an arrangement performs and where that role begins and ends.", "rationale": "Simple-machine identity depends on mechanical relationships rather than appearance, product name, or part count.", "layers": [ { "id": "family-recognition", "name": "Family recognition", "description": "Connects observable constraints and motion to the conventional families.", "findings": [ { "id": "operating-role", "name": "Operating role", "description": "Record the family assignment through the arrangement's force and motion relationships, allowing overlapping roles when justified.", "questions": [ { "text": "Which of the six conventional families describes the arrangement, and what observed motion or constraint supports that assignment?", "kind": "definition", "id": "operating-role-q01" }, { "text": "Does the same component perform different simple-machine roles in different uses or configurations?", "kind": "boundary", "id": "operating-role-q02" } ] } ] }, { "id": "elementary-versus-compound", "name": "Elementary versus compound", "description": "Separates an elementary mechanical role from the larger equipment containing it.", "findings": [ { "id": "mechanism-boundary", "name": "Mechanism boundary", "description": "Identify the contacts, supports, and elements needed for the elementary action without absorbing the complete host machine.", "questions": [ { "text": "Which components and external supports are necessary to define this simple-machine action?", "kind": "boundary", "id": "mechanism-boundary-q01" }, { "text": "Which additional mechanisms or energy sources belong to the host machine rather than this elementary role?", "kind": "boundary", "id": "mechanism-boundary-q02" } ] } ] } ] }, { "id": "geometry-and-motion", "name": "Geometry and motion", "description": "Captures the geometry and constraints that connect effort movement to load movement.", "rationale": "The governing measurements differ substantially between rotating mechanisms and inclined or helical contacts.", "layers": [ { "id": "rotation-and-flexible-transmission", "name": "Rotation and flexible transmission", "description": "Describes lever arms, coupled radii, and pulley routing.", "findings": [ { "id": "effective-arms-and-routing", "name": "Effective arms and routing", "description": "Use perpendicular moment arms, effective radii, and actual rope geometry rather than nominal component dimensions alone.", "questions": [ { "text": "For a lever or wheel and axle, what are the effective moment arms or radii at the stated force directions?", "kind": "measurement", "id": "effective-arms-and-routing-q01" }, { "text": "For a pulley arrangement, which segments support the moving load, at what angles, and how does routing constrain input and output travel?", "kind": "measurement", "id": "effective-arms-and-routing-q02" } ] } ] }, { "id": "inclined-and-helical-contact", "name": "Inclined and helical contact", "description": "Describes motion conversion through slopes, wedge faces, and threads.", "findings": [ { "id": "contact-geometry", "name": "Contact geometry", "description": "Record the active contact geometry and movement direction, including screw lead rather than assuming thread pitch equals advance per revolution.", "questions": [ { "text": "What slope length and rise, wedge-face angles, or screw lead govern the actual input and output movement?", "kind": "measurement", "id": "contact-geometry-q01" }, { "text": "Which body moves, which surfaces constrain it, and where do contact or travel limits terminate the motion?", "kind": "boundary", "id": "contact-geometry-q02" } ] } ] } ] }, { "id": "effort-work-and-losses", "name": "Effort, work, and losses", "description": "Relates ideal geometric performance to measured force, torque, travel, and energy transfer.", "rationale": "A simple machine can multiply force without multiplying energy, and actual effort depends on losses and operating conditions.", "layers": [ { "id": "ideal-transfer", "name": "Ideal transfer", "description": "States the assumptions and quantities used for an ideal performance estimate.", "findings": [ { "id": "force-travel-tradeoff", "name": "Force and travel trade-off", "description": "Pair every claimed force advantage with the associated displacement relationship and explicit idealisation.", "questions": [ { "text": "Under the stated frictionless and motion assumptions, what input effort and travel are required for the specified load movement?", "kind": "measurement", "id": "force-travel-tradeoff-q01" }, { "text": "Are the input and output both forces, both torques, or different quantities requiring a clearly defined conversion relationship?", "kind": "definition", "id": "force-travel-tradeoff-q02" } ] } ] }, { "id": "actual-performance", "name": "Actual performance", "description": "Accounts for measured losses and differences between starting and sustained movement.", "findings": [ { "id": "losses-and-test-basis", "name": "Losses and test basis", "description": "Associate actual performance with frictional contacts, deformation, speed, and a reproducible measurement basis.", "questions": [ { "text": "How do measured starting effort, running effort, and useful output work compare with the ideal prediction?", "kind": "measurement", "id": "losses-and-test-basis-q01" }, { "text": "What test or source supports the efficiency estimate, and which contact, lubrication, load, and speed conditions does it cover?", "kind": "provenance", "id": "losses-and-test-basis-q02" } ] } ] } ] }, { "id": "load-holding-and-integrity", "name": "Load holding and integrity", "description": "Assesses whether the arrangement remains supported and controlled under load.", "rationale": "Mechanical advantage alone establishes neither strength nor the ability to hold a load when effort ceases.", "layers": [ { "id": "backdrive-and-restraint", "name": "Backdrive and restraint", "description": "Distinguishes motion resistance from demonstrated load holding.", "findings": [ { "id": "release-of-effort", "name": "Release of effort", "description": "Determine what happens when input effort is removed, reduced, or reversed under the relevant contact conditions.", "questions": [ { "text": "Will the specified load descend, unwind, eject the wedge, or otherwise reverse the mechanism when effort is removed?", "kind": "measurement", "id": "release-of-effort-q01" }, { "text": "What restraint or verified holding condition is required before releasing input effort or approaching the load?", "kind": "action", "id": "release-of-effort-q02" } ] } ] }, { "id": "load-path-condition", "name": "Load-path condition", "description": "Connects support integrity and local defects to configuration-specific limits.", "findings": [ { "id": "capacity-and-defects", "name": "Capacity and defects", "description": "Record evidence for capacity and inspect the interfaces whose failure would interrupt the load path.", "questions": [ { "text": "What documentation or assessment establishes the allowable load for the fulcrum, axle, rope, thread, contact surface, and anchorage actually used?", "kind": "provenance", "id": "capacity-and-defects-q01" }, { "text": "Which observed wear, cracking, thread damage, rope damage, slipping support, or deformation requires withdrawal or reassessment?", "kind": "action", "id": "capacity-and-defects-q02" } ] } ] } ] }, { "id": "configuration-and-intervention", "name": "Configuration and intervention", "description": "Guides setup, adjustment, and maintenance of the elementary mechanism.", "rationale": "Changing a fulcrum, reeving path, contact surface, or thread condition can change both useful performance and hazards.", "layers": [ { "id": "setup-and-use", "name": "Setup and use", "description": "Checks that the chosen configuration can deliver the intended motion within its supported operating envelope.", "findings": [ { "id": "configuration-check", "name": "Configuration check", "description": "Evaluate effort access, available travel, stable support, and load control before operation.", "questions": [ { "text": "Does the selected geometry provide sufficient output travel with available input effort and movement space?", "kind": "measurement", "id": "configuration-check-q01" }, { "text": "What setup changes are needed to prevent support movement, rope derailment, contact separation, or entry into pinch and crush zones?", "kind": "action", "id": "configuration-check-q02" } ] } ] }, { "id": "maintenance-and-reassessment", "name": "Maintenance and reassessment", "description": "Identifies interventions that preserve function or require renewed performance and holding checks.", "findings": [ { "id": "contact-changing-interventions", "name": "Contact-changing interventions", "description": "Treat lubrication, replacement, alignment, and geometry changes as interventions that may alter friction, advantage, or load retention.", "questions": [ { "text": "Which pivots, bearings, threads, ropes, and contact faces require inspection or maintenance under the applicable usage instructions?", "kind": "action", "id": "contact-changing-interventions-q01" }, { "text": "After lubrication, replacement, or reconfiguration, which effort, travel, support, and backdriving properties must be checked again?", "kind": "action", "id": "contact-changing-interventions-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 classical mechanics category, not a particular product or physical unit; the six types are a conventional classification and are not all mechanically independent.", "Dimensions, load capacities, power sources, controls and applicable standards depend on the actual implementation and cannot be assigned universally.", "Ideal mechanical advantage assumes lossless operation; practical performance also depends on friction, deformation and operating conditions." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of simple machine 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": [ "Lever", "Wheel and axle", "Pulley", "Inclined plane", "Wedge", "Screw" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of simple machine 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": [ "Levers lift or pry loads about a fulcrum.", "Wheel-and-axle arrangements transmit torque and provide mechanical advantage in devices such as hand winches.", "Pulley arrangements redirect pulling forces or reduce the effort required to lift loads.", "Inclined planes let loads reach a different elevation over a longer travel distance.", "Wedges split or separate materials, while screws convert rotation into axial motion or clamping force." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of simple machine 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": "Mechanical advantage", "typical_range": "No universal range; the ratio of output load force to input effort force can be below, equal to, or above 1.", "unit": "dimensionless" }, { "quantity": "Mechanical efficiency", "typical_range": "100% in the ideal lossless model; less than 100% in real operation with friction or other losses.", "unit": "%" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of simple machine 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": [ "Overloading can bend, buckle or fracture load-bearing components.", "Sliding loads, slipping contact surfaces or displaced supports can cause sudden loss of control.", "Moving parts and closing gaps can create pinch, crush or entanglement hazards.", "Friction and wear can increase required effort and degrade operation.", "An unsupported load can drive a reversible mechanism backward and fall or move unexpectedly." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of simple machine 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": "Compound machine", "difference": "Combines two or more simple machines into an operating assembly." }, { "name": "Mechanism", "difference": "A broader category of arrangements that constrain or transmit motion and forces; it need not belong to one of the six classical simple-machine types." }, { "name": "Engine", "difference": "Converts an energy source into mechanical work; a simple machine transmits and transforms mechanical input." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of simple machine this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own the simple-machine concept, requiring this registry entry to link to it?", "Which authoritative sources should anchor the six-family classification and resolve overlapping classifications such as a wedge acting as a moving inclined plane?", "Where should this catalogue draw the boundary between a pulley arrangement modelled under simple machine and a compound lifting mechanism?", "Which application-specific standards and issuing bodies apply to particular implementations, and which requirements belong in neighbouring equipment models?", "What evidence is sufficient to record load capacity or self-locking behaviour when an arrangement has no manufacturer rating or documented test?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 26 } }, "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 simple machine, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a simple machine, assess how it transmits force and motion, and determine whether a proposed use is mechanically feasible and safe.", "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: reach extender.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 70 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 simple machine, 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": [ "reach extender" ] } ], "standing": "Described in 70 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 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 simple machine from another, and a simple machine 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 simple machine, 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 simple machine, 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 simple machine 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 simple machine, 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 simple machine, 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 simple machine 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 simple machine 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 simple machine, 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 simple machine, 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 simple machine 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 simple machine from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a simple machine, 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 simple machine, 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 simple machine 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 simple machine 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 simple machine, 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 simple machine, 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 simple machine 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 simple machine is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a simple machine, 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 simple machine, 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 simple machine 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 simple machine is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a simple machine, 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 simple machine, 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 simple machine 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 simple machine 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 simple machine is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a simple machine, 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 simple machine, 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 simple machine 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 simple machine 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 simple machine, 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 simple machine, 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 simple machine 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 simple machine 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 simple machine between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a simple machine, 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 simple machine, 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 simple machine 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 simple machine, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a simple machine 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 simple machine, 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 simple machine, 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 simple machine 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 simple machine 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 simple machine 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 simple machine, 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 simple machine 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 simple machine 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 simple machine 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 simple machine 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 simple machine 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 simple machine, 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 simple machine 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 simple machine and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a simple machine, 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 simple machine, 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 simple machine 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 simple machine is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a simple machine, 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 simple machine, 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 simple machine 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 } } } }