{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T08:50:38Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.0, "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: 01a094ce-c3ff-79d1-af82-562a48c789e6\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: console\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 registe", "usd": 0.0, "recall": true }, "codex": { "seconds": 65.1, "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: 01a094ce-c410-72f0-a2c0-166d0d3477a5\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: console\nRegistry id: vr.tr.console\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext " } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:59:44+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] } }, "metaModel": { "id": "THING-Q7887380", "registryId": "vr.tr.console", "name": "console", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q7887380/", "model": { "registry_id": "vr.tr.console", "name": "console", "purpose": "Enable an agent to recognise a physical operator console, assess its readiness for interaction with connected equipment, and determine which actions its controls permit.", "definition": "In the equipment sense, a console is a physical assembly that groups controls, displays, or both at an operator position for monitoring or operating a system.", "scope_statement": "Provisionally, this model owns console as a physical assembly that groups operator controls and feedback for another system; the registry provides no definition, so research must confirm this sense before publication.", "in_scope": [ "The console assembly and its operator-facing layout", "Controls, indicators, displays and their assigned functions", "Connections between the console and controlled equipment", "Operating modes, control authority and feedback availability", "Console-specific inspection, servicing and safe interaction" ], "out_of_scope": [ "The complete machine, vehicle or process controlled through the console", "Software-only terminals, command shells and developer consoles", "Furniture called a console without an operator-control function", "Dedicated video game console hardware pending confirmation of the registry sense", "Product lines, individual serialised units and their operating histories" ], "distinguishing_features": [ "Groups operator controls and system feedback into an identifiable physical assembly rather than merely housing equipment.", "Has controls or interaction surfaces mapped to identifiable functions of connected or integrated equipment.", "Provides an operator interaction position or surface, rather than serving solely as a passive display.", "Its physical assembly can be distinguished from the software interface it may display and from the wider system it operates." ], "characteristics": [ { "name": "Console role", "kind": "category", "unit_or_values": "control; monitoring and control; configuration; mixed; unresolved", "why_it_matters": "Establishes which operator activities the assembly supports." }, { "name": "Controlled equipment", "kind": "relation", "unit_or_values": "Identified systems or subsystems with command and feedback mappings", "why_it_matters": "Prevents assigning a console action to the wrong target." }, { "name": "Interaction arrangement", "kind": "category", "unit_or_values": "physical controls; touchscreen; keyboard and display; mixed", "why_it_matters": "Determines how commands are entered and confirmed." }, { "name": "Control authority", "kind": "state", "unit_or_values": "active; shared; inhibited; monitoring only; unknown", "why_it_matters": "Distinguishes visible controls from controls currently authorised to affect equipment." }, { "name": "Feedback validity", "kind": "state", "unit_or_values": "current and verified; stale; unavailable; inconsistent; unknown", "why_it_matters": "A displayed condition may not represent the present condition of the controlled system." }, { "name": "Operator geometry", "kind": "measurement", "unit_or_values": "Control and display heights and reach distances in mm; viewing angles in degrees", "why_it_matters": "Supports assessment of visibility, reach and suitability for the intended operator position." }, { "name": "Power and communication dependencies", "kind": "relation", "unit_or_values": "Supply, communication links and any independent backup paths", "why_it_matters": "Explains which console functions remain available when a dependency fails." }, { "name": "Control identification condition", "kind": "state", "unit_or_values": "legible and verified; damaged; missing; mismatched; unknown", "why_it_matters": "Incorrect or unreadable labels can make an otherwise functional console unsafe to operate." } ], "affordances": [ "Identify the equipment addressed by each console control and display.", "Assess whether the operator can see feedback and reach the required controls.", "Determine whether the console holds authority to issue a proposed command.", "Issue a permitted command using the applicable operating procedure and verify its result.", "Diagnose whether lost interaction originates in console power, communications, controls or feedback.", "Prepare the console for inspection or service while accounting for other control stations." ], "agent_conduct": { "may": [ "Monitor displays and report alarms on a console it is authorized to observe.", "Operate controls on a console within the authority the operator has delegated." ], "must_not": [ "Silence, bypass or acknowledge alarms without the operator's knowledge.", "Operate controls of a system it is not authorized to run.", "Leave a console unattended when its procedures require a person.", "Change console configurations without change control." ], "requires_human": [ "Operating controls that affect safety, such as in a plant, vessel or control room.", "Handing over a console between shifts." ] }, "ethics": { "considerations": [ "Operators at consoles control processes that affect public safety.", "Alarm overload and fatigue lead to errors." ], "affected_parties": [ "Operators", "People affected by the controlled system", "Maintenance staff" ] }, "owners": { "steward": "The operator of the system it controls.", "master_systems": [] }, "visual_identification": [ "A desk or cabinet with screens, switches, buttons and indicators at an operator position.", "Labels and alarm lights grouped by system or function." ], "failure_modes_and_hazards": [ "Missed or suppressed alarms can let incidents escalate.", "Poor layout causes operator errors." ], "standards_and_regulation": [ "ISO 11064, Ergonomic design of control centres, International Organization for Standardization." ], "what_it_is_for": [ "A console table stands against a wall in an entrance hall, corridor, living room, or similar interior.", "Its shallow surface provides space for small belongings, lighting, or decorative objects where a deeper table would obstruct circulation." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q7887380: console", "url": "https://www.wikidata.org/wiki/Q7887380", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Console table", "url": "https://en.wikipedia.org/wiki/Console_table", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "console-identity-and-boundary", "name": "Console identity and boundary", "description": "Establishes the intended meaning of console and its relationship to the operated system.", "rationale": "The unqualified name can denote materially different kinds of things, and an operator console must not be conflated with its target equipment.", "layers": [ { "id": "registered-sense", "name": "Registered sense", "description": "Tests whether the registry entry denotes a physical operator console.", "findings": [ { "id": "operator-console-sense", "name": "Operator console sense", "description": "Record evidence supporting or rejecting the provisional interpretation as a physical operator interface.", "questions": [ { "text": "What registry provenance or source definition establishes which meaning of console this entry denotes?", "kind": "provenance", "id": "operator-console-sense-q01" }, { "text": "Does the intended kind group controls and feedback for an operator, or does it denote gaming hardware, furniture or another sense?", "kind": "definition", "id": "operator-console-sense-q02" } ] } ] }, { "id": "assembly-and-targets", "name": "Assembly and targets", "description": "Separates console components from the equipment they operate.", "findings": [ { "id": "console-system-boundary", "name": "Console-to-system boundary", "description": "Identify what belongs to the console assembly and what is only connected to or controlled through it.", "questions": [ { "text": "Which controls, displays, processors and support structures belong to the console assembly?", "kind": "boundary", "id": "console-system-boundary-q01" }, { "text": "Which external systems receive its commands or supply its feedback?", "kind": "boundary", "id": "console-system-boundary-q02" } ] } ] } ] }, { "id": "operator-layout-and-command-meaning", "name": "Operator layout and command meaning", "description": "Records how an operator interprets and physically uses the console.", "rationale": "Console usability depends on the relationship between control placement, displayed information and the meaning of each input.", "layers": [ { "id": "controls-and-indications", "name": "Controls and indications", "description": "Connects operator inputs and feedback to their actual functions.", "findings": [ { "id": "control-feedback-mapping", "name": "Control and feedback mapping", "description": "Record the target, command and confirmation associated with each relevant interaction.", "questions": [ { "text": "What function does each control invoke, and does that function change with mode or screen context?", "kind": "definition", "id": "control-feedback-mapping-q01" }, { "text": "What indication confirms command receipt, and what separate evidence confirms the equipment performed the action?", "kind": "action", "id": "control-feedback-mapping-q02" } ] } ] }, { "id": "operator-position", "name": "Operator position", "description": "Assesses the physical relationship between operator, controls and displays.", "findings": [ { "id": "reach-and-visibility", "name": "Reach and visibility", "description": "Record console geometry and conditions affecting access to controls and interpretation of feedback.", "questions": [ { "text": "What are the heights, reach distances and viewing angles of frequently used and urgent controls from the intended operator position?", "kind": "measurement", "id": "reach-and-visibility-q01" }, { "text": "Which labels or displays become obscured, unreadable or difficult to distinguish under intended lighting and use conditions?", "kind": "measurement", "id": "reach-and-visibility-q02" } ] } ] } ] }, { "id": "authority-modes-and-connections", "name": "Authority, modes and connections", "description": "Establishes when console interactions can affect the intended equipment.", "rationale": "A console can appear operational while lacking control authority, a working command path or valid feedback.", "layers": [ { "id": "command-authority", "name": "Command authority", "description": "Records who or what may control the system through this console.", "findings": [ { "id": "mode-and-station-selection", "name": "Mode and station selection", "description": "Identify command permissions and their dependence on operating mode, operator access and other stations.", "questions": [ { "text": "Which modes enable, inhibit or reinterpret commands from this console?", "kind": "definition", "id": "mode-and-station-selection-q01" }, { "text": "How is authority acquired, transferred or relinquished when another console or automatic controller can operate the same equipment?", "kind": "action", "id": "mode-and-station-selection-q02" } ] } ] }, { "id": "command-and-feedback-paths", "name": "Command and feedback paths", "description": "Records the dependencies that carry commands and return system state.", "findings": [ { "id": "connection-loss-behaviour", "name": "Connection-loss behaviour", "description": "Establish what happens when console power, command transmission or feedback is interrupted.", "questions": [ { "text": "Which power supplies and communication paths support commands, displays and any independent protective controls?", "kind": "boundary", "id": "connection-loss-behaviour-q01" }, { "text": "What happens to pending commands and displayed values when a connection fails or is restored?", "kind": "action", "id": "connection-loss-behaviour-q02" }, { "text": "How can an operator determine the age and validity of displayed feedback?", "kind": "measurement", "id": "connection-loss-behaviour-q03" } ] } ] } ] }, { "id": "safe-operation-and-service", "name": "Safe operation and service", "description": "Supports decisions about consequential inputs, degraded operation and console maintenance.", "rationale": "Console actions can affect equipment beyond the operator's immediate view, and servicing the console may leave other control paths active.", "layers": [ { "id": "consequential-controls", "name": "Consequential controls", "description": "Identifies safeguards and conditions for commands with significant effects.", "findings": [ { "id": "command-safeguards", "name": "Command safeguards", "description": "Record verified protections against unintended inputs and the limits of any stop or inhibit function.", "questions": [ { "text": "Which commands require guards, confirmation, deliberate sequences or permissive conditions, and what evidence establishes those requirements?", "kind": "provenance", "id": "command-safeguards-q01" }, { "text": "If a stop or inhibit control exists, which equipment does it affect and under what conditions is it effective?", "kind": "boundary", "id": "command-safeguards-q02" }, { "text": "Which commands must be withheld when feedback or target identification is uncertain?", "kind": "action", "id": "command-safeguards-q03" } ] } ] }, { "id": "inspection-and-restoration", "name": "Inspection and restoration", "description": "Addresses console defects and verification after intervention.", "findings": [ { "id": "console-service-readiness", "name": "Console service readiness", "description": "Record inspection criteria, service dependencies and the checks needed to restore reliable interaction.", "questions": [ { "text": "Which defects in controls, labels, displays or connectors require restricting console use under the applicable procedure?", "kind": "action", "id": "console-service-readiness-q01" }, { "text": "How must remote or automatic control paths be accounted for before servicing the console?", "kind": "action", "id": "console-service-readiness-q02" }, { "text": "What checks verify control mappings, feedback and authority after replacement, reconfiguration or repair?", "kind": "action", "id": "console-service-readiness-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": [ "The registry supplies no sense: the operator-equipment interpretation is provisional, and PHY.OBJ also permits a video game console, console table, or architectural console.", "The listed kinds apply to the operator-equipment interpretation and should not be treated as confirmed registry scope.", "Dimensions, ratings, identifier schemes, and applicable standards depend on the intended console type; none can safely be assigned from the name alone." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of console 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": [ "Industrial operator console", "Audio mixing console", "Lighting control console", "Broadcast production console", "Vehicle operator console", "Organ console" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of console 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": [ "Monitoring and controlling industrial processes", "Combining and adjusting audio signals", "Programming and operating stage lighting", "Selecting and coordinating broadcast signals", "Grouping vehicle controls and instruments within an operator's reach" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of console 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": [ "Ambiguous labels or poorly arranged controls can cause operator errors.", "Failed or stale displays can conceal the actual state of the controlled system.", "Communication failures can prevent commands or status updates from reaching their destination.", "Electrical faults in powered consoles can create shock, overheating, or fire hazards.", "Poor positioning of controls and displays can contribute to fatigue and musculoskeletal strain." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of console 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": "Control panel", "difference": "A control panel is a surface or assembly carrying controls and indicators; a console generally integrates these into an operator station and may contain several panels." }, { "name": "Workstation", "difference": "A workstation supports an individual's work more generally; a console specifically concentrates the interface for operating or monitoring a system." }, { "name": "Video game console", "difference": "A video game console is a computing device primarily intended to run games; its controllers and display can be separate from the device." }, { "name": "Software console", "difference": "A software console is a logical interface for commands or status information rather than the physical assembly described here." }, { "name": "Console table", "difference": "A console table is furniture for supporting objects rather than an assembly for controlling a system." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of console this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.console denote an operator console, video game console, furniture console or another physical sense?", "Does an existing world model already cover the confirmed sense and therefore provide the authoritative publication?", "Which console subtypes belong within the registered kind, and which require links to neighbouring models?", "Which issuing bodies, standards and conformity requirements apply once the console's intended sector and use are established?", "Which sources establish representative dimensions, operating limits, failure behaviour and service requirements without treating one product's specifications as universal?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 13, "questions": 24 } }