{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:43:13Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.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: 01a094fe-bd43-7ad3-81b8-ef1c15e85bb2\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: field telephone\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", "usd": 0.0, "recall": true }, "codex": { "seconds": 76.0, "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: 01a094fe-bd52-7b12-aa1e-c42cef002497\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: field telephone\nRegistry id: vr.tr.field-telephone\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:54:37+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "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-Q202821", "registryId": "vr.tr.field-telephone", "name": "field telephone", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q202821/", "model": { "registry_id": "vr.tr.field-telephone", "name": "field telephone", "purpose": "Enable an agent to recognise a field telephone, assess its readiness for temporary wired voice communication, and determine compatible connections, operation and maintenance.", "definition": "A field telephone is a portable, rugged telephone designed for voice communication over temporarily deployed wire circuits, especially in military operations.", "scope_statement": "This model owns the field telephone as a kind of portable, rugged telephone endpoint for field-deployed wired voice communication, including the attributes needed to assess particular designs and units without treating a product model or deployed network as the kind itself.", "in_scope": [ "Field-use construction, portability and identification as a wired voice endpoint", "Speech circuitry, handset behaviour and supported telephone operating modes", "Power arrangements, call signalling and operator controls", "Line interfaces, compatibility and conditional communication performance", "Readiness checks, fault isolation, maintenance and electrical exposure" ], "out_of_scope": [ "Radio transceivers and their wireless communication links", "Field switchboards and network-wide routing or subscriber management", "Cable manufacture, cable inventories and complete field-line infrastructure", "Permanent public telephone exchange infrastructure", "Product-line catalogues and individual-unit service histories as independent models" ], "distinguishing_features": [ "Provides two-way voice communication through a wired telephone circuit; a portable radio instead carries its communication over a radio link.", "Is designed for transport and temporary field deployment, rather than being classified as a field telephone merely because an ordinary desk telephone is used outdoors.", "Functions as a subscriber endpoint; a field switchboard primarily interconnects subscriber circuits.", "Has a telephone line interface and call-handling functions beyond those of a passive handset accessory.", "Must be identified through its supported circuit and signalling arrangements; a crank, battery compartment or military appearance alone is insufficient." ], "characteristics": [ { "name": "Supported circuit modes", "kind": "category", "unit_or_values": "Documented modes, such as local-battery or common-battery operation; unknown", "why_it_matters": "Determines which power and circuit arrangements can support speech and signalling." }, { "name": "Line interface", "kind": "category", "unit_or_values": "Terminal or connector type, conductor arrangement and documented electrical interface", "why_it_matters": "Physical attachment does not establish electrical compatibility." }, { "name": "Call signalling method", "kind": "category", "unit_or_values": "Magneto, battery-powered electronic or other documented method; unknown", "why_it_matters": "Determines whether another endpoint or switchboard can recognise an outgoing call." }, { "name": "Speech and signalling power sources", "kind": "category", "unit_or_values": "Separate records for battery, line supply, hand generator or other documented source", "why_it_matters": "Successful ringing does not by itself prove that the speech circuit has suitable power." }, { "name": "Required supply", "kind": "measurement", "unit_or_values": "V DC, polarity and permitted range by powered circuit; not applicable where documented", "why_it_matters": "Supports correct battery selection and prevents unsupported power connections." }, { "name": "Permitted line conditions", "kind": "measurement", "unit_or_values": "Documented loop resistance in Ω, insulation resistance in MΩ and attenuation in dB at stated test conditions", "why_it_matters": "Provides a defensible basis for evaluating a proposed line rather than assuming a universal range." }, { "name": "Compatible counterpart", "kind": "relation", "unit_or_values": "Endpoint, switchboard port or adapter with supporting interface evidence", "why_it_matters": "Compatibility depends on both ends of the connection." }, { "name": "Functional readiness", "kind": "state", "unit_or_values": "Untested, ready for a specified configuration, degraded or unserviceable", "why_it_matters": "Readiness must reflect separate speech, signalling and power checks." }, { "name": "Environmental protection", "kind": "category", "unit_or_values": "Documented ingress or environmental test designation with issuing body and applicable configuration; unknown", "why_it_matters": "Rugged appearance alone does not establish suitability for rain, dust or immersion." }, { "name": "Carried mass", "kind": "measurement", "unit_or_values": "kg, stating whether batteries, handset, case and accessories are included", "why_it_matters": "Supports deployment planning and distinguishes bare-unit specifications from carried equipment." } ], "affordances": [ "Identify the supported speech, power and signalling configuration from markings and documentation.", "Determine whether a proposed telephone, switchboard port and line are compatible.", "Prepare a unit for use by fitting approved power sources and setting documented controls.", "Connect and test an authorised field circuit after checking its electrical conditions.", "Place, receive and terminate a call using the unit's documented procedure.", "Isolate telephone, power or line faults and select permitted maintenance or withdrawal from service." ], "agent_conduct": { "may": [ "Describe field telephones and their history in military and emergency use.", "Catalogue and restore field telephones in museum and collector holdings.", "Set up and test field lines for training or events on the organizer's instructions." ], "must_not": [ "Tap or listen to field lines without authorization.", "Run wires across roads or paths where people can trip or vehicles snag them.", "Present a field telephone as secure communication when it is not.", "Connect old equipment to public phone networks in ways that interfere with them." ], "requires_human": [ "Use of field telephones in real emergencies or military operations." ] }, "ethics": { "considerations": [ "Wired communication in conflict can save or cost lives; misuse can expose people.", "Historic equipment is part of military and communication heritage." ], "affected_parties": [ "Operators", "People near laid wires", "Collectors and museums" ] }, "owners": { "steward": "The unit, organization or collector that holds it.", "master_systems": [] }, "visual_identification": [ "A rugged handset telephone in a leather, wooden or plastic case with a crank or buzzer.", "Connected by twin wire unrolled from a reel." ], "failure_modes_and_hazards": [ "Laid wires create trip hazards and can be damaged by vehicles.", "Unsecured lines can be tapped." ], "what_it_is_for": [ "Field telephones provide temporary wired voice communication in military positions, training areas and other field installations.", "They connect personnel through deployed wire circuits, either directly or through compatible switching equipment.", "Their suitability depends on circuit compatibility, available power and environmental conditions." ], "standards_and_regulation": [ "MIL-STD-810, issued by the United States Department of Defense, provides environmental engineering and laboratory test methods for field telephones when required by the applicable procurement specification.", "MIL-STD-461, issued by the United States Department of Defense, specifies electromagnetic interference requirements for equipment including field telephones when invoked by the applicable procurement specification." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q202821: field telephone", "url": "https://www.wikidata.org/wiki/Q202821", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Field telephone", "url": "https://en.wikipedia.org/wiki/Field_telephone", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "field-endpoint-identity", "name": "Field endpoint identity", "description": "Establishes what makes the thing a field telephone and which design information governs its use.", "rationale": "Field telephones can resemble radios, desk telephones, intercoms or loose handset assemblies, while differing electrically between designs.", "layers": [ { "id": "kind-and-boundary", "name": "Kind and boundary", "description": "Separates the wired field telephone endpoint from neighbouring communication equipment.", "findings": [ { "id": "wired-field-role", "name": "Wired field role", "description": "Recognition requires evidence of a wired voice endpoint intended for field deployment; appearance and current location are insufficient.", "questions": [ { "text": "What documented purpose and interface identify this equipment as a field telephone?", "kind": "definition", "id": "wired-field-role-q01" }, { "text": "Is the item a complete telephone endpoint, a handset accessory, a radio or a switching device?", "kind": "boundary", "id": "wired-field-role-q02" } ] } ] }, { "id": "design-identification", "name": "Design identification", "description": "Connects observable markings and fitted components to applicable operating information.", "findings": [ { "id": "configuration-evidence", "name": "Configuration evidence", "description": "Design designation, revision and fitted handset or accessories determine which instructions can safely be applied.", "questions": [ { "text": "Which markings and component identifiers establish the design and configuration?", "kind": "provenance", "id": "configuration-evidence-q01" }, { "text": "Which manual or technical record applies to this configuration, including modifications?", "kind": "provenance", "id": "configuration-evidence-q02" } ] } ] } ] }, { "id": "speech-and-power", "name": "Speech and power", "description": "Describes the voice path and the supplies needed for its supported operating modes.", "rationale": "A field telephone's speech circuit and calling mechanism can have different power dependencies.", "layers": [ { "id": "voice-path", "name": "Voice path", "description": "Covers the transmitter, receiver, handset connections and controls governing conversation.", "findings": [ { "id": "speech-circuit-operation", "name": "Speech circuit operation", "description": "The model records how speech is transmitted and received, including any required handset switch or mode setting.", "questions": [ { "text": "Which circuit mode and handset controls are required for two-way speech?", "kind": "definition", "id": "speech-circuit-operation-q01" }, { "text": "What documented test establishes intelligible transmission and reception independently?", "kind": "action", "id": "speech-circuit-operation-q02" } ] } ] }, { "id": "supply-arrangements", "name": "Supply arrangements", "description": "Separates local supply requirements from any power obtained through the line.", "findings": [ { "id": "power-dependencies", "name": "Power dependencies", "description": "Each function needs an explicit power dependency, permitted supply and assessment method.", "questions": [ { "text": "Which functions require local batteries, line power, a hand generator or another documented source?", "kind": "definition", "id": "power-dependencies-q01" }, { "text": "What voltage, polarity and loaded-supply measurements establish acceptable operation?", "kind": "measurement", "id": "power-dependencies-q02" }, { "text": "Which replacement cells or external supplies are approved for this design?", "kind": "action", "id": "power-dependencies-q03" } ] } ] } ] }, { "id": "calling-and-control", "name": "Calling and control", "description": "Captures how calls are initiated, detected, answered and ended.", "rationale": "An audible speech path alone does not establish a usable telephone connection if calling or supervision is incompatible.", "layers": [ { "id": "outgoing-signalling", "name": "Outgoing signalling", "description": "Describes the mechanism and electrical conditions used to alert the connected party.", "findings": [ { "id": "call-generation", "name": "Call generation", "description": "The outgoing call signal must be identified and matched to the receiving endpoint or switchboard.", "questions": [ { "text": "How does the operator generate a call signal in each supported operating mode?", "kind": "action", "id": "call-generation-q01" }, { "text": "What signal voltage, frequency or other interface parameters are specified, and under what load?", "kind": "measurement", "id": "call-generation-q02" } ] } ] }, { "id": "incoming-call-and-supervision", "name": "Incoming call and supervision", "description": "Covers incoming alerts and any circuit state changes associated with answering or clearing.", "findings": [ { "id": "call-state-behaviour", "name": "Call state behaviour", "description": "Alerting, answer and clearing behaviour are configuration-dependent and must be distinguished from speech operation.", "questions": [ { "text": "What indicates an incoming call, and what controls or settings can disable that indication?", "kind": "definition", "id": "call-state-behaviour-q01" }, { "text": "What actions answer and end a call, and does the connected switchboard require a separate clearing signal?", "kind": "action", "id": "call-state-behaviour-q02" } ] } ] } ] }, { "id": "line-and-interoperability", "name": "Line and interoperability", "description": "Defines connection requirements and the evidence needed to judge operation over a particular field line.", "rationale": "Usable reach depends on the line and counterpart equipment; a shared connector or quoted distance is insufficient.", "layers": [ { "id": "electrical-connection", "name": "Electrical connection", "description": "Relates terminals and supported circuit arrangements to compatible counterparts.", "findings": [ { "id": "compatible-circuit", "name": "Compatible circuit", "description": "A valid connection requires agreement on conductor arrangement, power, speech interface and signalling.", "questions": [ { "text": "Which terminal assignments and conductor arrangements are supported by the applicable documentation?", "kind": "definition", "id": "compatible-circuit-q01" }, { "text": "What evidence establishes compatibility with the proposed remote telephone or switchboard port?", "kind": "provenance", "id": "compatible-circuit-q02" }, { "text": "Does the proposed connection need an adapter or interface outside the telephone's own boundary?", "kind": "boundary", "id": "compatible-circuit-q03" } ] } ] }, { "id": "conditional-line-performance", "name": "Conditional line performance", "description": "Assesses speech and calling against measured or documented line conditions.", "findings": [ { "id": "usable-line-envelope", "name": "Usable line envelope", "description": "Any distance claim must retain its cable, circuit, supply and test conditions, with speech and signalling assessed separately.", "questions": [ { "text": "What loop resistance, insulation condition and attenuation are measured for the proposed line?", "kind": "measurement", "id": "usable-line-envelope-q01" }, { "text": "Under which cable and operating conditions are the documented speech and signalling limits valid?", "kind": "provenance", "id": "usable-line-envelope-q02" } ] } ] } ] }, { "id": "field-readiness-and-care", "name": "Field readiness and care", "description": "Supports deployment, safe handling, fault isolation and recovery of the telephone.", "rationale": "Field readiness depends on exposed terminals, portable power, handset integrity and protective construction as well as successful conversation.", "layers": [ { "id": "deployment-and-exposure", "name": "Deployment and exposure", "description": "Checks the carried assembly, protective features and electrical conditions before use.", "findings": [ { "id": "deployment-suitability", "name": "Deployment suitability", "description": "Suitability requires evidence for the complete operating configuration, including open covers, connected leads and environmental exposure.", "questions": [ { "text": "What carried mass, dimensions and environmental limits apply with the required accessories fitted?", "kind": "measurement", "id": "deployment-suitability-q01" }, { "text": "Which documented checks and precautions address ringing voltage, foreign line voltage and weather-related line exposure before connection or repair?", "kind": "action", "id": "deployment-suitability-q02" }, { "text": "Which issuing body, standard edition and test record support any claimed protection or certification?", "kind": "provenance", "id": "deployment-suitability-q03" } ] } ] }, { "id": "fault-isolation-and-maintenance", "name": "Fault isolation and maintenance", "description": "Distinguishes failed speech, failed calling, supply problems and external line faults.", "findings": [ { "id": "serviceability-evidence", "name": "Serviceability evidence", "description": "Readiness follows configuration-specific checks of power, speech, signalling and physical condition; unresolved faults remain explicit.", "questions": [ { "text": "Which approved checks distinguish battery depletion, handset or cord defects, signalling faults and an external line fault?", "kind": "action", "id": "serviceability-evidence-q01" }, { "text": "Which observed defects require cleaning, approved component replacement, specialist repair or withdrawal from service?", "kind": "action", "id": "serviceability-evidence-q02" }, { "text": "What test results and remaining limitations justify the recorded readiness state?", "kind": "measurement", "id": "serviceability-evidence-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": [ "Battery requirements, line reach, mass, ringing voltage and environmental limits are model-specific; no class-wide numerical ranges are asserted.", "Many classic sets use battery-powered speech and hand-cranked magneto calling, but neither arrangement defines every field telephone.", "Applicable military specifications, environmental qualification standards and compatibility requirements should be checked against the particular model and procurement authority." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of field telephone 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": [ "Local-battery analog field telephones", "Common-battery analog field telephones", "Sound-powered field telephones", "Digital field telephones" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of field telephone 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": "U.S. Joint Electronics Type Designation System", "value_or_pattern": "TA-312/PT", "note": "An example equipment designation for a field telephone model, not an identifier for the entire device class." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of field telephone 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": [ "Connecting military command posts, observation posts and defensive positions.", "Providing wired voice links where radio transmission is undesirable or unreliable.", "Connecting dispersed users through a field telephone switchboard.", "Providing temporary communications during training exercises and emergency operations." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of field telephone 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": [ "Broken conductors, damaged connectors or loose terminals interrupt communication.", "Damaged insulation and wet connections cause leakage, noise or short circuits.", "Depleted or leaking batteries impair speech in local-battery sets and can damage contacts.", "Lightning or accidental contact with electrical power conductors can introduce dangerous voltages into deployed lines.", "Exposed wire routes are vulnerable to vehicle damage, create trip hazards and can be physically tapped." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of field telephone 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": [ "National military procurement systems use different equipment designations, connectors and signaling arrangements; interoperability requires checking the actual equipment." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of field telephone 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": "Telephone", "difference": "A field telephone is a telephone subtype specifically adapted for portable use and temporary wire deployment under field conditions." }, { "name": "Two-way radio", "difference": "A two-way radio communicates through radio waves; a field telephone normally uses a physical wire circuit." }, { "name": "Field telephone switchboard", "difference": "A switchboard connects and routes calls among circuits; a field telephone is a user's endpoint." }, { "name": "Sound-powered telephone", "difference": "Sound-powered describes how speech signals are generated without an external speech-power supply; field telephone describes deployment and construction, so the categories overlap." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of field telephone this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend to include sound-powered and digital field telephones, or only conventional analogue field telephone designs?", "Which existing Vercy telephone or military communications models should supply inherited concepts without duplicating this entry?", "Which primary manuals establish representative operating modes, signal characteristics and conditional line-performance limits?", "Which environmental, electrical safety and interoperability standards apply to particular design families, and which are procurement-specific requirements?", "Which maintenance tasks are operator-permitted across documented designs, and which require specialist facilities or obsolete replacement parts?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 31 } }