{ "model": { "rank": 5678, "code": "thing-connection-artifact", "model_id": "vr.tr.connection-artifact", "name": "connection", "purpose": "an instrumentality that connects", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/connection-artifact/", "tier": 2, "score": 65, "payload": { "layer": "wordnet", "aliases": [ "anchor chain", "anchor rope", "attachment", "bond", "backbone", "baling wire", "ball-and-socket joint", "barbed wire", "barbwire", "bicycle chain", "binder", "ligature", "butt hinge", "butt joint", "butt", "butt weld", "butt-weld", "chain", "chatelaine", "clip lead", "concertina", "connexion", "connector", "connecter", "connective", "digital subscriber line", "DSL", "dovetail", "dovetail joint", "fell", "felled seam", "fish joint", "fob", "watch chain", "watch guard", "ground", "earth", "haywire", "hinge", "flexible joint" ], "aliasCount": 106, "merged": 65, "knownIn": 0, "facets": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "portable", "scale": "handheld", "affordances": [ "graspable" ] }, "markers": [ "artifact" ], "lexicalClass": "noun.artifact", "senseRank": 2, "alsoRegisteredAs": null, "source": { "dataset": "oewn:2024", "synset": "oewn-03095830-n", "ili": "i52280", "license": "CC BY 4.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T08:59:39Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 5.2, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 80.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07b16-fe4b-73a2-af54-5c33ef51b50c\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: connection\nRegistry id: vr.tr.connection-artifact\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: an instrumentality that connects\nNames folded in" } } }, "metaModel": { "id": "THING-CONNECTION-ARTIFACT", "registryId": "vr.tr.connection-artifact", "name": "connection", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/connection-artifact/", "model": { "registry_id": "vr.tr.connection-artifact", "name": "connection", "purpose": "Enable an AI agent to recognise a physical connecting instrumentality, assess whether it connects its intended endpoints adequately, and determine which installation, use, inspection or separation actions are permissible.", "definition": "an instrumentality that connects", "scope_statement": "This model owns the physical artifact whose role is to connect otherwise distinct physical things, including its endpoint interfaces, connecting mechanism, conveyed effects, operating limits and connection state; it does not own the connected things themselves or an abstract relationship between them.", "in_scope": [ "The connecting artifact and the boundary separating it from its endpoints", "Endpoint interfaces, mating requirements and attachment arrangements", "How the artifact establishes and maintains a physical connection", "What the connection carries, transmits, constrains or holds together", "Conditions governing connection integrity, use and disconnection" ], "out_of_scope": [ "The complete models of the objects or systems being connected", "Abstract associations, social connections and informational links without a physical connecting artifact", "A contact or joint understood only as a relationship or location", "The substance, energy or information conveyed through the connection", "The architecture and operation of the wider network containing the connection" ], "distinguishing_features": [ "An identifiable physical artifact performs the connecting role; two things merely touching does not by itself identify such an artifact.", "Its connecting role can be described by identifying the physical things or interfaces it joins, even when those endpoints are temporarily absent.", "Its own physical features provide attachment, continuity, retention or another connecting mechanism, rather than merely indicating that a relationship exists.", "A loose or disengaged connecting artifact can retain its identity as a connection artifact while failing to establish a current connection.", "A connector, fastener, adapter, cable or similar named object may satisfy this definition; its name alone does not establish a separate registry concept." ], "characteristics": [ { "name": "Artifact boundary", "kind": "category", "unit_or_values": "Single component, bounded assembly, integrated connecting feature, or unresolved", "why_it_matters": "Establishes what the agent is assessing and which parts belong to neighbouring objects." }, { "name": "Endpoint assignments", "kind": "relation", "unit_or_values": "Artifact interface mapped to intended and currently attached physical endpoint", "why_it_matters": "Distinguishes correct connection, wrong connection and an unoccupied interface." }, { "name": "Interface compatibility", "kind": "state", "unit_or_values": "Compatible, conditionally compatible, incompatible, or unverified for each proposed endpoint", "why_it_matters": "Physical fit alone may not establish suitability for the intended connection." }, { "name": "Connecting mechanism", "kind": "category", "unit_or_values": "Recorded mechanism, such as threaded engagement, latching, bonding, clamping or interference fit", "why_it_matters": "Determines how the connection is established, retained, inspected and released." }, { "name": "Connecting function", "kind": "category", "unit_or_values": "One or more of mechanical restraint, load transfer, fluid passage, electrical continuity, optical continuity, or another specified physical function", "why_it_matters": "Defines what successful connection means for this artifact." }, { "name": "Engagement state", "kind": "state", "unit_or_values": "Disengaged, partially engaged, engaged but unsecured, secured, or unknown, per interface where applicable", "why_it_matters": "Separates apparent attachment from a connection ready for its intended use." }, { "name": "Relative motion behaviour", "kind": "category", "unit_or_values": "Restrained or permitted translation and rotation, with the relevant directions identified", "why_it_matters": "Movement can be an intended capability or evidence of loss of connection." }, { "name": "Function-specific limits", "kind": "measurement", "unit_or_values": "Applicable quantities and units, such as N, N·m, Pa, A, V or °C, with their conditions and evidence", "why_it_matters": "Supports comparison of intended service with verified connection limits." }, { "name": "Connection performance", "kind": "measurement", "unit_or_values": "Applicable observations such as retention force in N, leakage in mL/min, resistance in Ω or optical loss in dB, with test conditions", "why_it_matters": "Provides evidence that the artifact performs its particular connecting function." }, { "name": "Separation and reuse status", "kind": "state", "unit_or_values": "Recorded separation method, whether separation is destructive, and verified or unresolved reuse eligibility", "why_it_matters": "Prevents an agent from assuming that a connection can be opened or reinstalled safely." } ], "affordances": [ "Identify the artifact and map its interfaces to intended and actual endpoints.", "Evaluate a proposed endpoint pairing against documented interface and service requirements.", "Plan or perform authorised engagement, securing and functional verification.", "Inspect or test retention and continuity using criteria appropriate to the connecting function.", "Determine whether service conditions require restriction, isolation, repair or replacement.", "Plan or perform authorised separation and assess whether the artifact may be reused." ] }, "sources": [], "structure": { "bundles": [ { "id": "connecting-artifact-and-endpoints", "name": "Connecting artifact and endpoints", "description": "Identify the physical instrumentality and the things it is intended to join.", "rationale": "An agent must distinguish the artifact from the relationship it creates and from the objects at its ends.", "layers": [ { "id": "artifact-boundary", "name": "Artifact boundary", "description": "Locate the physical extent of the connecting instrumentality.", "findings": [ { "id": "bounded-connecting-unit", "name": "Bounded connecting unit", "description": "Record the component or assembly treated as the connection artifact, including uncertain boundaries.", "questions": [ { "text": "Which physical component or assembly performs the connecting role?", "kind": "definition", "id": "bounded-connecting-unit-q01" }, { "text": "Which mating features belong to this artifact, and which belong to the connected objects?", "kind": "boundary", "id": "bounded-connecting-unit-q02" } ] } ] }, { "id": "endpoint-mapping", "name": "Endpoint mapping", "description": "Distinguish intended attachment arrangements from current attachments.", "findings": [ { "id": "intended-and-actual-endpoints", "name": "Intended and actual endpoints", "description": "Record the physical endpoint assigned to each interface, including vacant or incorrectly occupied interfaces.", "questions": [ { "text": "What physical endpoints is each interface intended to connect?", "kind": "definition", "id": "intended-and-actual-endpoints-q01" }, { "text": "Which endpoints are currently attached, and how was that mapping verified?", "kind": "provenance", "id": "intended-and-actual-endpoints-q02" } ] } ] } ] }, { "id": "mating-and-retention", "name": "Mating and retention", "description": "Describe how endpoints fit the artifact and remain connected.", "rationale": "A connection can appear to fit while lacking compatibility, full engagement or adequate retention.", "layers": [ { "id": "interface-compatibility", "name": "Interface compatibility", "description": "Capture the requirements for a valid physical pairing.", "findings": [ { "id": "valid-mating-conditions", "name": "Valid mating conditions", "description": "Record applicable geometry, orientation, material and interface specifications for each endpoint.", "questions": [ { "text": "Which dimensions, interface specifications, orientations or material combinations determine a valid pairing?", "kind": "definition", "id": "valid-mating-conditions-q01" }, { "text": "What documentation or inspection establishes compatibility with the proposed endpoint?", "kind": "provenance", "id": "valid-mating-conditions-q02" } ] } ] }, { "id": "engagement-and-securing", "name": "Engagement and securing", "description": "Describe the mechanism and evidence of established attachment.", "findings": [ { "id": "retained-engagement", "name": "Retained engagement", "description": "Record how engagement is achieved, how unintended separation is resisted and whether securing is complete.", "questions": [ { "text": "What mechanism establishes engagement and prevents unintended separation?", "kind": "definition", "id": "retained-engagement-q01" }, { "text": "Which observable or measurable condition distinguishes partial engagement from correctly secured engagement?", "kind": "measurement", "id": "retained-engagement-q02" } ] } ] } ] }, { "id": "connecting-function", "name": "Connecting function", "description": "Define what the artifact enables or constrains between its endpoints.", "rationale": "Successful connection depends on the intended physical effect, not attachment alone.", "layers": [ { "id": "transfer-and-continuity", "name": "Transfer and continuity", "description": "Identify what passes through or across the artifact and what must remain separated.", "findings": [ { "id": "intended-physical-paths", "name": "Intended physical paths", "description": "Record required paths for load, matter, energy or signals, including directionality and isolation where applicable.", "questions": [ { "text": "What must this artifact transmit or carry between which interfaces, and in which directions?", "kind": "definition", "id": "intended-physical-paths-q01" }, { "text": "Which paths, channels or surrounding regions must remain isolated from one another?", "kind": "boundary", "id": "intended-physical-paths-q02" } ] } ] }, { "id": "mechanical-relationship", "name": "Mechanical relationship", "description": "Identify the spatial relationship the connection must maintain or permit.", "findings": [ { "id": "restraint-and-permitted-motion", "name": "Restraint and permitted motion", "description": "Record required positioning, permitted movement and constraints imposed between endpoints.", "questions": [ { "text": "Which relative translations or rotations must the connection restrain, permit or accommodate?", "kind": "definition", "id": "restraint-and-permitted-motion-q01" }, { "text": "What observed movement or displacement would indicate departure from the intended relationship?", "kind": "measurement", "id": "restraint-and-permitted-motion-q02" } ] } ] } ] }, { "id": "service-fitness-and-integrity", "name": "Service fitness and integrity", "description": "Assess whether the established connection can perform under its actual conditions.", "rationale": "A secured artifact may still be unsuitable for its load, environment or required continuity.", "layers": [ { "id": "service-envelope", "name": "Service envelope", "description": "Relate applicable connection limits to the intended service.", "findings": [ { "id": "supported-service-conditions", "name": "Supported service conditions", "description": "Record evidenced limits and the conditions under which those limits apply.", "questions": [ { "text": "Which loads, pressures, electrical quantities, temperatures, movements or exposures constrain this connection's intended use?", "kind": "measurement", "id": "supported-service-conditions-q01" }, { "text": "What source or test establishes those limits for this artifact and endpoint combination?", "kind": "provenance", "id": "supported-service-conditions-q02" } ] } ] }, { "id": "integrity-evidence", "name": "Integrity evidence", "description": "Assess loss of retention, continuity, isolation or positional control.", "findings": [ { "id": "connection-condition-assessment", "name": "Connection condition assessment", "description": "Record relevant defects, functional test results and unresolved inspection limitations.", "questions": [ { "text": "What inspection or test results establish the present quality of retention and the required connecting functions?", "kind": "measurement", "id": "connection-condition-assessment-q01" }, { "text": "Which observed conditions require restricted use, isolation, repair or replacement?", "kind": "action", "id": "connection-condition-assessment-q02" } ] } ] } ] }, { "id": "connection-and-separation-actions", "name": "Connection and separation actions", "description": "Define supported transitions into service, out of service and back into service.", "rationale": "Connecting and disconnecting alter endpoint support and physical pathways, so an agent needs explicit action conditions.", "layers": [ { "id": "establishing-service", "name": "Establishing service", "description": "Identify preparation, engagement and verification requirements.", "findings": [ { "id": "installation-and-release-to-use", "name": "Installation and release to use", "description": "Record the applicable procedure and evidence required before treating the connection as usable.", "questions": [ { "text": "What endpoint preparation, alignment, tools and securing sequence are required to establish this connection?", "kind": "action", "id": "installation-and-release-to-use-q01" }, { "text": "What checks must pass before the connected assembly may enter its intended service?", "kind": "action", "id": "installation-and-release-to-use-q02" } ] } ] }, { "id": "separation-and-reconnection", "name": "Separation and reconnection", "description": "Identify how the connection can be opened and whether it can subsequently be restored.", "findings": [ { "id": "controlled-separation-and-reuse", "name": "Controlled separation and reuse", "description": "Record separation prerequisites, expected damage and conditions for reuse or replacement.", "questions": [ { "text": "What support, isolation, unloading or containment is required before releasing or removing this artifact?", "kind": "action", "id": "controlled-separation-and-reuse-q01" }, { "text": "After separation, what evidence determines whether the artifact and its securing or sealing elements may be reused?", "kind": "action", "id": "controlled-separation-and-reuse-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does this registry entry include integral connecting features, deposited joining materials and bonded joints, or only separately identifiable artifacts?", "How does the registry relate this entry to connector, coupling, fastener, adapter and cable entries, and does an existing world model already provide the authoritative coverage?", "When several components jointly establish one connection, what determines whether they form one connection artifact or multiple registered things?", "Which connection families require specialised extensions, and which interface, retention and performance concepts can reliably be shared?", "What evidence and acceptance criteria should govern state judgments for undocumented, custom-made or inaccessible connections?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "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 connection, record what state it is in, and decide what may be done with it.", "whatItIs": "an instrumentality that connects", "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: anchor chain, anchor rope, attachment, bond, backbone, baling wire, ball-and-socket joint, barbed wire, barbwire, bicycle chain, binder, ligature.", "65 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 connection, 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": [ "anchor chain", "anchor rope", "attachment", "bond", "backbone", "baling wire", "ball-and-socket joint", "barbed wire", "barbwire", "bicycle chain", "binder", "ligature" ] } ], "standing": "65 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 connection from another, and a connection 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 connection, 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 connection, 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 connection 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 connection, 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 connection, 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 connection 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 connection 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 connection, 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 connection, 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 connection 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 connection from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a connection, 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 connection, 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 connection 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 connection 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 connection, 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 connection, 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 connection 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 connection is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a connection, 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 connection, 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 connection 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 connection is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a connection, 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 connection, 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 connection 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 connection 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 connection is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a connection, 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 connection, 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 connection 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 connection 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 connection, 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 connection, 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 connection 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 connection 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 connection between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a connection, 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 connection, 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 connection 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 connection, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a connection 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 connection, 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 connection, 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 connection 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 connection 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 connection 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 connection, 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 connection 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 connection 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 connection 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 connection 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 connection 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 connection, 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 connection 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 connection and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a connection, 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 connection, 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 connection 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 connection is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a connection, 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 connection, 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 connection 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 } } } }