{ "model": { "rank": 4500, "code": "thing-system", "model_id": "vr.tr.system", "name": "system", "purpose": "instrumentality that combines interrelated interacting artifacts designed to work as a coherent entity", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/system/", "tier": 2, "score": 75, "payload": { "layer": "wordnet", "aliases": [ "backup system", "cable", "cable television", "cable system", "cable television service", "closed-circuit television", "closed loop", "closed-loop system", "color television", "colour television", "color television system", "colour television system", "color TV", "colour TV", "communication system", "computer network", "computer system", "computing system", "automatic data processing system", "ADP system", "ADPS", "containment", "control system", "data system", "information system", "drainage system", "early warning system", "ethernet", "exhaust", "exhaust system", "explosive detection system", "EDS", "explosive trace detection", "ETD", "field-sequential color television", "field-sequential color TV", "field-sequential color television system", "field-sequential color TV system", "firewall", "fuel injection" ], "aliasCount": 149, "merged": 75, "knownIn": 0, "facets": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "portable", "scale": "handheld", "affordances": [ "graspable" ] }, "markers": [ "artifact" ], "lexicalClass": "noun.artifact", "senseRank": 0, "alsoRegisteredAs": null, "source": { "dataset": "oewn:2024", "synset": "oewn-04384144-n", "ili": "i59913", "license": "CC BY 4.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:22:02Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 24.7, "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: 01a087d4-dd03-7293-a9f4-bdbe2ffdafd4\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: system\nSense to describe: instrumentality that combines interrelated interacting artifacts designed to work as a coherent entity\nDomain code: PHY.OBJ\nAl", "usd": 0, "recall": true }, "codex": { "seconds": 53, "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: 01a087d4-dcf5-70a0-a35c-36229b5e2a42\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: system\nRegistry id: vr.tr.system\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: instrumentality that combines interrelated interacting artifacts " } } }, "metaModel": { "id": "THING-SYSTEM", "registryId": "vr.tr.system", "name": "system", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/system/", "model": { "registry_id": "vr.tr.system", "name": "system", "purpose": "Enable an AI agent to recognise an engineered physical system, assess whether its interacting artifacts can perform their intended joint function, and determine which operations or changes are justified.", "definition": "A system, in this physical artifact sense, is an engineered combination of interrelated, interacting artifacts arranged to function as a coherent entity for an intended purpose.", "scope_statement": "This model owns the registered sense of system as an instrumentality composed of interrelated, interacting artifacts designed to work as a coherent entity, including its functional boundary, integration, collective behaviour, and conditions for operation.", "in_scope": [ "The intended joint function that makes several artifacts one system", "System boundaries, constituent roles, and dependencies on external systems", "Interfaces and exchanges through which artifacts interact", "System operating modes, coordination, and performance constraints", "Integration evidence, failure propagation, and conditions for safe intervention" ], "out_of_scope": [ "Naturally occurring biological systems, including lymphatic and urinary systems", "Political and institutional arrangements, including parliamentary systems", "Abstract mathematical systems and conceptual classification systems", "Detailed internal construction of constituent devices, machines, or tools", "Product-line identities, commercial catalogue records, and individual-unit histories as separate models", "Standalone software systems without an engineered physical artifact assembly" ], "distinguishing_features": [ "Its artifacts have designed interactions that contribute to an identifiable joint function; proximity or shared ownership alone does not establish a system.", "Its functional boundary identifies what participates in collective operation and what supplies external services or environmental conditions.", "Assessing the constituents separately does not establish system readiness; their connections, compatibility, and coordination also require assessment.", "The selected level of description owns a joint function across constituent artifacts, even when a constituent could itself be modelled as a device, machine, or subsystem.", "The term refers here to an engineered physical instrumentality, rather than any organised collection of concepts, institutions, or biological structures." ], "characteristics": [ { "name": "Joint function", "kind": "category", "unit_or_values": "Declared system-level functions with observable success criteria", "why_it_matters": "Provides the basis for deciding whether the artifacts form a coherent instrumentality and whether it works." }, { "name": "Boundary and constituent roles", "kind": "relation", "unit_or_values": "Included artifacts and subsystems, their functional roles, and explicitly external entities", "why_it_matters": "Separates system responsibilities from assumptions about its surroundings." }, { "name": "Interface dependencies", "kind": "relation", "unit_or_values": "Connected endpoints, exchange type, direction, compatibility conditions, and dependency strength", "why_it_matters": "Makes the interactions that enable joint operation inspectable." }, { "name": "Operating mode", "kind": "state", "unit_or_values": "Declared modes such as isolated, starting, operating, degraded, stopping, or maintenance; applicability must be established", "why_it_matters": "Determines which constituent states and actions are currently valid." }, { "name": "Delivered functional performance", "kind": "measurement", "unit_or_values": "Function-specific measures and units, such as throughput in items/h or response time in s, where applicable", "why_it_matters": "Tests the joint outcome rather than assuming that healthy constituents imply adequate performance." }, { "name": "External service requirements", "kind": "relation", "unit_or_values": "Required utilities, inputs, supporting systems, and acceptable supply conditions", "why_it_matters": "Identifies dependencies that can prevent operation even when internal artifacts are serviceable." }, { "name": "Verified configuration", "kind": "relation", "unit_or_values": "Constituent versions, interface arrangements, settings, and the evidence applicable to that combination", "why_it_matters": "Prevents evidence from one assembled configuration being assumed valid for another." }, { "name": "Functional readiness", "kind": "state", "unit_or_values": "Unknown, unavailable, restricted, or ready against declared function and mode criteria", "why_it_matters": "Supports decisions about operation without reducing readiness to a count of working parts." } ], "affordances": [ "Trace an intended function through the artifacts, interfaces, and external services needed to deliver it.", "Assess readiness for a specified operating mode using constituent conditions and integration evidence.", "Identify which system functions may be affected by a failed constituent or disrupted interface.", "Evaluate whether a proposed replacement or reconfiguration requires renewed integration checks.", "Determine prerequisites for startup, shutdown, isolation, maintenance, and return to service.", "Compare observed joint performance with the acceptance criteria for the assembled configuration." ] }, "sources": [], "structure": { "bundles": [ { "id": "functional-unity-and-boundary", "name": "Functional unity and boundary", "description": "Establishes why the artifacts constitute one system and where that system ends.", "rationale": "A collection of artifacts becomes meaningful as this registered thing through designed interaction and joint function.", "layers": [ { "id": "joint-purpose", "name": "Joint purpose", "description": "Identifies the outcome that the artifacts are designed to deliver together.", "findings": [ { "id": "collective-function", "name": "Collective function", "description": "Record the intended joint outcome and the interactions needed to produce it.", "questions": [ { "text": "What observable outcome are the artifacts designed to produce together?", "kind": "definition", "id": "collective-function-q01" }, { "text": "Which interactions distinguish this system from a collection of independently useful artifacts?", "kind": "boundary", "id": "collective-function-q02" } ] } ] }, { "id": "system-of-interest", "name": "System of interest", "description": "Selects the level of aggregation and separates constituents from the operating environment.", "findings": [ { "id": "membership-and-nesting", "name": "Membership and nesting", "description": "Record constituent roles, nested subsystems, and external dependencies at the selected boundary.", "questions": [ { "text": "Which artifacts belong inside the selected boundary, and what functional role justifies each inclusion?", "kind": "boundary", "id": "membership-and-nesting-q01" }, { "text": "Which required services or connected systems remain outside that boundary?", "kind": "boundary", "id": "membership-and-nesting-q02" }, { "text": "What design or operational evidence establishes this level as the system of interest?", "kind": "provenance", "id": "membership-and-nesting-q03" } ] } ] } ] }, { "id": "interfaces-and-integration", "name": "Interfaces and integration", "description": "Describes how constituent artifacts connect and the conditions under which their interactions work.", "rationale": "Constituents can be individually suitable while their assembled interfaces prevent coherent operation.", "layers": [ { "id": "interaction-paths", "name": "Interaction paths", "description": "Makes the exchanges between constituents and across the system boundary explicit.", "findings": [ { "id": "exchange-contracts", "name": "Exchange contracts", "description": "Record relevant transfers of energy, material, information, or mechanical load and their compatibility requirements.", "questions": [ { "text": "What passes across each function-critical interface, between which endpoints, and in which direction?", "kind": "definition", "id": "exchange-contracts-q01" }, { "text": "What limits, units, tolerances, or timing conditions must each exchange satisfy?", "kind": "measurement", "id": "exchange-contracts-q02" } ] } ] }, { "id": "assembled-compatibility", "name": "Assembled compatibility", "description": "Relates integration evidence to the actual combination of constituents and settings.", "findings": [ { "id": "configuration-validity", "name": "Configuration validity", "description": "Identify the configurations for which interface compatibility and joint operation have been demonstrated.", "questions": [ { "text": "Which constituent versions, connections, and settings are covered by the available integration evidence?", "kind": "provenance", "id": "configuration-validity-q01" }, { "text": "Which proposed substitutions or connection changes require compatibility checks before operation?", "kind": "action", "id": "configuration-validity-q02" } ] } ] } ] }, { "id": "coordinated-operation", "name": "Coordinated operation", "description": "Captures the modes, sequencing, and shared constraints needed for artifacts to operate together.", "rationale": "Coherent operation depends on compatible states and coordinated transitions across the assembly.", "layers": [ { "id": "modes-and-transitions", "name": "Modes and transitions", "description": "Defines system modes through required constituent states and transition prerequisites.", "findings": [ { "id": "collective-state", "name": "Collective state", "description": "Record how constituent states establish a system mode and what permits a change of mode.", "questions": [ { "text": "Which combinations of constituent states establish each supported system operating mode?", "kind": "definition", "id": "collective-state-q01" }, { "text": "What sequencing, permissions, and interlocks, if any, govern startup, shutdown, and mode changes?", "kind": "action", "id": "collective-state-q02" } ] } ] }, { "id": "joint-performance", "name": "Joint performance", "description": "Assesses delivered function under shared resource limits and external operating conditions.", "findings": [ { "id": "system-operating-envelope", "name": "System operating envelope", "description": "Record measurable acceptance criteria and the combinations of load, supply, and environment under which they apply.", "questions": [ { "text": "Which system-level measures demonstrate successful joint operation, and what are their acceptance limits and units?", "kind": "measurement", "id": "system-operating-envelope-q01" }, { "text": "Which shared-resource limits or constituent bottlenecks constrain the assembled system under its intended load?", "kind": "measurement", "id": "system-operating-envelope-q02" }, { "text": "What external supply and environmental conditions are assumed by those performance criteria?", "kind": "boundary", "id": "system-operating-envelope-q03" } ] } ] } ] }, { "id": "failure-containment-and-intervention", "name": "Failure containment and intervention", "description": "Connects constituent and interface failures to collective consequences and justified interventions.", "rationale": "Interaction can transmit failures, defeat apparent redundancy, or make a local maintenance action affect the whole system.", "layers": [ { "id": "failure-propagation", "name": "Failure propagation", "description": "Traces loss or corruption of constituent contributions through dependent functions.", "findings": [ { "id": "functional-loss-and-containment", "name": "Functional loss and containment", "description": "Record affected functions, propagation paths, and evidenced isolation or redundancy arrangements.", "questions": [ { "text": "Which joint functions are lost or degraded when each critical constituent or interface fails?", "kind": "definition", "id": "functional-loss-and-containment-q01" }, { "text": "What evidence supports claimed containment or redundancy, including dependencies shared by backup paths?", "kind": "provenance", "id": "functional-loss-and-containment-q02" }, { "text": "Under what established conditions may the remaining assembly continue operating?", "kind": "action", "id": "functional-loss-and-containment-q03" } ] } ] }, { "id": "intervention-and-restoration", "name": "Intervention and restoration", "description": "Determines how maintenance or change affects the connected assembly and its return to service.", "findings": [ { "id": "isolation-and-requalification", "name": "Isolation and requalification", "description": "Record cross-boundary isolation needs and checks required to restore confidence in joint operation.", "questions": [ { "text": "Which connected artifacts, supplies, stored energies, or control paths must be addressed before the proposed intervention?", "kind": "action", "id": "isolation-and-requalification-q01" }, { "text": "Which interface and system-function checks must pass after reconnection, replacement, or reconfiguration?", "kind": "action", "id": "isolation-and-requalification-q02" }, { "text": "What evidence establishes that the restored configuration meets its applicable operating and safety criteria?", "kind": "provenance", "id": "isolation-and-requalification-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This entry covers the generic artifact kind, not a particular product model or installed unit, and excludes biological, political and purely abstract senses.", "There is no defensible capacity, dimension, power requirement or operating range for this broad kind; measurements require a specified application and system boundary.", "The named standards are recalled references, not researched citations; applicable editions, legal requirements and sector-specific standards need verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of system 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": [ "Mechanical systems", "Electrical systems", "Electronic systems", "Hydraulic systems", "Pneumatic systems", "Electromechanical systems" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of system this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "ISO/IEC/IEEE 15288, issued jointly by ISO, IEC and IEEE, defines system life cycle processes applicable to engineered systems.", "ISO/IEC/IEEE 42010, issued jointly by ISO, IEC and IEEE, specifies requirements for architecture descriptions of systems and other entities.", "IEC 61508, issued by the International Electrotechnical Commission, addresses functional safety of electrical, electronic and programmable electronic safety-related systems where applicable." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of system 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": [ "Combining generation, distribution and protection equipment to supply electrical power.", "Integrating pumps, valves, actuators and controls to transmit hydraulic power.", "Coordinating heating, ventilation and cooling equipment to maintain indoor conditions.", "Integrating sensors, controllers and actuators to control industrial processes.", "Combining communication equipment and transmission links to carry information." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of system 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": [ "Interface incompatibility can prevent components from exchanging power, material or information correctly.", "Failure of a shared power supply, controller or other dependency can disable multiple components simultaneously.", "Faults can propagate between connected components and produce cascading loss of function.", "Feedback instability or poorly coordinated controls can cause oscillation, unsafe motion or operation outside intended limits.", "Incorrect configuration, maintenance or replacement parts can defeat safeguards or introduce hazardous interactions." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of system 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": [ "Applicable electrical, machinery, pressure-equipment and conformity-assessment requirements vary by jurisdiction and application." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of system 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": "component", "difference": "A component is considered as a constituent of a larger entity; a system is considered through the coordinated function of its interacting constituents." }, { "name": "assembly", "difference": "An assembly emphasizes parts joined together; a system emphasizes their interactions and collective function, even when its parts are spatially distributed." }, { "name": "machine", "difference": "A machine performs work through mechanisms; a system can incorporate several machines or consist of artifacts whose collective function does not require mechanical work." }, { "name": "subsystem", "difference": "A subsystem is itself a system considered within a larger system boundary; the distinction depends on the chosen scope." }, { "name": "lymphatic system", "difference": "A lymphatic system comprises biological structures and processes, so it uses a biological sense of system rather than this engineered-artifact sense." }, { "name": "urinary system", "difference": "A urinary system comprises organs involved in urine production and elimination, rather than designed, interacting artifacts." }, { "name": "parliamentary system", "difference": "A parliamentary system organizes political institutions and authority, rather than physical artifacts operating together." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of system this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover this engineered physical sense of system, requiring a link instead of a separate publication?", "How does the registry distinguish system from assembly, apparatus, machine, and installation when the same artifact grouping satisfies several descriptions?", "Where should the physical-system boundary fall for software-controlled or human-operated assemblies, especially when software or operator action is essential to coordination?", "Which primary sources should establish the general systems-engineering terminology, and which standards apply only to particular system families?", "What evidence threshold should distinguish declared compatibility, demonstrated integration, and readiness for a particular operation?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 27 } }, "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.", "facetsInferred": false, "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 system, record what state it is in, and decide what may be done with it.", "whatItIs": "instrumentality that combines interrelated interacting artifacts designed to work as a coherent entity", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "portable", "scale": "handheld" }, "whatYouCanDoWithIt": [ "picked up and handled" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: backup system, cable, cable television, cable system, cable television service, closed-circuit television, closed loop, closed-loop system, color television, colour television, color television system, colour television system.", "75 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it." ], "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 system, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Fits in a hand and is carried without help.", "Moved by a person without machinery.", "Does nothing on its own; everything it does, something else did to it." ], "whatCanBeDoneWithIt": [ "pick it up, hold it, put it somewhere else" ], "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": [ "backup system", "cable", "cable television", "cable system", "cable television service", "closed-circuit television", "closed loop", "closed-loop system", "color television", "colour television", "color television system", "colour television system" ] } ], "standing": "75 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 system from another, and a system 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 system, 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 system, 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 system 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 system, 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 system, 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 system 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 system 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 system, 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 system, 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 system 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 system from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a system, 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 system, 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 system 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 system 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 at handheld scale.", "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 system, 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 system, 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 system 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 system is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a system, 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 system, 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 system 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 system is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a system, 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 system, 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 system 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 system is, how it got there and where it may go (portable).", "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 system is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a system, 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 system, 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 system 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 system 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 system, 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 system, 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 system 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 system 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 system between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a system, 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 system, 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 system 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 system, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a system 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 system, 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 system, 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 system 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 system 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 system 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 system, 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 system 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 system 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 system 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 system 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 system 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 system, 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 system 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 system and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a system, 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 system, 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 system 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 system is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a system, 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 system, 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 system 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 } } } }