{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:07:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.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: 01a09514-be03-7590-9f3d-f1b120821c27\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Ground Master 400\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: 10", "usd": 0.0, "recall": true }, "codex": { "seconds": 73.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: 01a09514-bdfb-7ba0-bf1e-21ffd676ca33\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Ground Master 400\nRegistry id: vr.tr.ground-master-400\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entr" } }, "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", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:31+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q5610868", "registryId": "vr.tr.ground-master-400", "name": "Ground Master 400", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5610868/", "model": { "registry_id": "vr.tr.ground-master-400", "name": "Ground Master 400", "purpose": "Enable an agent to recognise the Ground Master 400 radar product, interpret configuration-specific capability and condition evidence, and determine whether inspection, maintenance or authorised surveillance use is supported.", "definition": "Ground Master 400 is a family of transportable, ground-based, three-dimensional air-surveillance radars developed by Thales, using an active electronically scanned array to detect and track aerial targets for air defence.", "scope_statement": "This model owns the product-level identity and assessment requirements of Ground Master 400 under vr.tr.ground-master-400, distinguishing original GM400 specifications from GM400 Alpha upgrades and linking individual installations as instances.", "in_scope": [ "GM400 product identity, manufacturer documentation and configuration lineage", "Three-dimensional air-surveillance function and configuration-specific performance evidence", "Radar equipment boundary, deployment configuration and supporting services", "Surveillance outputs and integration dependencies", "Readiness, maintenance evidence and operating authorisation" ], "out_of_scope": [ "The complete Ground Master radar portfolio", "Individual radar asset histories except as linked instance evidence", "National air-defence networks and command organisations", "Weapon engagement decisions and fire-control procedures", "Tactical deployment optimisation or countermeasure techniques" ], "distinguishing_features": [ "Require manufacturer or procurement evidence explicitly identifying Ground Master 400 or GM400; a generic Ground Master designation is insufficient.", "Identify the product as a ground-based long-range three-dimensional air-surveillance radar, rather than a complete air-defence system.", "Distinguish the original GM400 configuration from GM400 Alpha: Thales describes Alpha as an evolution with upgraded processing and extended range. [Thales launch announcement](https://www.thalesgroup.com/en/print/pdf/node/10101)", "Separate product identity from serial-numbered equipment and from the wider installation supplying power, communications and operator facilities." ], "characteristics": [ { "name": "Product and upgrade baseline", "kind": "category", "unit_or_values": "Original GM400; documented GM400 Alpha configuration; other documented baseline; unresolved", "why_it_matters": "Prevents transferring capability claims between generations." }, { "name": "Configuration evidence", "kind": "relation", "unit_or_values": "Manufacturer specification, equipment identification, acceptance record and applicable revision", "why_it_matters": "Connects the assessed radar to the documents that actually govern it." }, { "name": "Instrumented surveillance range", "kind": "measurement", "unit_or_values": "km, with configuration, mode and source; no default value", "why_it_matters": "Instrumented range must remain distinct from demonstrated detection performance." }, { "name": "Three-dimensional measurement performance", "kind": "measurement", "unit_or_values": "Range and altitude uncertainty in m; azimuth uncertainty in degrees; stated test conditions", "why_it_matters": "Supports judging whether radar reports meet the receiving system's needs." }, { "name": "Surveillance update interval", "kind": "measurement", "unit_or_values": "s, with operating mode and definition of update", "why_it_matters": "Distinguishes antenna revisit, local track refresh and delivered report timing." }, { "name": "Installation configuration", "kind": "category", "unit_or_values": "Documented transport, deployed or fixed installation arrangement", "why_it_matters": "Determines which support equipment and acceptance evidence apply." }, { "name": "Electrical supply requirement", "kind": "measurement", "unit_or_values": "V, Hz and kW or kVA, with equipment boundary and operating state", "why_it_matters": "Enables compatibility checks without assuming a universal generator package." }, { "name": "Readiness assessment", "kind": "state", "unit_or_values": "Unassessed; unavailable; maintenance; restricted; ready, mapped to documented equipment states", "why_it_matters": "Separates an agent's assessment from manufacturer status codes." }, { "name": "Surveillance interface baseline", "kind": "relation", "unit_or_values": "Applicable interface specification, software revision and receiving-system acceptance", "why_it_matters": "A functioning radar does not by itself establish usable integration." } ], "affordances": [ "Resolve a GM400-labelled record to its documented product and upgrade baseline.", "Compare a claimed capability with configuration-specific specifications and acceptance evidence.", "Assess installation support requirements against documented power, environmental and interface constraints.", "Interpret readiness evidence and identify missing inspections or maintenance approvals.", "Check whether delivered surveillance reports meet an authorised receiving system's acceptance criteria." ], "agent_conduct": { "may": [ "Describe this radar family from public, official and manufacturer-neutral sources.", "Report publicly announced deployments and capabilities without speculation." ], "must_not": [ "Help locate, jam, spoof or attack such radars or their crews.", "Disclose non-public technical, operational or deployment details.", "Help export or transfer such systems outside arms control rules." ], "requires_human": [ "Any request touching on military use, procurement or transfer of the system." ] }, "ethics": { "considerations": [ "Air-surveillance radar protects airspace and is also a military target.", "Arms transfers can fuel conflict and abuse." ], "affected_parties": [ "Operating forces and crews", "Civilians in conflict areas", "Air traffic users" ] }, "owners": { "steward": "The operating air force or defence ministry that holds each unit.", "master_systems": [] }, "visual_identification": [ "A large flat rotating antenna array mounted on a truck or trailer.", "Usually deployed with a shelter or vehicle for operators and a generator." ], "failure_modes_and_hazards": [ "Strong radio emissions can harm people too close to the antenna.", "Interference with other spectrum users if wrongly operated." ], "standards_and_regulation": [ "Arms Trade Treaty, United Nations.", "Wassenaar Arrangement on Export Controls for Conventional Arms and Dual-Use Goods and Technologies." ], "what_it_is_for": [ "This transportable radar family is used by military air-surveillance and air-defence organizations to detect and track aerial objects.", "It supports the production of an air picture for command systems at prepared sites or temporary deployments.", "Its use and maintenance depend on the installed configuration, site conditions and authorized operational role." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q5610868: Ground Master 400", "url": "https://www.wikidata.org/wiki/Q5610868", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Ground Master 400", "url": "https://en.wikipedia.org/wiki/Ground_Master_400", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "gm400-identity-and-lineage", "name": "GM400 identity and lineage", "description": "Establish which GM400 product configuration a record describes.", "rationale": "Original and upgraded GM400 records can share a name while requiring different capability evidence.", "layers": [ { "id": "product-identification", "name": "Product identification", "description": "Resolve the registry name against authoritative product evidence.", "findings": [ { "id": "gm400-identification-evidence", "name": "GM400 identification evidence", "description": "Require evidence of the GM400 designation and distinguish product records from equipment instances.", "questions": [ { "text": "Which manufacturer or procurement document identifies this record as Ground Master 400?", "kind": "provenance", "id": "gm400-identification-evidence-q01" }, { "text": "Does the record describe the product, a purchased configuration or one serial-numbered radar?", "kind": "boundary", "id": "gm400-identification-evidence-q02" } ] } ] }, { "id": "upgrade-applicability", "name": "Upgrade applicability", "description": "Control how original and Alpha evidence attaches to the registered thing.", "findings": [ { "id": "baseline-and-upgrade-status", "name": "Baseline and upgrade status", "description": "Keep original GM400 claims separate from Alpha claims unless an upgrade is documented.", "questions": [ { "text": "Which hardware and software records establish the applicable GM400 baseline?", "kind": "provenance", "id": "baseline-and-upgrade-status-q01" }, { "text": "What evidence establishes completion and acceptance of any Alpha upgrade?", "kind": "provenance", "id": "baseline-and-upgrade-status-q02" }, { "text": "Does the registry treat Alpha as a configuration of this entry or as a separately registered product?", "kind": "boundary", "id": "baseline-and-upgrade-status-q03" } ] } ] } ] }, { "id": "surveillance-function-and-evidence", "name": "Surveillance function and evidence", "description": "Represent what the GM400 measures and how capability claims are qualified.", "rationale": "A long-range radar designation alone cannot establish useful detection or tracking performance.", "layers": [ { "id": "radar-measurement-chain", "name": "Radar measurement chain", "description": "Identify the documented sensing and processing principles of the selected baseline.", "findings": [ { "id": "three-dimensional-surveillance", "name": "Three-dimensional surveillance", "description": "Record how the baseline obtains spatial measurements and turns observations into surveillance reports.", "questions": [ { "text": "Which authoritative GM400 document establishes its frequency band, antenna architecture and scanning principle?", "kind": "provenance", "id": "three-dimensional-surveillance-q01" }, { "text": "Which outputs are direct radar measurements and which are estimated track attributes?", "kind": "definition", "id": "three-dimensional-surveillance-q02" } ] } ] }, { "id": "performance-qualification", "name": "Performance qualification", "description": "Attach measurement definitions and conditions to GM400 performance figures.", "findings": [ { "id": "range-and-report-quality", "name": "Range and report quality", "description": "Record range, accuracy and update claims without treating headline coverage as guaranteed detection.", "questions": [ { "text": "What instrumented range, measurement accuracy and update interval are specified for this baseline and mode?", "kind": "measurement", "id": "range-and-report-quality-q01" }, { "text": "Which target assumptions, environmental conditions and acceptance criteria accompany demonstrated detection performance?", "kind": "measurement", "id": "range-and-report-quality-q02" }, { "text": "Which reported figures describe radar observations, maintained tracks or exported reports?", "kind": "definition", "id": "range-and-report-quality-q03" } ] } ] } ] }, { "id": "installation-and-support-boundary", "name": "Installation and support boundary", "description": "Determine what a GM400 installation includes and which external services it needs.", "rationale": "Transportability and readiness depend on the delivered equipment package and installation conditions.", "layers": [ { "id": "equipment-package", "name": "Equipment package", "description": "Identify the radar assembly and separately supplied installation equipment.", "findings": [ { "id": "delivered-system-boundary", "name": "Delivered system boundary", "description": "Separate the GM400 radar from its transport platform, site works and optional supporting equipment.", "questions": [ { "text": "Which antenna, electronics, operator and support assemblies belong to the documented GM400 delivery?", "kind": "boundary", "id": "delivered-system-boundary-q01" }, { "text": "What transport and deployed dimensions and masses apply to that package?", "kind": "measurement", "id": "delivered-system-boundary-q02" } ] } ] }, { "id": "installation-services", "name": "Installation services", "description": "Record power, cooling and environmental dependencies from applicable installation documents.", "findings": [ { "id": "support-service-compatibility", "name": "Support service compatibility", "description": "Require configuration-specific evidence that the installation supports approved radar operation.", "questions": [ { "text": "What electrical supply, cooling and earthing requirements apply to this GM400 configuration?", "kind": "measurement", "id": "support-service-compatibility-q01" }, { "text": "Which environmental limits and installation acceptance records govern readiness at this site?", "kind": "provenance", "id": "support-service-compatibility-q02" } ] } ] } ] }, { "id": "surveillance-output-and-integration", "name": "Surveillance output and integration", "description": "Define the boundary between GM400 observations and the receiving air-surveillance system.", "rationale": "Radar operation, identity information and an integrated air picture require distinct evidence.", "layers": [ { "id": "report-semantics", "name": "Report semantics", "description": "Identify the meaning, timing and reference frames of exported radar information.", "findings": [ { "id": "exported-report-contract", "name": "Exported report contract", "description": "Record the applicable output contract without assuming an interface standard.", "questions": [ { "text": "Which interface specification and revision define the GM400 reports delivered to the receiving system?", "kind": "provenance", "id": "exported-report-contract-q01" }, { "text": "How are position reference, timestamps, track identifiers and quality indicators defined?", "kind": "definition", "id": "exported-report-contract-q02" } ] } ] }, { "id": "external-system-dependencies", "name": "External system dependencies", "description": "Separate primary radar performance from identification and network integration.", "findings": [ { "id": "identification-and-network-boundaries", "name": "Identification and network boundaries", "description": "Treat associated identification equipment and command-system functions as explicit dependencies.", "questions": [ { "text": "Is identification equipment included, separately integrated or absent in this GM400 installation?", "kind": "boundary", "id": "identification-and-network-boundaries-q01" }, { "text": "Which acceptance evidence confirms correct report exchange with the intended receiving system?", "kind": "provenance", "id": "identification-and-network-boundaries-q02" }, { "text": "What documented restrictions apply when identification or communications services are unavailable?", "kind": "action", "id": "identification-and-network-boundaries-q03" } ] } ] } ] }, { "id": "readiness-maintenance-and-authorisation", "name": "Readiness, maintenance and authorisation", "description": "Connect GM400 condition evidence to permitted maintenance and surveillance use.", "rationale": "A powered radar may still have degraded measurement performance or lack approval to transmit.", "layers": [ { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Interpret diagnostics and service history against the applicable GM400 baseline.", "findings": [ { "id": "serviceability-evidence", "name": "Serviceability evidence", "description": "Link reported faults and completed maintenance to documented restrictions and acceptance checks.", "questions": [ { "text": "Which diagnostics and inspection results establish the condition of the antenna, transmitter, receiver, processing and cooling assemblies?", "kind": "measurement", "id": "serviceability-evidence-q01" }, { "text": "Which manufacturer documents define maintenance intervals, consumables and fault-related operating restrictions?", "kind": "provenance", "id": "serviceability-evidence-q02" }, { "text": "What acceptance checks are required after component replacement or a software upgrade?", "kind": "action", "id": "serviceability-evidence-q03" } ] } ] }, { "id": "safe-authorised-operation", "name": "Safe authorised operation", "description": "Identify the evidence required before a GM400 installation may emit or enter service.", "findings": [ { "id": "transmission-and-service-release", "name": "Transmission and service release", "description": "Keep technical readiness, personnel safety and transmission authorisation separately assessable.", "questions": [ { "text": "Which applicable documents establish RF exposure controls, electrical protections and antenna-motion safeguards?", "kind": "provenance", "id": "transmission-and-service-release-q01" }, { "text": "Which issuing bodies and document revisions govern spectrum authorisation and installation safety acceptance?", "kind": "provenance", "id": "transmission-and-service-release-q02" }, { "text": "Who may approve transmission and return to service, and what evidence must that approval reference?", "kind": "action", "id": "transmission-and-service-release-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 description is recalled knowledge; no sources were consulted.", "Confirm the manufacturer's exact variant hierarchy and distinguish baseline GM400 specifications from GM400 Alpha specifications.", "Detection range, altitude coverage, update rate, transport dimensions and applicable standards require variant-specific verification; they are omitted here." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Ground Master 400 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": [ "Ground Master 400 Alpha (GM400α), an enhanced variant" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Ground Master 400 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": "Thales product designation", "value_or_pattern": "Ground Master 400; GM400", "note": "Identifies a radar product family, not an individual radar installation." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Ground Master 400 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": [ "Long-range surveillance of national airspace", "Supplying air tracks to integrated air-defence command systems", "Detecting and tracking aircraft and other airborne targets", "Deployable surveillance supporting military operations" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Ground Master 400 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": "Nominal surveillance coverage in azimuth", "typical_range": "360", "unit": "degree" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Ground Master 400 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": [ "Terrain masking and the radar horizon limit detection of low-altitude targets.", "Electronic interference or deliberate jamming can degrade detection and tracking.", "Clutter and propagation effects can produce false detections or reduce track quality.", "Failures of electrical power, cooling or communications can interrupt surveillance or delivery of tracks.", "High-power radio-frequency emissions require controlled exposure around the operating antenna." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Ground Master 400 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": "Ground Master 200", "difference": "A separate Thales radar family oriented toward medium-range surveillance; it is not a Ground Master 400 variant." }, { "name": "Air-defence missile system", "difference": "Ground Master 400 supplies surveillance and tracking information; it does not itself launch interceptors." }, { "name": "Individual Ground Master 400 radar unit", "difference": "A physical unit has its own serial number, configuration and service history; this entry describes the product family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Ground Master 400 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.ground-master-400 cover the original GM400 alone or the product lineage including Alpha, and does an existing world-model publication already cover that scope?", "Which original GM400 technical documents establish antenna architecture, frequency band and performance without importing Alpha specifications?", "What configuration-specific dimensions, masses, power requirements and environmental limits apply across documented delivery packages?", "Which surveillance and identification interfaces are standard, optional or customer-specific?", "Which maintenance manuals, acceptance standards, safety interlocks and issuing-body approvals are publicly verifiable for the relevant baseline?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 32 } }