{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:40:19Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.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: 01a09569-a5b2-76c1-b2b0-1c33fa287fdd\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Nokia 8910\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 regi", "usd": 0.0, "recall": true }, "codex": { "seconds": 95.6, "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: 01a09569-a5b8-7592-b764-ccf1a3fd6c51\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Nokia 8910\nRegistry id: vr.tr.nokia-8910\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:51:00+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:26+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1749694", "registryId": "vr.tr.nokia-8910", "name": "Nokia 8910", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1749694/", "model": { "registry_id": "vr.tr.nokia-8910", "name": "Nokia 8910", "purpose": "Enable an agent to recognise the Nokia 8910 product model, assess an associated handset's condition and compatibility, and choose supported operation, preservation or repair actions.", "definition": "The Nokia 8910 is a premium dual-band GSM mobile telephone model introduced by Nokia in 2002, distinguished by a titanium casing, a sliding mechanism that exposes the keypad, and a monochrome display.", "scope_statement": "This model owns the Nokia 8910-specific recognition criteria, capabilities, physical mechanisms and assessment requirements for registry entry vr.tr.nokia-8910 in PHY / PHY.OBJ; individual handsets supply observations against these requirements.", "in_scope": [ "Product identity and differentiation from Nokia 8910i and other Nokia sliding phones", "Titanium casing, upward opening mechanism, keypad and display", "Cellular, Bluetooth, infrared and legacy computer connectivity", "Battery, charging compatibility and operational condition", "Firmware-dependent controls, stored information and restoration requirements" ], "out_of_scope": [ "The general mobile telephone operating model", "Nokia corporate history and its wider product portfolio", "Nokia 8910i and other separately identified phone models", "Subscriber accounts, SIM ownership and telecommunications network operation", "Individual handset ownership, sale price and collection provenance", "Battery chemistry and charger design beyond compatibility with this handset" ], "distinguishing_features": [ "Require agreement between handset identification markings and software identity for Nokia 8910; an exterior shell or seller title alone is insufficient.", "Check the upward opening body that exposes chrome-finished keys together with the titanium outer casing. These are documented design features, but are not independently conclusive identity tests. [Nokia announcement](https://www.globenewswire.com/news-release/2002/02/19/1845731/0/en/The-Nokia-8910-epitomises-elegant-sophistication.html)", "Check for the documented greyscale display with white backlighting; a colour-display handset requires investigation for 8910i identity or replacement parts. [Nokia announcement](https://www.globenewswire.com/news-release/2002/02/19/1845731/0/en/The-Nokia-8910-epitomises-elegant-sophistication.html)", "Cross-check the documented combination of EGSM 900/GSM 1800, GPRS, Bluetooth and infrared against the identified hardware and firmware. [Nokia announcement](https://www.globenewswire.com/news-release/2002/02/19/1845731/0/en/The-Nokia-8910-epitomises-elegant-sophistication.html)" ], "characteristics": [ { "name": "Product identity evidence", "kind": "relation", "unit_or_values": "Manufacturer model marking, hardware type, product code and firmware identification linked to their evidence", "why_it_matters": "Prevents an 8910i, replacement shell or mixed assembly being accepted solely by appearance." }, { "name": "Opening mechanism condition", "kind": "state", "unit_or_values": "Closed and retained; releases and opens; partial travel; jammed; fails to retain; untested", "why_it_matters": "Determines keypad access and whether further movement could damage the mechanism." }, { "name": "Housing originality", "kind": "category", "unit_or_values": "Documented original; documented service replacement; aftermarket; mixed; unresolved", "why_it_matters": "Separates product design characteristics from the materials and finish actually present." }, { "name": "Display and keypad condition", "kind": "state", "unit_or_values": "Display legibility, backlight operation and individual key responses recorded separately", "why_it_matters": "Establishes whether menus, prompts and telephone functions can be controlled reliably." }, { "name": "Cellular service readiness", "kind": "state", "unit_or_values": "Untested; SIM rejected; searching; registered; voice verified; SMS verified; packet data verified, with operator, place and date", "why_it_matters": "Separates hardware capability from service availability and subscription configuration." }, { "name": "Local connection compatibility", "kind": "relation", "unit_or_values": "Bluetooth or infrared linked to peer device, software, requested function and observed result", "why_it_matters": "A successful connection does not establish support for every transfer or accessory function." }, { "name": "Installed battery and charger", "kind": "relation", "unit_or_values": "Battery designation, charger designation, label ratings and supporting compatibility document", "why_it_matters": "Supports a compatibility decision without assuming that a fitting connector establishes suitability." }, { "name": "Measured operating endurance", "kind": "measurement", "unit_or_values": "Hours, with battery identity, charge procedure, signal conditions and workload", "why_it_matters": "Separates present battery performance from historical advertised endurance." }, { "name": "Information storage location", "kind": "category", "unit_or_values": "Handset; SIM; connected computer; multiple locations; unknown", "why_it_matters": "Guides preservation and deletion without confusing handset memory with removable subscriber storage." } ], "affordances": [ "Identify a candidate handset and document unresolved conflicts between shell, labels and software.", "Assess opening, display, keypad and audio operation before selecting further tests.", "Determine whether voice, SMS or legacy data operation is feasible with a specified network and SIM.", "Test a specific Bluetooth or infrared accessory or computer workflow.", "Preserve authorised contacts and other supported records before reset or repair.", "Select documented battery, charging and repair actions while recording replacement parts." ], "agent_conduct": { "may": [ "Identify this titanium-cased slider model from its label, casing and keypad mechanism.", "Report a handset's cosmetic and mechanical condition, including slide action and casing wear, for a collector or owner." ], "must_not": [ "Present a re-housed or replica casing as an original titanium shell.", "Read or copy the messages and contacts on a collector's handset without the owner's consent.", "Alter its IMEI or serial label to make a handset appear rarer or cleaner than it is.", "Promise that it will work on networks where second-generation service has ended." ], "requires_human": [ "Selling or valuing a handset where originality of casing or parts is disputed.", "Replacing or charging an original aged battery in a collectible handset." ] }, "ethics": { "considerations": [ "As a luxury collectible, it attracts fakes that defraud buyers.", "Old handsets may still carry personal data of a former owner." ], "affected_parties": [ "Owners and collectors", "Buyers of used handsets", "Former users whose data remains" ] }, "owners": { "steward": "The person who owns the handset; the network operator holds any subscription record.", "master_systems": [ "IMEI blocklists" ] }, "visual_identification": [ "A compact titanium-coloured metal body with a slide that reveals the keypad.", "A small monochrome display on the front face.", "Model and IMEI on a label under the battery; mismatched labels suggest a re-housed unit." ], "failure_modes_and_hazards": [ "Calls fail on networks that no longer offer second-generation service.", "Aged lithium-ion batteries can swell inside the metal casing and distort it.", "Counterfeit casings or parts reduce value and mislead buyers." ], "standards_and_regulation": [ "GSM technical specifications, maintained by 3GPP, which define the network the handset was built for.", "Directive 2012/19/EU on waste electrical and electronic equipment (WEEE), European Union, which governs disposal of old handsets." ], "what_it_is_for": [ "This early mobile handset was designed for voice calls and text messaging on compatible second-generation cellular networks.", "It is now encountered in collections, electronics repair and preservation work, where battery condition and local network availability affect usability." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1749694: Nokia 8910", "url": "https://www.wikidata.org/wiki/Q1749694", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Nokia 8910", "url": "https://en.wikipedia.org/wiki/Nokia_8910", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "identity-and-model-boundary", "name": "Identity and model boundary", "description": "Establish what qualifies as a Nokia 8910 and how conflicting identification evidence is handled.", "rationale": "Similar Nokia designs and replacement assemblies make appearance alone an unreliable basis for model attribution.", "layers": [ { "id": "manufacturer-identification", "name": "Manufacturer identification", "description": "Connect the registered model to manufacturer markings and software identifiers.", "findings": [ { "id": "consistent-8910-identity", "name": "Consistent 8910 identity", "description": "Require traceable agreement between the claimed model and available hardware and software evidence.", "questions": [ { "text": "Which manufacturer type codes, product codes and firmware identifiers establish Nokia 8910 identity?", "kind": "definition", "id": "consistent-8910-identity-q01" }, { "text": "Which label photographs, software readings and manufacturer documents support the candidate handset's identification?", "kind": "provenance", "id": "consistent-8910-identity-q02" } ] } ] }, { "id": "neighbouring-models-and-replacements", "name": "Neighbouring models and replacements", "description": "Separate original model identity from similar products and later component substitutions.", "findings": [ { "id": "8910-versus-8910i", "name": "8910 versus 8910i", "description": "Define discriminators and classify mixed assemblies without creating a new registry thing for every repair.", "questions": [ { "text": "Which documented display, firmware and hardware differences reliably separate the 8910 from the 8910i?", "kind": "boundary", "id": "8910-versus-8910i-q01" }, { "text": "When casing, display and mainboard evidence disagree, what identity should be retained and what uncertainty recorded?", "kind": "action", "id": "8910-versus-8910i-q02" } ] } ] } ] }, { "id": "opening-body-and-controls", "name": "Opening body and controls", "description": "Assess the characteristic casing and opening assembly alongside the exposed user interface.", "rationale": "The moving body affects recognition, access and handling, so cosmetic grading cannot substitute for functional assessment.", "layers": [ { "id": "casing-and-opening-mechanism", "name": "Casing and opening mechanism", "description": "Record material evidence, release behaviour, travel and retention.", "findings": [ { "id": "controlled-opening-and-retention", "name": "Controlled opening and retention", "description": "Distinguish surface wear from faults affecting opening or secure closure.", "questions": [ { "text": "Does the release mechanism complete its intended travel and retain the handset correctly when closed?", "kind": "measurement", "id": "controlled-opening-and-retention-q01" }, { "text": "Which inspection or service procedure applies if travel is obstructed or the body fails to remain closed?", "kind": "action", "id": "controlled-opening-and-retention-q02" }, { "text": "What evidence establishes whether the installed outer casing matches the documented material and finish?", "kind": "provenance", "id": "controlled-opening-and-retention-q03" } ] } ] }, { "id": "display-keypad-and-call-controls", "name": "Display, keypad and call controls", "description": "Assess visible prompts, physical input and the interaction between opening position and telephone controls.", "findings": [ { "id": "usable-handset-interface", "name": "Usable handset interface", "description": "Record control behaviour independently from cosmetic appearance and network availability.", "questions": [ { "text": "Are display segments, backlighting, navigation keys and number keys usable throughout the intended opening positions?", "kind": "measurement", "id": "usable-handset-interface-q01" }, { "text": "How do opening, closing and keypad locking affect answering, ending calls and accidental input on the installed firmware?", "kind": "definition", "id": "usable-handset-interface-q02" } ] } ] } ] }, { "id": "cellular-and-local-connectivity", "name": "Cellular and local connectivity", "description": "Separate radio capability, available services and demonstrated peer compatibility.", "rationale": "The 8910's legacy cellular and local interfaces require explicit compatibility evidence before an agent promises a working communication path.", "layers": [ { "id": "gsm-service-dependencies", "name": "GSM service dependencies", "description": "Assess voice, SMS and data availability against the actual operator and subscriber configuration.", "findings": [ { "id": "service-specific-readiness", "name": "Service-specific readiness", "description": "Treat registration, calls, messages and data as distinct results rather than one working-phone flag.", "questions": [ { "text": "At the intended place and date, does an operator provide compatible service and accept the installed SIM and handset?", "kind": "boundary", "id": "service-specific-readiness-q01" }, { "text": "Which of registration, outgoing and incoming calls, SMS and GPRS have been demonstrated under recorded conditions?", "kind": "measurement", "id": "service-specific-readiness-q02" }, { "text": "Which observations distinguish unavailable service or incorrect settings from a suspected handset radio fault?", "kind": "action", "id": "service-specific-readiness-q03" } ] } ] }, { "id": "bluetooth-infrared-and-pc", "name": "Bluetooth, infrared and PC", "description": "Qualify individual accessory, transfer and modem workflows.", "findings": [ { "id": "verified-peer-workflow", "name": "Verified peer workflow", "description": "The guide describes Bluetooth and infrared computer connections, including modem use; compatibility must be established for each intended workflow. [Nokia user guide](https://www.manualslib.com/manual/112239/Nokia-8910.html)", "questions": [ { "text": "Which Bluetooth functions and infrared modes are documented for the identified 8910 firmware and intended peer?", "kind": "definition", "id": "verified-peer-workflow-q01" }, { "text": "Which peer hardware, operating system, Nokia software version and settings produced a successful transfer, audio or modem test?", "kind": "measurement", "id": "verified-peer-workflow-q02" }, { "text": "What pairing or connection authorisation must be established before the intended operation?", "kind": "action", "id": "verified-peer-workflow-q03" } ] } ] } ] }, { "id": "power-and-serviceability", "name": "Power and serviceability", "description": "Establish appropriate power accessories and evidence-based repair choices for an ageing 8910.", "rationale": "An intact premium casing does not establish battery condition, charging suitability or internal serviceability.", "layers": [ { "id": "battery-and-charging", "name": "Battery and charging", "description": "Connect installed accessories to documented compatibility and observed charging behaviour.", "findings": [ { "id": "supported-power-configuration", "name": "Supported power configuration", "description": "The guide gives a BLB-2 battery and ACP-8 charger example; establish the full applicable accessory list before generalising compatibility. [Nokia user guide](https://www.manualslib.com/manual/112239/Nokia-8910.html)", "questions": [ { "text": "Which battery and charger combinations are approved in the applicable Nokia documentation, and what is actually installed?", "kind": "provenance", "id": "supported-power-configuration-q01" }, { "text": "What battery condition, charging behaviour and measured endurance support continued use or replacement?", "kind": "measurement", "id": "supported-power-configuration-q02" } ] } ] }, { "id": "fault-isolation-and-repair", "name": "Fault isolation and repair", "description": "Use model-specific service evidence to distinguish replaceable faults from unsupported intervention.", "findings": [ { "id": "documented-repair-path", "name": "Documented repair path", "description": "Record symptoms, relevant assembly, service procedure and replacement provenance without assuming that reported ageing faults are universal.", "questions": [ { "text": "Which 8910 service documents specify diagnostic steps, tools and replacement parts for the observed fault?", "kind": "provenance", "id": "documented-repair-path-q01" }, { "text": "What checks after repair establish that opening, charging, controls, audio and applicable radio functions remain operational?", "kind": "action", "id": "documented-repair-path-q02" } ] } ] } ] }, { "id": "firmware-and-information-preservation", "name": "Firmware and information preservation", "description": "Assess software behaviour and preserve or remove stored information through supported operations.", "rationale": "Legacy firmware, SIM storage and computer tools create dependencies that must be resolved before resetting or restoring an 8910.", "layers": [ { "id": "firmware-and-access-state", "name": "Firmware and access state", "description": "Record software identity and distinguish different causes of restricted operation.", "findings": [ { "id": "interpreted-access-prompts", "name": "Interpreted access prompts", "description": "Treat keypad lock, SIM access prompts and handset security restrictions as separate states.", "questions": [ { "text": "Which firmware and language variant is installed, and which documented menu behaviour applies to it?", "kind": "provenance", "id": "interpreted-access-prompts-q01" }, { "text": "Does the observed prompt concern keypad locking, SIM credentials, handset security or another restriction, and what authorised recovery path applies?", "kind": "action", "id": "interpreted-access-prompts-q02" } ] } ] }, { "id": "records-backup-and-reset", "name": "Records, backup and reset", "description": "Determine where records reside and verify the effects of copying, synchronisation and reset.", "findings": [ { "id": "verified-preservation-or-removal", "name": "Verified preservation or removal", "description": "Define a preservation or deletion outcome for each supported record type and storage location.", "questions": [ { "text": "Which contacts, messages, calendar entries and recordings reside on the handset, SIM or connected computer?", "kind": "boundary", "id": "verified-preservation-or-removal-q01" }, { "text": "Which supported transfer procedure preserves the required fields, and how is the resulting copy verified?", "kind": "action", "id": "verified-preservation-or-removal-q02" }, { "text": "What does the documented factory-settings operation retain, and which additional operations are needed for the requested deletion outcome?", "kind": "action", "id": "verified-preservation-or-removal-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 is recall-based information; no sources were consulted.", "Check exact dimensions, mass, battery specification, Bluetooth version, and regional hardware identifiers against original Nokia documentation.", "The frequency figures are nominal band designations, not exact transmit and receive frequency limits." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Nokia 8910 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": "8910", "note": "Identifies the product model, not an individual handset." }, { "scheme": "International Mobile Equipment Identity (IMEI)", "value_or_pattern": "15 decimal digits", "note": "Identifies an individual handset; there is no single IMEI for the model." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Nokia 8910 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 specifications maintained by ETSI and 3GPP for cellular communication.", "Bluetooth specifications administered by the Bluetooth Special Interest Group (Bluetooth SIG)." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Nokia 8910 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": [ "Mobile voice calls on compatible GSM networks.", "Sending and receiving SMS text messages.", "Short-range connectivity through Bluetooth and infrared.", "Collecting and restoring early premium mobile phones." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Nokia 8910 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": "Supported GSM frequency bands", "typical_range": "900 and 1800", "unit": "MHz" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Nokia 8910 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": [ "Ageing rechargeable batteries can lose capacity, swell, or leak.", "Wear or damage to the sliding mechanism can impair opening and keypad access.", "Liquid ingress and corrosion can damage contacts and electronics.", "Withdrawal of compatible GSM service can prevent cellular use despite functioning hardware." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Nokia 8910 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 operation depends on local support for GSM 900 or GSM 1800 and continued availability of compatible service." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Nokia 8910 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 8910i", "difference": "A later, distinct model with a colour display; the original 8910 has a monochrome display." }, { "name": "GSM mobile telephone", "difference": "The broader device category; Nokia 8910 identifies one specific product model within it." }, { "name": "Individual Nokia 8910 handset", "difference": "A physical unit has its own IMEI, condition, and ownership history; this entry describes the model." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Nokia 8910 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which manufacturer hardware types, regional product codes and firmware revisions belong to the original Nokia 8910, and how can mixed 8910/8910i assemblies be identified?", "What are the authoritative dimensions, mass measurement conditions, battery ratings and complete approved charger list for each relevant variant?", "Which Bluetooth profiles, infrared modes and Nokia PC Suite versions support each intended workflow, and which combinations remain practically usable?", "Which Nokia service procedures establish opening-mechanism tolerances, verified failure modes and acceptable replacement-part substitutions?", "Which model-specific declarations, certification identifiers and exposure measurements apply, with their issuing bodies, jurisdictions and documented test conditions?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 32 } }