{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:26:49Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.9, "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: 01a0955d-d504-7861-ad4a-2afab8818a96\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: multitap\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 regist", "usd": 0.0, "recall": true }, "codex": { "seconds": 60.4, "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: 01a0955d-d516-7562-adf6-d037fc5fefa6\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: multitap\nRegistry id: vr.tr.multitap\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContex" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:42:12+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:26+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1537770", "registryId": "vr.tr.multitap", "name": "multitap", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1537770/", "model": { "registry_id": "vr.tr.multitap", "name": "multitap", "purpose": "Enable an AI agent to recognise a video-game controller multitap, assess its compatibility and condition, and determine how it can support additional players.", "definition": "In video gaming, a multitap is a console-specific adapter that connects multiple controllers through a console controller port, allowing compatible software to support additional simultaneous players.", "scope_statement": "Provisionally, this model owns the physical adapter that connects multiple game controllers through a console controller interface, including its port topology, controller identification, game support and operating states; the registry's intended sense of 'multitap' remains unconfirmed.", "in_scope": [ "Console-facing connection and downstream controller ports", "Controller signalling, selection and player-slot mapping", "Compatibility with consoles, controllers and individual games", "Power requirements, operating modes and connection procedures", "Faults affecting controller detection or simultaneous play" ], "out_of_scope": [ "Electrical power strips or multi-outlet adapters also called multitaps", "Multi-tap text entry on telephone keypads", "Game controllers and their internal input mechanisms", "Console hardware beyond the multitap interface", "Game rules, multiplayer design and network matchmaking" ], "distinguishing_features": [ "Provides multiple downstream controller connections through a shared console-facing controller interface.", "Keeps controller inputs distinguishable through a supported signalling or selection mechanism; connector multiplication alone does not establish multitap functionality.", "Expands locally addressable controller connections rather than providing network sessions or online player capacity.", "Requires compatibility to be assessed at the console, controller and game levels; matching plugs alone are insufficient.", "Is distinguished from a generic USB hub by evidence of its role in the console's supported controller-expansion arrangement." ], "characteristics": [ { "name": "Console interface", "kind": "category", "unit_or_values": "Connector family, signalling interface and documented console family", "why_it_matters": "Determines whether physical connection and controller communication are possible." }, { "name": "Downstream controller-port count", "kind": "measurement", "unit_or_values": "controller ports", "why_it_matters": "Records physical connection capacity without equating it to supported player count." }, { "name": "Console ports occupied", "kind": "measurement", "unit_or_values": "console controller ports", "why_it_matters": "Shows how the adapter affects other direct controller connections." }, { "name": "Supported simultaneous controller count", "kind": "measurement", "unit_or_values": "controllers, qualified by console, game and adapter configuration", "why_it_matters": "Separates usable input capacity from the number of visible sockets." }, { "name": "Controller and game compatibility", "kind": "relation", "unit_or_values": "Documented or tested combinations of console revision, adapter variant, controller type and game version", "why_it_matters": "A functioning adapter may still be unsupported by a particular combination." }, { "name": "Player-slot mapping", "kind": "relation", "unit_or_values": "Mapping between physical controller ports and game-visible controller or player slots", "why_it_matters": "Allows an agent to connect controllers to the intended players and diagnose crossed assignments." }, { "name": "Operating mode", "kind": "state", "unit_or_values": "Device-labelled modes, fixed operation, or unknown", "why_it_matters": "Where a selector exists, its setting may affect controller detection and game support." }, { "name": "Power arrangement", "kind": "category", "unit_or_values": "Host-supplied, externally supplied, other documented arrangement, or unknown; ratings in V and mA where available", "why_it_matters": "Constrains which connected accessories and operating combinations are supported." }, { "name": "Port detection condition", "kind": "state", "unit_or_values": "Untested, consistently detected, intermittently detected, undetected, or physically damaged", "why_it_matters": "Supports port-specific diagnosis without treating compatibility failures as proven hardware defects." } ], "affordances": [ "Select a multitap for a documented console, game and controller combination.", "Connect controllers and establish their game-visible player assignments.", "Set an available operating selector according to the adapter and game's instructions.", "Test controller detection and simultaneous input across downstream ports.", "Isolate faults by comparing known-working controllers, ports and supported games.", "Determine whether a proposed multi-adapter arrangement is supported." ], "agent_conduct": { "may": [ "Identify a multitap and the console it was made for.", "Explain which games support it and how many players it allows." ], "must_not": [ "Describe an adapter as compatible with a console or game without evidence.", "Sell or describe a third-party or reproduction adapter as original.", "Recommend modifying old adapters in ways that risk damaging consoles." ], "requires_human": [ "Selling or trading collectible hardware on someone's behalf." ] }, "ethics": { "considerations": [ "Shared play brings people together; accessible hardware matters for disabled players.", "Collectors can be misled by false claims of authenticity." ], "affected_parties": [ "Players", "Collectors", "Buyers" ] }, "owners": { "steward": "The person who owns the adapter.", "master_systems": [] }, "visual_identification": [ "A small box with one cable or plug for the console and several controller ports.", "Port shapes match a specific console's controller connector." ], "failure_modes_and_hazards": [ "Incompatible adapters can fail to work or cause input errors.", "Old electronics may have damaged cables or contacts." ], "what_it_is_for": [ "A multitap is used with compatible video game consoles when a game supports more simultaneous controllers than the console can connect directly.", "It is encountered in local multiplayer setups and collections of older gaming equipment, where connector fit alone does not establish compatibility." ], "standards_and_regulation": [ "IEC 62368-1, issued by the International Electrotechnical Commission, provides product safety requirements for audio, video and information technology equipment, including electronic peripherals within its scope." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1537770: multitap", "url": "https://www.wikidata.org/wiki/Q1537770", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Multitap", "url": "https://en.wikipedia.org/wiki/Multitap", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "identity-and-interface-boundary", "name": "Identity and interface boundary", "description": "Establishes which sense of multitap is intended and identifies the controller-expansion interface.", "rationale": "The registry supplies no definition, and the name alone does not establish either the object kind or its console compatibility.", "layers": [ { "id": "registered-sense", "name": "Registered sense", "description": "Resolves the meaning of the registry entry before applying controller-specific assumptions.", "findings": [ { "id": "controller-multitap-identification", "name": "Controller multitap identification", "description": "Record evidence that the entry denotes a video-game controller expansion adapter.", "questions": [ { "text": "Does the registry's originating record define multitap as a video-game controller adapter?", "kind": "definition", "id": "controller-multitap-identification-q01" }, { "text": "What originating identifier, description or reference distinguishes this entry from electrical multi-outlet devices?", "kind": "provenance", "id": "controller-multitap-identification-q02" } ] } ] }, { "id": "host-and-controller-connections", "name": "Host and controller connections", "description": "Describes the adapter's connection boundary without confusing connector shape with protocol support.", "findings": [ { "id": "interface-topology", "name": "Interface topology", "description": "Record console-facing plugs, downstream controller sockets and any additional connection roles.", "questions": [ { "text": "Which console interface does the adapter use, and how many console controller ports does it occupy?", "kind": "definition", "id": "interface-topology-q01" }, { "text": "How many downstream sockets accept controllers, and are any sockets reserved for another accessory type?", "kind": "measurement", "id": "interface-topology-q02" } ] } ] } ] }, { "id": "controller-addressing-and-capacity", "name": "Controller addressing and capacity", "description": "Models how connected controllers remain distinguishable and how physical ports translate into usable input capacity.", "rationale": "A multitap's defining function is controller expansion, which cannot be inferred from socket count alone.", "layers": [ { "id": "input-identification", "name": "Input identification", "description": "Captures the documented mechanism for exposing separate controllers to the host.", "findings": [ { "id": "controller-selection-mechanism", "name": "Controller selection mechanism", "description": "Establish how the host selects or identifies controllers connected through the adapter.", "questions": [ { "text": "What documented signalling, polling or selection mechanism distinguishes the downstream controllers?", "kind": "definition", "id": "controller-selection-mechanism-q01" }, { "text": "Which protocol documentation or reproducible observation establishes that mechanism for this adapter variant?", "kind": "provenance", "id": "controller-selection-mechanism-q02" } ] } ] }, { "id": "port-to-player-capacity", "name": "Port-to-player capacity", "description": "Separates physical connectivity, addressable controllers and game-level player assignments.", "findings": [ { "id": "effective-controller-map", "name": "Effective controller map", "description": "Record the effective controller count and assignment map for an explicit operating configuration.", "questions": [ { "text": "How many controllers can the specified console and game read through this arrangement during simultaneous play?", "kind": "measurement", "id": "effective-controller-map-q01" }, { "text": "How do downstream port labels, remaining console ports and any second adapter map to game-visible player slots?", "kind": "boundary", "id": "effective-controller-map-q02" } ] } ] } ] }, { "id": "compatibility-and-configuration", "name": "Compatibility and configuration", "description": "Determines which hardware and software combinations support the adapter and how those combinations must be configured.", "rationale": "Multitap usability depends on the complete console-controller-game combination, including any required selector settings.", "layers": [ { "id": "supported-combinations", "name": "Supported combinations", "description": "Qualifies support by adapter variant, host, controller capabilities and game version.", "findings": [ { "id": "compatibility-evidence", "name": "Compatibility evidence", "description": "Record supported and unsupported combinations with the evidence and limits of each result.", "questions": [ { "text": "Which console revisions, controller types and game versions explicitly support this adapter?", "kind": "provenance", "id": "compatibility-evidence-q01" }, { "text": "Within those combinations, which controller features or specialised peripherals have confirmed support or limitations?", "kind": "boundary", "id": "compatibility-evidence-q02" } ] } ] }, { "id": "operating-selection-and-expansion", "name": "Operating selection and expansion", "description": "Captures available selector positions and supported arrangements involving more than one adapter.", "findings": [ { "id": "valid-setup-procedure", "name": "Valid setup procedure", "description": "Determine the connection order, mode and game setup needed for a supported configuration.", "questions": [ { "text": "What selector setting, connection sequence and in-game configuration do the applicable instructions require?", "kind": "action", "id": "valid-setup-procedure-q01" }, { "text": "Does the documented configuration permit adapters on separate console ports, chained adapters, or neither?", "kind": "boundary", "id": "valid-setup-procedure-q02" } ] } ] } ] }, { "id": "power-and-input-integrity", "name": "Power and input integrity", "description": "Assesses whether the connected arrangement can operate reliably and distinguishes interface faults from unsupported configurations.", "rationale": "Shared connections can create power or signal problems that appear as missing players or intermittent controller input.", "layers": [ { "id": "electrical-operating-envelope", "name": "Electrical operating envelope", "description": "Records documented supply arrangements and connection constraints for the controller-expansion path.", "findings": [ { "id": "supported-electrical-load", "name": "Supported electrical load", "description": "Establish the available power evidence and any restrictions on connected controller accessories.", "questions": [ { "text": "How is the adapter powered, and what voltage, current or connected-accessory limits are documented?", "kind": "measurement", "id": "supported-electrical-load-q01" }, { "text": "What instructions govern connecting or disconnecting the adapter and controllers while the console is powered?", "kind": "action", "id": "supported-electrical-load-q02" } ] } ] }, { "id": "port-level-diagnosis", "name": "Port-level diagnosis", "description": "Uses controlled controller and port comparisons to assess detection and input reliability.", "findings": [ { "id": "fault-isolation-and-return-to-use", "name": "Fault isolation and return to use", "description": "Record observed symptoms, comparison tests and the evidence needed to return an adapter to service.", "questions": [ { "text": "Does a detection or input fault follow the controller, a particular downstream socket, the upstream connection, or the selected game?", "kind": "measurement", "id": "fault-isolation-and-return-to-use-q01" }, { "text": "Which documented inspection or maintenance action addresses the observed fault, and what simultaneous-input test verifies recovery?", "kind": "action", "id": "fault-isolation-and-return-to-use-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The registry supplies no sense; this description assumes the video-game accessory meaning. Check that it does not denote a multiple-outlet electrical adapter.", "Controller capacity, memory-card support, power arrangements and connection rules depend on the console and adapter.", "Physical connection does not establish compatibility: supported games determine the usable player count." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of multitap 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": [ "Controller-only multitaps", "Multitaps incorporating controller and memory-card connections" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of multitap 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": [ "Local multiplayer games requiring more controllers than the console's built-in ports accommodate", "Connecting several players' controllers and, on some systems, memory cards" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of multitap this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Controller connections per adapter", "typical_range": "Commonly 4; some designs provide 5", "unit": "controller ports" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of multitap 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": [ "Unsupported games fail to recognize additional controllers", "Console or controller incompatibility prevents correct operation", "Worn connectors or damaged cables cause intermittent input or disconnections", "Incorrect port placement or mode selection prevents player assignment on systems with those requirements", "Additional controller cables create trip and equipment-pull hazards" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of multitap 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": "USB hub", "difference": "Expands a USB connection for USB devices; a traditional console multitap uses the console's controller interface and requires specific game support." }, { "name": "Controller adapter", "difference": "Changes controller compatibility or connection format without necessarily increasing the number of independently usable controllers." }, { "name": "Power strip", "difference": "Distributes electrical power to multiple outlets; 'multitap' can also refer to this object in some usage." }, { "name": "Multi-tap text entry", "difference": "Is a text-input method using repeated key presses, rather than a physical controller-expansion device." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of multitap this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.multitap actually denote the video-game controller adapter, or does its originating record identify another physical object sense?", "Which existing Vercy model, if any, already owns this concept and should be linked instead of duplicated?", "Which interface families and adapter variants belong under this kind, and where is the boundary with generic hubs or controller converters?", "Which primary manuals or protocol references establish compatibility, mode behaviour, player mapping and multi-adapter limits?", "Which electrical ratings, accessory-load restrictions and applicable compliance requirements are documented for the variants covered?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 22 } }