{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:20:44Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.5, "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: 01a09521-1018-7cb1-9452-c482924efb6b\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: hum\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 registered ", "usd": 0.0, "recall": true }, "codex": { "seconds": 78.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09521-100b-7d23-a652-5bf465f7ea5f\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: hum\nRegistry id: vr.tr.hum\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for this" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:52:10+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "revisions": [ { "at": "2026-10-07T11:28:53+00:00", "engine": "codex", "fields": [ "agent_conduct", "definition", "distinguishing_features", "ethics", "failure_modes_and_hazards", "in_scope", "out_of_scope", "owners", "purpose", "scope_statement", "visual_identification" ], "answering_review": "e3f34aed233906bb125756ee864e361f944eb02497fe652441086fe3fe65b0f0" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T12:16:32+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q2922301", "registryId": "vr.tr.hum", "name": "hum", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2922301/", "model": { "registry_id": "vr.tr.hum", "name": "hum", "purpose": "Enable an agent to recognise and describe a vocal hum and distinguish it from other vocal sounds and non-vocal acoustic humming.", "definition": "A hum is a voiced bilabial nasal sound produced with the lips closed, the vocal folds vibrating and airflow passing through the nose.", "scope_statement": "This model owns hum in the sense of a voiced bilabial nasal vocal sound, including its production, acoustic characteristics and evidence for identification.", "in_scope": [ "Bilabial closure, voicing and nasal airflow are in scope.", "Audible pitch, duration and resonance are in scope.", "Humming in musical and communicative contexts is in scope.", "Evidence and uncertainty in distinguishing vocal hums from other sounds are in scope." ], "out_of_scope": [ "Mechanical and electrical humming noises are outside this model.", "Vehicle telematics products named Hum are outside this model.", "Environmental noise complaints and source attribution are outside this model.", "Clinical diagnosis and treatment of voice or breathing disorders are outside this model." ], "distinguishing_features": [ "The sound combines vocal-fold vibration, closed lips and nasal airflow.", "A steady pitch alone does not establish a vocal hum because machines and other sources can produce similar sounds.", "Closed lips alone do not establish humming because visible posture does not confirm voicing or nasal airflow.", "A hum may sustain or vary its pitch and need not form a spoken word." ], "characteristics": [ { "name": "Identity evidence", "kind": "relation", "unit_or_values": "Registry source entity, manufacturer documentation and equipment label", "why_it_matters": "The undefined name cannot independently establish that the registered thing is Verizon Hum." }, { "name": "Variant and equipment configuration", "kind": "category", "unit_or_values": "Documented variant; OBD reader; speaker present or absent; other documented components", "why_it_matters": "Feature expectations and installation instructions depend on configuration." }, { "name": "Host vehicle compatibility", "kind": "state", "unit_or_values": "Confirmed compatible, confirmed incompatible, unverified", "why_it_matters": "An available OBD-II socket does not establish complete system compatibility." }, { "name": "Reader installation state", "kind": "state", "unit_or_values": "Disconnected, connected and unverified, communicating, faulted", "why_it_matters": "Separates physical attachment from successful vehicle communication." }, { "name": "Component power condition", "kind": "state", "unit_or_values": "Reader power status; speaker charge status where applicable; unknown", "why_it_matters": "A powered reader does not establish that an optional speaker is operational." }, { "name": "Observation age", "kind": "measurement", "unit_or_values": "Seconds since the recorded diagnostic or location observation", "why_it_matters": "Old observations must not be presented as the vehicle's current condition." }, { "name": "Diagnostic observation", "kind": "relation", "unit_or_values": "Vehicle identity, reported DTC, observation timestamp and originating reader", "why_it_matters": "Keeps each reported code attached to its actual vehicle and observation context." }, { "name": "Location uncertainty", "kind": "measurement", "unit_or_values": "Metres when supplied; otherwise unknown", "why_it_matters": "Prevents a displayed position from implying unsupported precision." }, { "name": "Capability availability", "kind": "state", "unit_or_values": "Per feature: verified available, unavailable, degraded, historical only, unknown", "why_it_matters": "Installed hardware and historical advertising do not establish present service availability." }, { "name": "Vehicle and account binding", "kind": "relation", "unit_or_values": "Installed reader to host vehicle to authorised service account", "why_it_matters": "Incorrect binding can misattribute diagnostics, journeys or location." } ], "affordances": [ "Identify the documented Hum configuration and its applicable instructions.", "Assess installation readiness against vehicle compatibility and physical fit.", "Inspect timestamped vehicle diagnostic observations and flag unresolved faults.", "Assess whether a location or communications feature is presently usable.", "Review authorised access to vehicle telemetry and location.", "Prepare a documented transfer, removal or retirement procedure." ], "agent_conduct": { "may": [ "Describe the vocal production and acoustic characteristics of a hum.", "Measure and report pitch, duration and level from authorized vocal recordings." ], "must_not": [ "Classify a sound as a vocal hum solely because it has a steady pitch.", "Infer a person's diagnosis, emotion or intent from humming alone.", "Record, identify or share a person's vocalizations without appropriate authorization.", "Produce a hum at levels or times that disturb others." ], "requires_human": [ "Clinical interpretation of unusual or difficult vocal production requires a qualified human professional.", "Decisions with significant consequences for a person based on vocal analysis require human review." ] }, "ethics": { "considerations": [ "Vocal recordings can reveal personal information and require privacy protection.", "Differences in vocal expression should not be used to stigmatize people or infer unsupported personal traits." ], "affected_parties": [ "People whose humming is recorded or analyzed are affected.", "Listeners and people nearby are affected." ] }, "owners": { "steward": "No one owns the sound category; authorized custodians are responsible for vocal recordings and associated data.", "master_systems": [] }, "visual_identification": [ "Closed lips may accompany humming, but appearance alone cannot confirm the sound.", "Identification requires acoustic evidence or other evidence of voicing and nasal airflow." ], "failure_modes_and_hazards": [ "Confusing vocal humming with mechanical noise can produce incorrect sound labels.", "Inferring health, emotion or intent from a hum alone can produce unsupported conclusions.", "Recording or identifying a person from vocal sounds without authorization can compromise privacy." ], "what_it_is_for": [ "A voiced bilabial nasal hum is encountered in wordless vocalization, musical practice and speech assessment.", "It can carry a melody or provide a sustained vocal sound for examining pitch, resonance and phonation." ], "standards_and_regulation": [ "The International Phonetic Alphabet, maintained by the International Phonetic Association, classifies the voiced bilabial nasal with the symbol [m]." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q2922301: hum", "url": "https://www.wikidata.org/wiki/Q2922301", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Humming", "url": "https://en.wikipedia.org/wiki/Humming", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "hum-identity-and-configuration", "name": "Hum identity and configuration", "description": "Establish the intended referent and the equipment configuration being assessed.", "rationale": "The registry supplies neither a definition nor a source identifier, and Hum capabilities differ by configuration.", "layers": [ { "id": "referent-resolution", "name": "Referent resolution", "description": "Keep the Verizon interpretation explicit and conditional.", "findings": [ { "id": "provisional-verizon-referent", "name": "Provisional Verizon referent", "description": "Manufacturer material documents a Hum vehicle system, making this a plausible device-domain interpretation; it does not establish the registry mapping. See [Hum equipment FAQ](https://www.hum.com/faq/hum-equipment/).", "questions": [ { "text": "Which original registry source entity establishes what vr.tr.hum denotes?", "kind": "provenance", "id": "provisional-verizon-referent-q01" }, { "text": "Does that source identify Verizon Hum rather than a sound, landform or another named product?", "kind": "boundary", "id": "provisional-verizon-referent-q02" } ] } ] }, { "id": "variant-equipment", "name": "Variant equipment", "description": "Record component and feature differences within the registered kind.", "findings": [ { "id": "documented-equipment-set", "name": "Documented equipment set", "description": "The configuration record should identify the reader and any speaker, using documentation applicable to that variant.", "questions": [ { "text": "Which Hum variant and hardware identifiers appear on the equipment?", "kind": "measurement", "id": "documented-equipment-set-q01" }, { "text": "Which components and capabilities does the matching manufacturer guide specify?", "kind": "provenance", "id": "documented-equipment-set-q02" } ] } ] } ] }, { "id": "vehicle-interface-and-power", "name": "Vehicle interface and power", "description": "Assess whether the system can be installed and powered in its particular host vehicle.", "rationale": "Hum depends on a vehicle interface and may include a separately charged speaker.", "layers": [ { "id": "obd-installation", "name": "OBD installation", "description": "Separate compatibility, physical fit and verified communication.", "findings": [ { "id": "compatible-host-connection", "name": "Compatible host connection", "description": "Hum installation material directs connection of its reader to the vehicle's OBD-II port with the vehicle turned off. Applicability must be checked against the variant and vehicle. See [Hum installation instructions](https://www.hum.com/setup-hum-x-old/).", "questions": [ { "text": "What evidence confirms compatibility with this vehicle's make, model and year?", "kind": "provenance", "id": "compatible-host-connection-q01" }, { "text": "Can the reader fit securely without obstructing pedals, trim or driver movement?", "kind": "boundary", "id": "compatible-host-connection-q02" } ] } ] }, { "id": "power-and-startup", "name": "Power and startup", "description": "Assess reader operation and any speaker's separate readiness.", "findings": [ { "id": "component-readiness", "name": "Component readiness", "description": "Record reader startup separately from speaker charging and pairing; Hum installation instructions explicitly call for charging the HumX speaker before mounting it.", "questions": [ { "text": "What indicators or observations verify reader startup and vehicle communication?", "kind": "measurement", "id": "component-readiness-q01" }, { "text": "If a speaker is fitted, is it charged and connected according to its guide?", "kind": "measurement", "id": "component-readiness-q02" } ] } ] } ] }, { "id": "vehicle-diagnostic-evidence", "name": "Vehicle diagnostic evidence", "description": "Represent the vehicle information Hum reports without overstating its diagnostic reach.", "rationale": "A reported trouble code is evidence for investigation, not a complete diagnosis or proof of roadworthiness.", "layers": [ { "id": "diagnostic-observations", "name": "Diagnostic observations", "description": "Bind reported vehicle faults to their origin and time.", "findings": [ { "id": "reported-trouble-codes", "name": "Reported trouble codes", "description": "Hum describes receiving diagnostic information from the vehicle's OBD system and reporting diagnostic trouble codes. See [Hum vehicle diagnostics](https://www.hum.com/features/vehicle-diagnostics/).", "questions": [ { "text": "Which code was reported, for which vehicle, and at what observation time?", "kind": "measurement", "id": "reported-trouble-codes-q01" }, { "text": "Is the accompanying explanation vehicle-specific, a general code description or a separately confirmed diagnosis?", "kind": "boundary", "id": "reported-trouble-codes-q02" } ] } ] }, { "id": "diagnostic-limits", "name": "Diagnostic limits", "description": "Distinguish missing information from an observed absence of faults.", "findings": [ { "id": "silence-is-not-clearance", "name": "Missing reports do not establish vehicle health", "description": "The model must retain observation freshness and communication status before interpreting a screen with no reported faults.", "questions": [ { "text": "When did the reader last successfully obtain and transmit vehicle information?", "kind": "measurement", "id": "silence-is-not-clearance-q01" }, { "text": "What further inspection is needed before a repair or continued-use decision?", "kind": "action", "id": "silence-is-not-clearance-q02" } ] } ] } ] }, { "id": "connected-features-and-service", "name": "Connected features and service", "description": "Evaluate location, assistance and optional communications as dependent capabilities.", "rationale": "A physically intact Hum unit may lack a functioning network, account entitlement or supporting service.", "layers": [ { "id": "location-and-connectivity", "name": "Location and connectivity", "description": "Separate vehicle observations from delivery through the supporting network.", "findings": [ { "id": "freshness-and-network-dependencies", "name": "Freshness and network dependencies", "description": "Hum product material identifies GPS and network availability as dependencies for many services; the model should record each capability's actual status. See [Verizon Hum+ product information](https://www.verizon.com/business/shop/products/devices/connected-devices/hum-plus-gen-2).", "questions": [ { "text": "What are the timestamp, origin and available accuracy information for the displayed vehicle location?", "kind": "measurement", "id": "freshness-and-network-dependencies-q01" }, { "text": "Which required network and service dependencies are currently verified?", "kind": "measurement", "id": "freshness-and-network-dependencies-q02" } ] } ] }, { "id": "assistance-and-optional-features", "name": "Assistance and optional features", "description": "Represent documented features without treating them as universally present or currently operational.", "findings": [ { "id": "feature-specific-readiness", "name": "Feature-specific readiness", "description": "Assistance calling, incident-related functions and hotspot access require separate applicability and availability checks; historical product descriptions alone are insufficient.", "questions": [ { "text": "Which assistance and hotspot features belong to this variant and service agreement?", "kind": "definition", "id": "feature-specific-readiness-q01" }, { "text": "What current provider evidence confirms each feature remains supported?", "kind": "provenance", "id": "feature-specific-readiness-q02" }, { "text": "How can readiness be checked without initiating an unnecessary emergency request?", "kind": "action", "id": "feature-specific-readiness-q03" } ] } ] } ] }, { "id": "telemetry-access-and-retirement", "name": "Telemetry access and retirement", "description": "Manage account binding, location access and the end of an installation's useful service.", "rationale": "Hum associates vehicle information with accounts, and removal of hardware may not resolve account access or retained records.", "layers": [ { "id": "vehicle-data-access", "name": "Vehicle data access", "description": "Identify who may view telemetry for the attached vehicle.", "findings": [ { "id": "authorised-telemetry-binding", "name": "Authorised telemetry binding", "description": "Hum's privacy policy addresses vehicle information, location and connected services; the model should record the applicable policy and actual access configuration. See [Verizon Hum privacy policy](https://www.verizon.com/about/privacy/hum-privacy-policy).", "questions": [ { "text": "Which account and authorised users can access this vehicle's location and driving information?", "kind": "relation", "id": "authorised-telemetry-binding-q01" }, { "text": "What permissions and connected accounts must be reviewed before a vehicle or device transfer?", "kind": "action", "id": "authorised-telemetry-binding-q02" } ] } ] }, { "id": "service-end-and-removal", "name": "Service end and removal", "description": "Distinguish hardware condition from continued service support.", "findings": [ { "id": "retirement-disposition", "name": "Retirement disposition", "description": "Retirement assessment should cover provider support, vehicle removal, account unlinking and data disposition as separate unresolved checks where evidence is absent.", "questions": [ { "text": "What dated provider notice establishes the current service or retirement status?", "kind": "provenance", "id": "retirement-disposition-q01" }, { "text": "Which documented steps remove the equipment and resolve its account and vehicle associations?", "kind": "action", "id": "retirement-disposition-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "No sense is recorded; this answer provisionally describes the ordinary acoustic meaning.", "The PHY.OBJ classification and device-oriented batch context do not establish that a sound is intended; the registry's originating record should be checked before adopting this interpretation.", "The listed frequencies apply specifically to mains-related hum, not to hum in general." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of hum 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": [ "Vocal hum", "Mechanical hum", "Electrical mains hum" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of hum 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": [ "Humming melodies", "Using changes in equipment hum as clues to operating condition", "Identifying unwanted mains-related interference in audio systems" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of hum 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": "Mains-related hum frequency", "typical_range": "Common components at 50 or 60 Hz and their harmonics, including 100 or 120 Hz", "unit": "Hz" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of hum 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": [ "Unwanted hum can interfere with audio recording and reproduction.", "Mechanical hum can accompany vibration, looseness or resonance, but does not by itself establish a fault." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of hum 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": [ "Mains-related hum frequencies depend on whether the local electricity supply operates at 50 or 60 Hz." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of hum 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": "Buzz", "difference": "A buzz generally has a rougher timbre with more prominent higher harmonics; ordinary usage overlaps." }, { "name": "Humming", "difference": "Humming names the activity of producing a vocal hum; hum can name the resulting sound or a non-vocal sound." }, { "name": "The Hum", "difference": "The Hum refers to reports of persistent low-frequency sound with an uncertain or disputed source, rather than any ordinary humming sound." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of hum this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry's original source identify Hum by Verizon, or does vr.tr.hum denote another thing?", "Does an existing Vercy world model already cover this exact concept and require linking instead of a new publication?", "Which Hum generations and variants belong within this entry, and what equipment and capabilities distinguish them?", "What is the current provider-confirmed service status, including any discontinuation dates and residual functionality?", "Which variant-specific documents establish vehicle exclusions, electrical limits, certifications, removal procedures and data-retention rules?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 28 } }