{ "model": { "rank": 3940, "code": "thing-q5607", "model_id": "vr.tr.modem", "name": "modem", "purpose": "Enable an agent to recognise a modem, assess its communication readiness and condition, and determine which connection, configuration, diagnostic and recovery actions are appropriate.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q5607/", "tier": 2, "score": 80, "payload": { "layer": "wikidata", "aliases": [ "ISDN card", "Sportster 14,400", "Mobidem", "D01NX", "D22HW", "DSL modem", "Popcom", "DBT-03", "Courier", "56k modem", "Sportster", "Sportster 2400", "Sportster 1200", "Sportster 9600", "Sportster 28,800", "Sportster 33,600", "Sportster 56K", "mobile broadband modem", "Novation CAT", "wideband modem", "parallel transmission modem", "Snapdragon X12 LTE modem", "Snapdragon X10 LTE modem", "Softmodem", "Family Computer Network System", "XMM 7480", "ZyXEL Elite 2864", "Internet key", "Terminal node controller", "cable modem", "Bell 101", "Fax modem", "Snapdragon X24 LTE Modem", "Snapdragon X20 LTE Modem", "Snapdragon X50 Modem", "Intel XMM modems", "Narrowband modem", "Qualcomm Gobi", "satellite modem", "Bell 202 modem" ], "aliasCount": 53, "merged": 53, "knownIn": 80, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.modem", "source": { "dataset": "wikidata", "item": "Q5607", "url": "https://www.wikidata.org/wiki/Q5607", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T19:07:26Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 29.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08790-4680-7252-81a2-81babcfcaa21\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: modem\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 registered", "usd": 0, "recall": true }, "codex": { "seconds": 72, "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: 01a08790-4688-73d1-9904-c66a9f2c2d0d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: modem\nRegistry id: vr.tr.modem\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for " } } }, "metaModel": { "id": "THING-Q5607", "registryId": "vr.tr.modem", "name": "modem", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5607/", "model": { "registry_id": "vr.tr.modem", "name": "modem", "purpose": "Enable an agent to recognise a modem, assess its communication readiness and condition, and determine which connection, configuration, diagnostic and recovery actions are appropriate.", "definition": "A modem is a communications device or functional subsystem that modulates a signal to encode digital data for transmission over a communications channel and demodulates received signals to recover digital data.", "scope_statement": "This model owns the modem as a physical device kind defined by modulation and demodulation for a communication link, including dedicated devices and modem functions embedded in larger equipment; product specifications and individual-unit observations supply evidence without defining separate kinds.", "in_scope": [ "Conversion between host-side data and signals carried over the supported communication medium", "Link technology, peer compatibility, negotiation and registration requirements", "Host, line, antenna and power interfaces relevant to modem operation", "Link state, signal quality, negotiated rates and modem-specific diagnostics", "Provisioning, firmware, configuration, maintenance and permitted recovery actions" ], "out_of_scope": [ "Routing, firewall, Wi-Fi access-point and switching functions bundled into a gateway", "Provider access networks, subscriber contracts and billing arrangements", "Applications, remote services and end-to-end Internet performance beyond the modem link", "Standalone antennas, external cabling and power supplies as independently maintained things", "General-purpose software implementations without an identified physical modem host" ], "distinguishing_features": [ "Identify a function that both produces a communication-medium waveform from data and recovers data from a received waveform; packet forwarding alone does not establish modem identity.", "Distinguish a router's selection of packet paths from the modem's establishment and operation of the underlying communication link, even when one enclosure performs both functions.", "Distinguish a modem from a bare radio transceiver by evidence of the data modulation and demodulation function rather than transmission and reception alone.", "Identify the supported link family and compatible peer or access equipment; an Ethernet socket, SIM slot or antenna connector alone is insufficient evidence.", "For an embedded modem, locate the functional boundary between the modem, its host and any shared processor, power or antenna resources." ], "characteristics": [ { "name": "Communication medium and link family", "kind": "category", "unit_or_values": "Documented family and medium, such as telephone-band, DSL, cable, cellular or another radio link", "why_it_matters": "Determines which connections, diagnostics and compatibility checks apply." }, { "name": "Supported link specifications", "kind": "relation", "unit_or_values": "Specification identifier, issuing body, revision, supported profile and evidence source", "why_it_matters": "Allows compatibility to be judged against an explicit specification rather than a marketing label." }, { "name": "Modem integration", "kind": "category", "unit_or_values": "Dedicated external device, internal module, embedded subsystem or modem within a multifunction gateway", "why_it_matters": "Locates the modem boundary and identifies shared resources affected by an action." }, { "name": "Host and medium interfaces", "kind": "category", "unit_or_values": "Interface role, connector, electrical or radio specification and supported operating mode", "why_it_matters": "Prevents incompatible attachment and distinguishes data, line, antenna and management connections." }, { "name": "Transmit and receive capability", "kind": "category", "unit_or_values": "Supported modulation, coding, duplex modes, channels and frequency ranges where applicable", "why_it_matters": "Defines the signal capabilities required for a compatible link." }, { "name": "Negotiated link rate", "kind": "measurement", "unit_or_values": "bit/s separately for each direction, with timestamp and rate definition", "why_it_matters": "Separates the active link's capacity from advertised capability and measured application throughput." }, { "name": "Medium-specific signal quality", "kind": "measurement", "unit_or_values": "Named metric with its native unit, such as dB or dBm where applicable, direction, channel and timestamp", "why_it_matters": "Supports diagnosis without treating unlike signal metrics as interchangeable." }, { "name": "Communication state", "kind": "state", "unit_or_values": "Observed vendor state mapped where possible to powered off, initialising, searching, training, synchronised, registered, data ready, degraded or faulted", "why_it_matters": "Determines whether the modem is ready for traffic and where establishment has stopped." }, { "name": "Provisioning dependency", "kind": "relation", "unit_or_values": "Required provider acceptance, subscriber credential reference, device identity registration or peer configuration; none or unknown where appropriate", "why_it_matters": "Explains why a technically compatible modem may still lack service." }, { "name": "Error and interruption history", "kind": "measurement", "unit_or_values": "Named counter, count or rate, observation interval, reset time and relevant link or channel", "why_it_matters": "Distinguishes persistent degradation from isolated errors and counter-reset effects." }, { "name": "Power requirements", "kind": "measurement", "unit_or_values": "Rated input V, A and W as documented, supply type and connector or bus-power requirements", "why_it_matters": "Supports supply compatibility checks and investigation of resets or unstable operation." }, { "name": "Firmware and configuration identity", "kind": "relation", "unit_or_values": "Firmware version, hardware revision, configuration profile and management authority", "why_it_matters": "Makes supported features, diagnostic behaviour and permissible changes traceable." } ], "affordances": [ "Check a candidate modem against the intended medium, peer, provider requirements and host interface.", "Attach compatible line, antenna, host and power connections using documented installation constraints.", "Provision permitted link settings and initiate or restore a connection.", "Read link states, signal metrics and event history to isolate likely modem, medium, host or provisioning faults.", "Apply authorised firmware or configuration changes while accounting for service interruption and recovery.", "Reset, replace or decommission the modem with appropriate handling of credentials and provider registration." ] }, "sources": [], "structure": { "bundles": [ { "id": "modem-identity-and-boundary", "name": "Modem identity and boundary", "description": "Establishes what performs modulation and demodulation and separates it from neighbouring device functions.", "rationale": "A modem may be a dedicated device or one subsystem of a gateway, so enclosure labels alone cannot establish its identity or responsibilities.", "layers": [ { "id": "data-to-signal-function", "name": "Data-to-signal function", "description": "Identifies the communication medium and the conversion function that makes the thing a modem.", "findings": [ { "id": "modulation-demodulation-evidence", "name": "Modulation and demodulation evidence", "description": "Record evidence of the outbound and inbound signal conversion without assuming every network adapter is a modem.", "questions": [ { "text": "Which data input is converted into which transmitted signal, and how is received data recovered?", "kind": "definition", "id": "modulation-demodulation-evidence-q01" }, { "text": "Which manufacturer documentation or interface specification identifies this modem function and its supported medium?", "kind": "provenance", "id": "modulation-demodulation-evidence-q02" } ] } ] }, { "id": "integration-boundary", "name": "Integration boundary", "description": "Locates modem responsibilities within standalone, embedded and multifunction equipment.", "findings": [ { "id": "host-and-gateway-separation", "name": "Host and gateway separation", "description": "Record which functions belong to the modem and which depend on its host or a bundled router.", "questions": [ { "text": "Where does the modem link function end and host networking, routing or Wi-Fi operation begin?", "kind": "boundary", "id": "host-and-gateway-separation-q01" }, { "text": "Which processor, antenna, power and management resources are shared with other functions?", "kind": "boundary", "id": "host-and-gateway-separation-q02" } ] } ] } ] }, { "id": "signal-path-and-compatibility", "name": "Signal path and compatibility", "description": "Describes the physical attachments and signal capabilities needed for a usable modem link.", "rationale": "A matching connector does not establish electrical, radio, protocol or peer compatibility.", "layers": [ { "id": "physical-attachments", "name": "Physical attachments", "description": "Identifies host, medium, antenna and power connections with their relevant constraints.", "findings": [ { "id": "connection-role-and-rating", "name": "Connection role and rating", "description": "Record each attachment by function and documented compatibility requirements.", "questions": [ { "text": "Which interfaces carry host data, medium signals, antenna signals, management traffic and power?", "kind": "definition", "id": "connection-role-and-rating-q01" }, { "text": "Which cable, impedance, voltage, antenna or bus-power requirements must be satisfied before attachment?", "kind": "action", "id": "connection-role-and-rating-q02" } ] } ] }, { "id": "supported-link-profiles", "name": "Supported link profiles", "description": "Captures the specifications and operating profiles that determine communication compatibility.", "findings": [ { "id": "peer-and-profile-match", "name": "Peer and profile match", "description": "Record compatible link families, profiles and peer requirements with applicability evidence.", "questions": [ { "text": "Which specification identifiers, issuing bodies, revisions and profiles describe the supported link?", "kind": "provenance", "id": "peer-and-profile-match-q01" }, { "text": "Which frequency ranges, modulation and coding options, duplex modes or channel combinations must match the intended peer?", "kind": "boundary", "id": "peer-and-profile-match-q02" }, { "text": "Which capability limits depend on hardware revision, firmware, region or provider configuration?", "kind": "boundary", "id": "peer-and-profile-match-q03" } ] } ] } ] }, { "id": "link-establishment-and-provisioning", "name": "Link establishment and provisioning", "description": "Tracks the prerequisites and stages between power-up and a link ready to carry data.", "rationale": "Signal acquisition, link synchronisation, network acceptance and usable data service are distinct conditions.", "layers": [ { "id": "service-prerequisites", "name": "Service prerequisites", "description": "Identifies credentials, registrations and peer settings required by the particular modem family.", "findings": [ { "id": "identity-and-service-acceptance", "name": "Identity and service acceptance", "description": "Record applicable provisioning dependencies using credential references rather than secret values.", "questions": [ { "text": "Does this link require subscriber credentials, a SIM or eSIM profile, device registration, dial parameters or another provisioning mechanism?", "kind": "definition", "id": "identity-and-service-acceptance-q01" }, { "text": "Which prerequisites can the local operator change, and which require the provider or remote peer?", "kind": "action", "id": "identity-and-service-acceptance-q02" } ] } ] }, { "id": "connection-state-progression", "name": "Connection state progression", "description": "Maps reported indicators and events to the stages of link establishment and loss.", "findings": [ { "id": "state-and-readiness-evidence", "name": "State and readiness evidence", "description": "Record the actual device state vocabulary and evidence for readiness without relying solely on indicator colour.", "questions": [ { "text": "Which reported states distinguish acquisition or training, synchronisation, registration and readiness to carry data for this modem?", "kind": "definition", "id": "state-and-readiness-evidence-q01" }, { "text": "What observation confirms modem-link readiness separately from host addressing and remote-service reachability?", "kind": "measurement", "id": "state-and-readiness-evidence-q02" }, { "text": "Which failed transition is reported, and what retry or reconnection action is documented for it?", "kind": "action", "id": "state-and-readiness-evidence-q03" } ] } ] } ] }, { "id": "link-quality-and-fault-isolation", "name": "Link quality and fault isolation", "description": "Connects performance observations and error history to the modem link and its dependencies.", "rationale": "Slow or interrupted communication can arise from signal conditions, provisioning, the host or the wider network, requiring evidence that distinguishes these causes.", "layers": [ { "id": "capacity-and-signal-observations", "name": "Capacity and signal observations", "description": "Records directional link rates and medium-specific signal metrics with measurement context.", "findings": [ { "id": "rate-and-quality-interpretation", "name": "Rate and quality interpretation", "description": "Keep advertised limits, negotiated link rates and observed throughput distinct.", "questions": [ { "text": "What are the current transmit and receive link rates in bit/s, and what overhead or aggregation does each reported rate include?", "kind": "measurement", "id": "rate-and-quality-interpretation-q01" }, { "text": "Which signal metrics does this modem expose, in which units and for which channels and directions?", "kind": "measurement", "id": "rate-and-quality-interpretation-q02" }, { "text": "What documented reference supports interpreting these metrics for this link family and operating profile?", "kind": "provenance", "id": "rate-and-quality-interpretation-q03" } ] } ] }, { "id": "errors-and-interruptions", "name": "Errors and interruptions", "description": "Uses counters, retraining events, disconnections and controlled checks to narrow fault causes.", "findings": [ { "id": "fault-localisation-evidence", "name": "Fault localisation evidence", "description": "Associate symptoms with time-bounded observations before assigning a cause or performing disruptive recovery.", "questions": [ { "text": "Which error, retransmission, retraining or disconnection events occurred, over what interval and since which counter reset?", "kind": "measurement", "id": "fault-localisation-evidence-q01" }, { "text": "Which observations distinguish a medium fault from power instability, host-interface failure, provisioning rejection or an upstream outage?", "kind": "boundary", "id": "fault-localisation-evidence-q02" }, { "text": "Which documented diagnostic check can narrow the cause, and will it interrupt the active link?", "kind": "action", "id": "fault-localisation-evidence-q03" } ] } ] } ] }, { "id": "configuration-and-service-lifecycle", "name": "Configuration and service lifecycle", "description": "Governs management access, changes, installation conditions and recovery throughout modem use.", "rationale": "Modem changes can remove connectivity or provisioning, while physical installation and lifecycle state affect reliable and permitted operation.", "layers": [ { "id": "management-and-recovery", "name": "Management and recovery", "description": "Identifies management authority and the effects of firmware, profile and reset operations.", "findings": [ { "id": "controlled-modem-changes", "name": "Controlled modem changes", "description": "Record who controls settings and how service can be recovered after an authorised change.", "questions": [ { "text": "Which local, host-mediated or provider-controlled management interfaces exist, and who may use them?", "kind": "action", "id": "controlled-modem-changes-q01" }, { "text": "Which firmware and configuration versions are active, and what source establishes their compatibility with this hardware and service?", "kind": "provenance", "id": "controlled-modem-changes-q02" }, { "text": "How do reconnect, reboot, factory reset and firmware update differ in service interruption, retained settings and recovery requirements?", "kind": "action", "id": "controlled-modem-changes-q03" } ] } ] }, { "id": "installation-and-retirement", "name": "Installation and retirement", "description": "Captures modem-specific physical constraints, approval evidence and removal from service.", "findings": [ { "id": "safe-installation-and-decommissioning", "name": "Safe installation and decommissioning", "description": "Record applicable supply, ventilation, line or antenna constraints and the steps needed to retire a provisioned modem.", "questions": [ { "text": "Which documented power, temperature, ventilation, line-protection or antenna-installation limits apply to this modem variant?", "kind": "provenance", "id": "safe-installation-and-decommissioning-q01" }, { "text": "Which certification marks or approval records apply to this hardware, link technology and intended jurisdiction?", "kind": "provenance", "id": "safe-installation-and-decommissioning-q02" }, { "text": "Before replacement or disposal, which credentials, SIM or eSIM profiles, provider bindings and stored settings require removal or transfer?", "kind": "action", "id": "safe-installation-and-decommissioning-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This entry covers the device class, including embedded modem subsystems, rather than a particular product or physical unit.", "Standards and identifiers are recalled without source consultation; their applicable editions and technology-specific requirements need verification.", "Line rates are not application throughput; modern DSL, cable, cellular and satellite capacities require technology- and deployment-specific treatment." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of modem 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": [ "Voice-band dial-up modem", "DSL modem", "Cable modem", "Cellular modem", "Satellite modem", "Short-range radio modem" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of modem this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Manufacturer model number and serial number", "value_or_pattern": "Manufacturer-specific strings", "note": "The model number identifies a product design; the serial number identifies an individual unit." }, { "scheme": "IMEI", "value_or_pattern": "15 decimal digits", "note": "Identifies cellular equipment; applicable to many cellular modems, not to modems generally." }, { "scheme": "IEEE MAC address", "value_or_pattern": "48-bit address, commonly written as six hexadecimal octets", "note": "Identifies applicable network interfaces, including cable-modem interfaces; a device may have multiple addresses." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of modem this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "ITU-T Recommendation V.92 specifies enhancements for voice-band modems supporting downstream rates up to 56 kbit/s.", "ITU-T Recommendation G.992.1 specifies asymmetric digital subscriber line (ADSL) transceivers.", "ITU-T Recommendation G.993.2 specifies very-high-speed digital subscriber line transceivers 2 (VDSL2).", "CableLabs DOCSIS specifications govern data transmission and interoperability for cable modems.", "3GPP specifications define cellular radio technologies and protocol requirements used by cellular modems." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of modem 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": [ "Providing household and business internet access over telephone pairs or cable networks", "Connecting computers and embedded systems to cellular data networks", "Providing satellite data links at remote sites", "Carrying telemetry and industrial monitoring data over radio links", "Supporting legacy dial-up data connections" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of modem 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": "Negotiated downstream line rate for later-generation voice-band dial-up modems", "typical_range": "Approximately 28.8-56, depending on line conditions and network support", "unit": "kbit/s" }, { "quantity": "Nominal downstream line-rate capability of G.992.1 ADSL", "typical_range": "Up to approximately 8; actual service rates depend on loop length, noise and provisioning", "unit": "Mbit/s" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of modem 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": [ "Noise, attenuation or interference can cause errors, reduced negotiated rates and loss of synchronization.", "Incompatible protocols, provisioning or authentication settings can prevent connection despite intact hardware.", "Power-supply faults and overheating can cause resets or permanent failure.", "Lightning-induced surges on power, telephone or coaxial connections can damage equipment and create electrical hazards.", "Vulnerable firmware or exposed management interfaces can permit unauthorized access or disruption." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of modem this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Cellular frequency bands and operator certification requirements vary by country and network.", "Telephone-network interfaces and DSL deployment profiles vary among operators and regions.", "Cable-network channel plans and DOCSIS deployment generations vary among operators and regions." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of modem 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": "Router", "difference": "A router forwards packets between networks; a modem performs modulation and demodulation for a communications link, although one product can contain both." }, { "name": "Network switch", "difference": "A switch forwards frames among network ports; this forwarding role does not itself make it a modem." }, { "name": "Transceiver", "difference": "A transceiver both transmits and receives; a modem specifically encodes and recovers data through modulation and demodulation." }, { "name": "Wi-Fi access point", "difference": "An access point connects wireless stations to a local network; products combining it with a modem perform two distinct roles." }, { "name": "Optical network terminal", "difference": "An optical network terminal terminates a passive optical access network and its associated protocols; calling it a modem is common informally but does not specify that network role." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of modem this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover modem, requiring this registry entry to link to that source of truth?", "Where should this registry draw the modem boundary for optical network terminals, Ethernet physical-layer devices, software-defined radios and host-based softmodems?", "Which link-family specifications and issuing bodies should anchor researched profiles for telephone-band, DSL, cable, cellular and other radio modems?", "Which signal metrics, reference ranges, rate definitions and fault indicators can be supported by primary documentation for each link family?", "Which representative device documents establish typical capacities, dimensions, maintenance needs and jurisdiction-specific approvals without generalising product-specific claims to all modems?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 35 } }, "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. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "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 modem, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a modem, assess its communication readiness and condition, and determine which connection, configuration, diagnostic and recovery actions are appropriate.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: ISDN card, Sportster 14,400, Mobidem, D01NX, D22HW, DSL modem, Popcom, DBT-03, Courier, 56k modem, Sportster, Sportster 2400.", "53 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 80 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "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 modem, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "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": [ "ISDN card", "Sportster 14,400", "Mobidem", "D01NX", "D22HW", "DSL modem", "Popcom", "DBT-03", "Courier", "56k modem", "Sportster", "Sportster 2400" ] } ], "standing": "Described in 80 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 53 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 modem from another, and a modem 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 modem, 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 modem, 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 modem 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 modem, 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 modem, 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 modem 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 modem 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 modem, 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 modem, 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 modem 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 modem from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a modem, 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 modem, 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 modem 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 modem 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.", "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 modem, 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 modem, 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 modem 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 modem is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a modem, 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 modem, 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 modem 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 modem is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a modem, 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 modem, 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 modem 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 modem is, how it got there and where it may go (varies).", "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 modem is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a modem, 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 modem, 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 modem 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 modem 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 modem, 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 modem, 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 modem 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 modem 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 modem between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a modem, 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 modem, 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 modem 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 modem, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a modem 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 modem, 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 modem, 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 modem 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 modem 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 modem 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 modem, 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 modem 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 modem 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 modem 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 modem 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 modem 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 modem, 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 modem 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 modem and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a modem, 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 modem, 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 modem 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 modem is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a modem, 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 modem, 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 modem 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 } } } }