{ "model": { "rank": 921, "code": "thing-support-4", "model_id": "vr.tr.support-4", "name": "support", "purpose": "any device that bears the weight of another thing", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/support-4/", "tier": 2, "score": 216, "payload": { "layer": "wordnet", "aliases": [ "andiron", "firedog", "dog", "dog-iron", "angle bracket", "angle iron", "ankle brace", "arch support", "arm", "armrest", "atlas", "telamon", "back", "backrest", "backbench", "backboard", "back brace", "backseat", "backstay", "ball bearing", "needle bearing", "roller bearing", "baluster", "bar", "barbecue", "barbeque", "base", "pedestal", "stand", "beam", "bearing", "bedpost", "bell seat", "balloon seat", "bicycle rack", "bike rack", "bicycle parking rack", "bike parking rack", "bicycle stand", "bike stand" ], "aliasCount": 300, "merged": 216, "knownIn": 0, "facets": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "portable", "scale": "handheld", "affordances": [ "graspable", "operable" ] }, "markers": [ "artifact", "device" ], "lexicalClass": "noun.artifact", "senseRank": 9, "alsoRegisteredAs": null, "source": { "dataset": "oewn:2024", "synset": "oewn-04366676-n", "ili": "i59816", "license": "CC BY 4.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-06T21:49:01Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 2.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": 60.6, "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: 01a078b1-4ed5-7771-9cd1-bde3452480a8\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: support\nRegistry id: vr.tr.support-4\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: any device that bears the weight of another thing\nNames folde" } } }, "metaModel": { "id": "THING-SUPPORT-4", "registryId": "vr.tr.support-4", "name": "support", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/support-4/", "model": { "registry_id": "vr.tr.support-4", "name": "support", "purpose": "Enable an AI agent to recognise a weight-bearing device, assess its suitability and condition for a particular supported thing, and identify actions permitted by the available evidence.", "definition": "any device that bears the weight of another thing", "scope_statement": "This model owns support as a physical device whose function is to bear another thing's weight, including its bearing interfaces, load-transfer arrangement, configuration-dependent limits, stability and service condition.", "in_scope": [ "The device's weight-bearing role and relationship to the thing it supports", "Contact, attachment and load transfer through the support", "Support geometry, adjustment and installed configuration", "Evidence of permissible loading for the actual configuration", "Stability, deterioration and readiness for continued use" ], "out_of_scope": [ "The supported thing's internal construction, function and general condition", "The ground, building or foundation as an independently assessed asset", "Fasteners and anchors as independently specified products", "Lifting machinery and transport equipment beyond their support interfaces", "Detailed structural design calculations and certification processes" ], "distinguishing_features": [ "Identify another thing whose weight the device is intended to bear; incidental contact alone does not establish a support role.", "Trace how the supported thing's gravitational load enters and leaves the device; a component that only aligns or laterally restrains something may belong to a neighbouring model.", "Establish whether the candidate is an identifiable device rather than merely terrain or an available surface.", "Distinguish sustained weight-bearing from lifting or transport, recording multiple roles when one device performs more than one function." ], "characteristics": [ { "name": "Supported thing", "kind": "relation", "unit_or_values": "References to supported objects and their bearing locations", "why_it_matters": "Suitability depends on what the support bears and where the weight is applied." }, { "name": "Support arrangement", "kind": "category", "unit_or_values": "Freestanding, attached, suspended, integrated, other or unresolved", "why_it_matters": "Identifies which interfaces and dependencies require assessment." }, { "name": "Applied loading", "kind": "measurement", "unit_or_values": "Force in N and moment in N·m, with location, direction, operating condition and uncertainty", "why_it_matters": "A total weight alone does not describe how the support is loaded." }, { "name": "Permissible loading evidence", "kind": "relation", "unit_or_values": "Referenced rating, assessment or test tied to a specified configuration; unknown if unavailable", "why_it_matters": "Prevents a limit from being assumed or transferred between incompatible configurations." }, { "name": "Bearing geometry", "kind": "measurement", "unit_or_values": "Contact dimensions, footprint, height, extension and offsets in mm or m", "why_it_matters": "Geometry affects fit, load distribution and stability." }, { "name": "Adjustment and locking state", "kind": "state", "unit_or_values": "Fixed, adjusted and verified locked, unlocked, partially engaged, not applicable or unknown", "why_it_matters": "The current setting and its retention can determine whether the support is usable." }, { "name": "Receiving structure", "kind": "relation", "unit_or_values": "Reference to ground, floor, wall, frame or other element receiving the transferred load", "why_it_matters": "Support performance depends on the adequacy of the receiving interface." }, { "name": "Observed displacement", "kind": "measurement", "unit_or_values": "Deflection, settlement or slip in mm and tilt in degrees, with load and observation time", "why_it_matters": "Movement under known conditions informs assessment of fit, stability and changing condition." }, { "name": "Weight-bearing condition", "kind": "state", "unit_or_values": "Recorded defects, affected locations, inspection date and assessed service status", "why_it_matters": "Damage must be connected to the parts and interfaces that carry weight." } ], "affordances": [ "Match a support to a proposed supported thing using interface, loading and configuration evidence.", "Record placement, attachment and adjustment for assessment before loading.", "Compare observed use with documented limits and flag missing evidence.", "Inspect bearing surfaces, load-carrying members, joints and locking mechanisms.", "Identify whether repositioning, adjustment or removal requires unloading or an independently verified alternative support.", "Recommend continued use, further assessment, repair or withdrawal according to documented criteria." ] }, "sources": [], "structure": { "bundles": [ { "id": "weight-bearing-role", "name": "Weight-bearing role", "description": "Establishes what makes the candidate a support and identifies the extent of its responsibility.", "rationale": "A support is recognised through its relationship to another thing's weight, not through a single shape or material.", "layers": [ { "id": "supported-thing", "name": "Supported thing", "description": "Identifies what is borne and whether the bearing role is intended or incidental.", "findings": [ { "id": "bearing-relationship", "name": "Bearing relationship", "description": "Record the supported thing, the bearing locations and the evidence for the support role.", "questions": [ { "text": "Which thing's weight is this device intended to bear, and at which locations?", "kind": "definition", "id": "bearing-relationship-q01" }, { "text": "What documentation or observation establishes that weight-bearing role?", "kind": "provenance", "id": "bearing-relationship-q02" } ] } ] }, { "id": "device-boundary", "name": "Device boundary", "description": "Separates the support from neighbouring devices and from the receiving structure.", "findings": [ { "id": "support-assembly-boundary", "name": "Support assembly boundary", "description": "Record which members, feet, pads and integral adjustment components constitute this support.", "questions": [ { "text": "Which components belong to this support, and which are separate anchors, foundations or supported objects?", "kind": "boundary", "id": "support-assembly-boundary-q01" }, { "text": "Does the device also lift, transport or restrain the supported thing, and where are those roles represented?", "kind": "boundary", "id": "support-assembly-boundary-q02" } ] } ] } ] }, { "id": "load-transfer-and-limits", "name": "Load transfer and limits", "description": "Relates the actual loading to the device's load path and applicable evidence of permissible use.", "rationale": "An agent must distinguish a support that is carrying weight from one shown to be suitable for that loading.", "layers": [ { "id": "applied-load-path", "name": "Applied load path", "description": "Tracks how weight enters the support and passes to other elements.", "findings": [ { "id": "load-entry-and-exit", "name": "Load entry and exit", "description": "Record load application points, transfer members and receiving interfaces, including unresolved load sharing.", "questions": [ { "text": "Where does the weight enter this support, through which members does it pass, and where is it transferred onward?", "kind": "definition", "id": "load-entry-and-exit-q01" }, { "text": "What forces and moments act in the proposed use, and how was this support's share established when several supports are present?", "kind": "measurement", "id": "load-entry-and-exit-q02" } ] } ] }, { "id": "configuration-specific-limits", "name": "Configuration-specific limits", "description": "Connects loading limits to the settings and conditions for which they are evidenced.", "findings": [ { "id": "applicable-load-evidence", "name": "Applicable load evidence", "description": "Record the basis, applicability and gaps of any claimed loading limit.", "questions": [ { "text": "Which rating, test or assessment establishes permissible loading for this exact support and configuration?", "kind": "provenance", "id": "applicable-load-evidence-q01" }, { "text": "Does that evidence cover the actual extension, orientation, load offset and any changing or impact loading?", "kind": "boundary", "id": "applicable-load-evidence-q02" }, { "text": "What additional evidence is required before accepting a use outside the documented conditions?", "kind": "action", "id": "applicable-load-evidence-q03" } ] } ] } ] }, { "id": "bearing-interfaces-and-adjustment", "name": "Bearing interfaces and adjustment", "description": "Describes how the device fits the supported thing and retains its working geometry.", "rationale": "A support can have an applicable load rating yet remain unsuitable because its contact or adjustment arrangement is incompatible.", "layers": [ { "id": "contact-compatibility", "name": "Contact compatibility", "description": "Examines the surfaces through which the supported thing's weight enters the device.", "findings": [ { "id": "bearing-fit", "name": "Bearing fit", "description": "Record actual contact, alignment and any pads, saddles or adapters needed for the bearing interface.", "questions": [ { "text": "What contact area, alignment and load offset exist between the supported thing and the bearing surface?", "kind": "measurement", "id": "bearing-fit-q01" }, { "text": "What evidence establishes that the bearing surface and any adapter are suitable for the supported thing?", "kind": "provenance", "id": "bearing-fit-q02" } ] } ] }, { "id": "working-geometry-retention", "name": "Working geometry retention", "description": "Identifies adjustable parts and how their selected positions are maintained.", "findings": [ { "id": "settings-and-locks", "name": "Settings and locks", "description": "Record extension, angle and engagement of mechanisms that retain the load-bearing configuration.", "questions": [ { "text": "What are the current adjustable settings, and which pins, threads, clamps or other mechanisms retain them?", "kind": "measurement", "id": "settings-and-locks-q01" }, { "text": "How is correct engagement verified, and what documented conditions govern adjustment while carrying weight?", "kind": "action", "id": "settings-and-locks-q02" } ] } ] } ] }, { "id": "installed-stability", "name": "Installed stability", "description": "Assesses the installed arrangement's resistance to unintended movement and its dependence on surrounding structures.", "rationale": "Weight-bearing capability alone does not establish that the installed support will remain in place.", "layers": [ { "id": "receiving-interface", "name": "Receiving interface", "description": "Identifies the surface or structure receiving the support's load and the quality of engagement.", "findings": [ { "id": "base-or-attachment-engagement", "name": "Base or attachment engagement", "description": "Record foot contact or attachment engagement and reference assessments of the receiving structure.", "questions": [ { "text": "Which floor, ground, wall or frame receives the load, and what contact or attachment is actually engaged?", "kind": "boundary", "id": "base-or-attachment-engagement-q01" }, { "text": "What evidence establishes that the receiving interface can accept the transferred load in its current condition?", "kind": "provenance", "id": "base-or-attachment-engagement-q02" } ] } ] }, { "id": "movement-and-restraint", "name": "Movement and restraint", "description": "Relates loading and placement to relevant modes of unintended displacement.", "findings": [ { "id": "stability-assessment", "name": "Stability assessment", "description": "Record assessment of applicable tipping, sliding, swinging or separation risks and dependencies on restraints.", "questions": [ { "text": "Which unintended movements are relevant to this arrangement, and what assessment covers the actual load position and restraints?", "kind": "provenance", "id": "stability-assessment-q01" }, { "text": "What slip, tilt, settlement or other movement has been observed under stated loading conditions?", "kind": "measurement", "id": "stability-assessment-q02" }, { "text": "Which changes to placement, supported load or restraint require stability to be reassessed?", "kind": "action", "id": "stability-assessment-q03" } ] } ] } ] }, { "id": "bearing-condition-and-intervention", "name": "Bearing condition and intervention", "description": "Connects observed deterioration and service evidence to decisions about continued bearing and intervention.", "rationale": "An agent must relate defects to weight-bearing function and account for the supported thing before changing or removing its support.", "layers": [ { "id": "load-carrying-condition", "name": "Load-carrying condition", "description": "Records defects and changes in the members and interfaces that carry weight.", "findings": [ { "id": "defects-and-deformation", "name": "Defects and deformation", "description": "Locate observed damage, wear, looseness and deformation, distinguishing observations from assessed acceptability.", "questions": [ { "text": "Where are cracks, corrosion, wear, looseness or deformation observed along the load path?", "kind": "measurement", "id": "defects-and-deformation-q01" }, { "text": "Which inspection or acceptance criteria determine the significance of these observations for continued weight-bearing?", "kind": "provenance", "id": "defects-and-deformation-q02" } ] } ] }, { "id": "service-decisions", "name": "Service decisions", "description": "Records the evidence and prerequisites for loading, continued use, adjustment, repair or removal.", "findings": [ { "id": "intervention-prerequisites", "name": "Intervention prerequisites", "description": "Make service decisions traceable and identify how the supported weight is handled during intervention.", "questions": [ { "text": "What recorded decision permits or restricts current use, and which configuration and inspection evidence does it cover?", "kind": "provenance", "id": "intervention-prerequisites-q01" }, { "text": "Before adjustment, repair or removal, how will the supported weight be unloaded or transferred, and what verifies the alternative arrangement?", "kind": "action", "id": "intervention-prerequisites-q02" }, { "text": "What checks are required before returning this support to weight-bearing service?", "kind": "action", "id": "intervention-prerequisites-q03" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover this concept and therefore need to remain its single source of truth?", "How does the registry distinguish support devices from shelves, stands, brackets, hangers and integral structural members that also bear weight?", "Which support families require specialised extensions for flexible suspension, compliant bearing or active height control?", "Which authoritative sources establish configuration-specific loading evidence, inspection criteria and intervention rules for the support families included?", "How should shared loading across multiple supports be represented when the distribution has not been measured or otherwise established?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 23 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched.", "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 support, record what state it is in, and decide what may be done with it.", "whatItIs": "any device that bears the weight of another thing", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "portable", "scale": "handheld" }, "whatYouCanDoWithIt": [ "picked up and handled", "operated or controlled" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: andiron, firedog, dog, dog-iron, angle bracket, angle iron, ankle brace, arch support, arm, armrest, atlas, telamon.", "216 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 support, 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", "operate it, set it, turn it on and off" ], "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": [ "andiron", "firedog", "dog", "dog-iron", "angle bracket", "angle iron", "ankle brace", "arch support", "arm", "armrest", "atlas", "telamon" ] } ], "standing": "216 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 support from another, and a support 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 support, 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 support, 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 support 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 support, 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 support, 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 support 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 support 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 support, 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 support, 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 support 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 support from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a support, 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 support, 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 support 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 support 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 support, 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 support, 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 support 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 support is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a support, 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 support, 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 support 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 support is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a support, 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 support, 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 support 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 support 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 support is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a support, 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 support, 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 support 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 support 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 support, 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 support, 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 support 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 support 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 support between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a support, 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 support, 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 support 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 support, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a support 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 support, 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 support, 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 support 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 support 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 support 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 support, 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 support 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 support 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 support 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 support 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 support 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 support, 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 support 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 support and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a support, 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 support, 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 support 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 support is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a support, 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 support, 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 support 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 } } } }