{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:40:17Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22.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: 01a0956a-03d7-7570-8d15-ba5a42980f7a\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Nokia Communicator\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: 1", "usd": 0.0, "recall": true }, "codex": { "seconds": 69.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: 01a0956a-03dd-76a2-9bf4-431ed0eaede7\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Nokia Communicator\nRegistry id: vr.tr.nokia-communicator\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this en" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:38:45+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:28+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1995636", "registryId": "vr.tr.nokia-communicator", "name": "Nokia Communicator", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1995636/", "model": { "registry_id": "vr.tr.nokia-communicator", "name": "Nokia Communicator", "purpose": "Enable an agent to recognise a Nokia Communicator, assess its generation-specific capabilities and condition, and decide which operation, preservation or repair actions are appropriate.", "definition": "Nokia Communicator is a family of Nokia business-oriented mobile phones combining cellular telephony with personal-organiser and computing functions, characteristically using a folding body that opens to reveal a larger display and a physical QWERTY keyboard.", "scope_statement": "This model owns the Nokia Communicator product-family kind registered as vr.tr.nokia-communicator in PHY / PHY.OBJ, including the distinctions needed to assess particular variants and units without treating one generation's specifications as universal.", "in_scope": [ "Communicator family membership, exact model identification and regional variant distinctions", "Folding enclosure, keyboard, displays and relationship between telephone and communicator interfaces", "Model-dependent operating system, applications, storage and personal information workflows", "Cellular and local connectivity capabilities and present service compatibility", "Battery, mechanical condition, data preservation and repair feasibility" ], "out_of_scope": [ "Nokia as a company, brand owner or manufacturer", "Mobile phones, smartphones and personal digital assistants as broader device kinds", "Other Nokia product families merely sharing a keyboard, hinge or operating system", "Cellular networks, subscriptions and remote services as independently managed systems", "The substantive content of a user's messages, contacts and documents", "Individual units' ownership histories and market valuations except as evidence relevant to identification or handling" ], "distinguishing_features": [ "Establish Communicator family membership from an exact model designation and supporting product documentation; Nokia branding alone is insufficient.", "Check the combination of an exterior telephone interface and an opening interior workspace with a physical text keyboard and larger display against the identified model.", "Distinguish a Communicator from a generic clamshell phone by its documented messaging, organiser and document-oriented workspace.", "Distinguish generations using their documented platform, connectors and radio capabilities; similar Communicator enclosures do not establish software or accessory compatibility." ], "characteristics": [ { "name": "Product and regional variant", "kind": "category", "unit_or_values": "Documented model designation, product code and regional variant; unknown", "why_it_matters": "Determines which specifications, manuals, accessories and service constraints apply." }, { "name": "Family membership evidence", "kind": "relation", "unit_or_values": "Relation to manufacturer documentation or another attributable product record", "why_it_matters": "Prevents visually similar Nokia devices from being included solely by appearance." }, { "name": "Telephone and interior workspace condition", "kind": "state", "unit_or_values": "Separate observed states for exterior controls, interior keyboard, displays and hinge", "why_it_matters": "A working telephone interface does not demonstrate a working interior workspace." }, { "name": "Software platform and firmware", "kind": "category", "unit_or_values": "Observed operating system, interface platform, firmware version and language configuration; unknown", "why_it_matters": "Controls application compatibility, document handling and recovery options." }, { "name": "Cellular radio capability", "kind": "category", "unit_or_values": "Documented radio technologies and supported bands in MHz for the exact variant", "why_it_matters": "Separates original radio capability from compatibility with an available network." }, { "name": "Local transfer interfaces", "kind": "category", "unit_or_values": "Model-specific wired, infrared, Bluetooth, Wi-Fi or removable-media interfaces where documented", "why_it_matters": "Identifies feasible routes for synchronisation, backup and file extraction." }, { "name": "Battery and charging compatibility", "kind": "relation", "unit_or_values": "Battery designation, chemistry, nominal voltage in V and documented compatible charger", "why_it_matters": "Supports safe power-up and prevents substitution based only on connector fit." }, { "name": "Usable storage", "kind": "measurement", "unit_or_values": "Total and free internal or removable storage in MB or GB, with medium and reporting convention", "why_it_matters": "Constrains application use, backup planning and recovery operations." }, { "name": "Enclosure dimensions and mass", "kind": "measurement", "unit_or_values": "Closed dimensions in mm and mass in g, stating whether the battery is included", "why_it_matters": "Supports variant checking, accessory fit and protective storage." }, { "name": "Data accessibility", "kind": "state", "unit_or_values": "Accessible; access-controlled; partially readable; unreadable; untested", "why_it_matters": "Determines whether preservation can proceed through ordinary interfaces or needs a different recovery approach." } ], "affordances": [ "Identify the exact Communicator variant and select its applicable documentation.", "Evaluate telephone and interior productivity functions separately.", "Determine whether calling, messaging, synchronisation or file transfer is feasible with available infrastructure.", "Preserve accessible contacts, messages, documents and configuration through a compatible transfer route.", "Assess battery replacement, hinge repair and interface faults before choosing a repair action.", "Prepare a unit for offline demonstration, continued limited use or collection storage." ], "agent_conduct": { "may": [ "Describe the device family, its models and history from reliable sources.", "Help a collector or owner catalogue, store or exhibit a device they hold." ], "must_not": [ "Extract or publish personal data such as contacts and messages left on a second-hand device.", "Present a refurbished or modified unit as original in a sale.", "Connect an old device to networks in a way that exposes it or others to known security flaws.", "Charge or use a swollen or damaged battery." ], "requires_human": [ "Wiping or disposing of a device that may still hold someone's data." ] }, "ethics": { "considerations": [ "Old phones keep personal and business data long after they are retired.", "Electronic waste harms people and the environment when it is not recycled properly." ], "affected_parties": [ "Former owners whose data remains on the device", "Collectors and buyers", "Recycling workers" ] }, "owners": { "steward": "The person who owns the device; the network operator held any subscription linked to it.", "master_systems": [ "Device identity registries such as IMEI blocklists" ] }, "visual_identification": [ "A thick candy-bar phone with a small outer screen and keypad.", "Opens lengthwise like a clamshell to show a wide inner screen and a full keyboard." ], "failure_modes_and_hazards": [ "Aged lithium-ion batteries can swell, overheat or catch fire.", "Hinges and ribbon cables wear out with repeated opening.", "Outdated software lacks security updates." ], "standards_and_regulation": [ "GSM mobile communication standards, ETSI and 3GPP." ], "what_it_is_for": [ "These folding mobile devices were used for business communication, scheduling, contact management and document handling while travelling.", "They are now also encountered in historical technology collections, electronics repair and digital preservation work." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1995636: Nokia Communicator", "url": "https://www.wikidata.org/wiki/Q1995636", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Nokia Communicator", "url": "https://en.wikipedia.org/wiki/Nokia_Communicator", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "family-and-variant", "name": "Family and variant", "description": "Establishes which Communicator is being described and which evidence governs its capabilities.", "rationale": "The family spans variants whose specifications and compatibility must not be merged into a fictional universal device.", "layers": [ { "id": "communicator-membership", "name": "Communicator membership", "description": "Tests inclusion in the registered family.", "findings": [ { "id": "documented-family-identity", "name": "Documented family identity", "description": "Family identity requires evidence beyond a Nokia logo or folding keyboard form.", "questions": [ { "text": "Which attributable product record identifies this model as a Nokia Communicator?", "kind": "provenance", "id": "documented-family-identity-q01" }, { "text": "Which similarly named or similarly shaped Nokia devices fall outside this family boundary?", "kind": "boundary", "id": "documented-family-identity-q02" } ] } ] }, { "id": "variant-evidence", "name": "Variant evidence", "description": "Connects physical and software identifiers to the applicable product documentation.", "findings": [ { "id": "variant-specific-specification", "name": "Variant-specific specification", "description": "Capabilities must be attributed to the identified model and regional variant.", "questions": [ { "text": "What model designation and product code can be read from the unit or its original records?", "kind": "provenance", "id": "variant-specific-specification-q01" }, { "text": "Do the enclosure markings, firmware identity and regional keyboard layout agree?", "kind": "measurement", "id": "variant-specific-specification-q02" } ] } ] } ] }, { "id": "folding-workspace", "name": "Folding workspace", "description": "Models the exterior telephone interface and interior keyboard workspace as distinct but connected operating surfaces.", "rationale": "The Communicator's opening workspace creates identification, usability and mechanical assessment needs beyond those of a conventional handset.", "layers": [ { "id": "interface-behaviour", "name": "Interface behaviour", "description": "Establishes how exterior and interior interfaces expose functions and states.", "findings": [ { "id": "telephone-workspace-transition", "name": "Telephone-to-workspace transition", "description": "Opening, closing and switching interfaces must be assessed according to the particular model's behaviour.", "questions": [ { "text": "Which calling and organiser functions are accessible with this model closed and open?", "kind": "definition", "id": "telephone-workspace-transition-q01" }, { "text": "What happens to an active call or application when the enclosure is opened or closed?", "kind": "measurement", "id": "telephone-workspace-transition-q02" } ] } ] }, { "id": "keyboard-display-and-hinge", "name": "Keyboard, display and hinge", "description": "Assesses the components that make the interior workspace usable.", "findings": [ { "id": "interior-workspace-integrity", "name": "Interior workspace integrity", "description": "Keyboard response, display legibility and hinge behaviour jointly determine practical text-work capability.", "questions": [ { "text": "Which keys, display regions or controls fail during a repeatable text-entry and navigation check?", "kind": "measurement", "id": "interior-workspace-integrity-q01" }, { "text": "Does opening the hinge through its normal range cause image loss, intermittent input or mechanical resistance?", "kind": "measurement", "id": "interior-workspace-integrity-q02" } ] } ] } ] }, { "id": "software-and-personal-data", "name": "Software and personal data", "description": "Determines what the installed platform can run and how its organiser and document data can be preserved.", "rationale": "Communicator productivity depends on generation-specific software and data formats as much as on physical condition.", "layers": [ { "id": "platform-capabilities", "name": "Platform capabilities", "description": "Identifies the actual installed environment and application requirements.", "findings": [ { "id": "installed-platform-compatibility", "name": "Installed platform compatibility", "description": "Software compatibility follows the observed platform and version rather than the family name.", "questions": [ { "text": "Which operating system, interface platform and firmware version does this unit report?", "kind": "measurement", "id": "installed-platform-compatibility-q01" }, { "text": "Which application packages and document formats are explicitly supported by that environment?", "kind": "boundary", "id": "installed-platform-compatibility-q02" } ] } ] }, { "id": "preservation-and-recovery", "name": "Preservation and recovery", "description": "Establishes a workable route from stored personal information to a verified backup.", "findings": [ { "id": "recoverable-organiser-and-files", "name": "Recoverable organiser and files", "description": "Preservation needs an identified storage location, compatible transfer method and usable exported representation.", "questions": [ { "text": "Where are contacts, calendar entries, messages and documents stored on this model, and which are currently readable?", "kind": "measurement", "id": "recoverable-organiser-and-files-q01" }, { "text": "Which available transfer method can preserve these records, and how will the resulting backup be checked?", "kind": "action", "id": "recoverable-organiser-and-files-q02" }, { "text": "Which reset, update or repair operations could erase data before that backup is complete?", "kind": "action", "id": "recoverable-organiser-and-files-q03" } ] } ] } ] }, { "id": "communications-and-interoperability", "name": "Communications and interoperability", "description": "Separates built-in communications capabilities from usable networks, services and companion systems.", "rationale": "A functioning legacy Communicator may lack a compatible network or host environment even when its hardware operates correctly.", "layers": [ { "id": "cellular-service-fit", "name": "Cellular service fit", "description": "Tests the exact radio variant against a specified place, operator and date.", "findings": [ { "id": "radio-and-service-compatibility", "name": "Radio and service compatibility", "description": "Network usability depends on both device support and externally available service.", "questions": [ { "text": "Which cellular technologies and frequency bands are documented for this regional variant?", "kind": "provenance", "id": "radio-and-service-compatibility-q01" }, { "text": "At the intended location and assessment date, which operator services accept this radio technology and subscriber configuration?", "kind": "boundary", "id": "radio-and-service-compatibility-q02" } ] } ] }, { "id": "local-and-remote-data-paths", "name": "Local and remote data paths", "description": "Assesses accessory, host-software and protocol dependencies for exchanging information.", "findings": [ { "id": "usable-transfer-and-service-path", "name": "Usable transfer and service path", "description": "A listed interface or application does not by itself establish an end-to-end working connection.", "questions": [ { "text": "Which cable, wireless interface or removable medium is supported, and what compatible host software is available?", "kind": "action", "id": "usable-transfer-and-service-path-q01" }, { "text": "Which protocol, authentication or encryption requirements prevent the installed messaging or browser software from using a proposed service?", "kind": "boundary", "id": "usable-transfer-and-service-path-q02" } ] } ] } ] }, { "id": "power-repair-and-preservation", "name": "Power, repair and preservation", "description": "Supports safe energising, targeted fault assessment and preservation of an ageing Communicator.", "rationale": "Battery ageing, specialised parts and the folding assembly can determine whether a unit should be operated, repaired or stored.", "layers": [ { "id": "battery-and-charging", "name": "Battery and charging", "description": "Establishes compatible power components and their observed condition.", "findings": [ { "id": "power-up-readiness", "name": "Power-up readiness", "description": "Power-up requires model-correct electrical compatibility and an acceptable battery and connector condition.", "questions": [ { "text": "Which battery and charger designations, voltages and connection requirements are specified for this model?", "kind": "provenance", "id": "power-up-readiness-q01" }, { "text": "Do swelling, leakage, corrosion, damaged contacts or abnormal heating make a charging attempt inappropriate?", "kind": "action", "id": "power-up-readiness-q02" } ] } ] }, { "id": "repair-and-storage-decision", "name": "Repair and storage decision", "description": "Combines fault evidence, service information and intended use into a handling decision.", "findings": [ { "id": "evidence-based-intervention", "name": "Evidence-based intervention", "description": "An intervention should address a demonstrated fault and account for data, part compatibility and enclosure integrity.", "questions": [ { "text": "Which observed symptoms and model-specific service information support the proposed repair?", "kind": "provenance", "id": "evidence-based-intervention-q01" }, { "text": "Which replacement parts are demonstrably compatible with this variant's hinge, displays, keyboard or power assembly?", "kind": "boundary", "id": "evidence-based-intervention-q02" }, { "text": "Given data preservation needs and intended use, should the next action be repair, limited operation or battery-separated storage?", "kind": "action", "id": "evidence-based-intervention-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 name is interpreted as the product family because no narrower sense is recorded.", "Specifications must be attached to individual models: operating systems, network support, displays and connectivity changed substantially between generations.", "The mass range is approximate; exact weights, regional variants and model-specific regulatory approvals should be checked against original documentation." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Nokia Communicator 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": [ "Nokia 9000 Communicator", "Nokia 9110 Communicator", "Nokia 9210 Communicator", "Nokia 9500 Communicator", "Nokia E90 Communicator" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Nokia Communicator 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": "Nokia commercial model designation", "value_or_pattern": "9000, 9110, 9210, 9500, E90", "note": "Identifies product models within the family, rather than individual devices; this list is not exhaustive." }, { "scheme": "International Mobile Equipment Identity (IMEI)", "value_or_pattern": "15 decimal digits", "note": "Identifies an individual cellular device, not the Communicator family." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Nokia Communicator 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": [ "GSM cellular specifications, developed by ETSI and subsequently maintained within 3GPP; supported frequency bands depend on the model.", "IEEE 802.11 wireless LAN standards, issued by IEEE; applicable to Wi-Fi-equipped models such as the 9500 and E90." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Nokia Communicator 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": [ "Business voice calls and SMS messaging.", "Mobile email and text entry using a physical keyboard.", "Calendar, contact and task management.", "Viewing and editing documents using model-specific applications.", "Web browsing and data communication within the capabilities of the model and network." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Nokia Communicator 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": "Device mass with battery", "typical_range": "Approximately 210-400 across the family", "unit": "g" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Nokia Communicator 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": [ "Rechargeable battery ageing can reduce operating time or prevent startup.", "Damaged or deteriorated lithium-ion batteries can swell, overheat or ignite.", "Hinge wear or damage to interconnecting cables can impair the internal display or keyboard.", "Ageing software, certificates and supported protocols can prevent access to modern email and web services.", "Shutdown of compatible cellular networks can remove calling and mobile-data functionality." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Nokia Communicator 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": [ "Regional variants differ in supported cellular frequency bands.", "Keyboard layouts and software languages vary by market.", "Present-day usability depends on local availability of compatible cellular networks." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Nokia Communicator 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": "Nokia 9000 Communicator", "difference": "A specific model in the Communicator family; the registered name covers the family rather than only its first model." }, { "name": "Personal digital assistant", "difference": "A PDA provides handheld organiser or computing functions but does not necessarily include integrated cellular voice telephony." }, { "name": "Smartphone", "difference": "Smartphone is the broader device category; Nokia Communicator identifies a particular Nokia product family with a characteristic folding keyboard design." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Nokia Communicator this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which exact models and regional variants does the registry intend the Nokia Communicator family entry to include, and does an existing Vercy world model already own this concept?", "Which manufacturer manuals and service records establish each included variant's dimensions, radio bands, battery, charger and interface specifications?", "Which regulatory approvals and standards apply to each regional variant, and which markings or declarations substantiate them?", "Which hinge, display, keyboard and power faults are documented recurring failures rather than isolated reports?", "Which available host environments and export tools can preserve each generation's organiser and message data without material loss?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 31 } }