{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:00:26Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 27.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: 01a09545-8d01-73f2-9d7e-775b428674a5\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: location identifier\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: ", "usd": 0.0, "recall": true }, "codex": { "seconds": 67.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: 01a09545-8cf9-7463-ab47-12f02570b2a1\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: location identifier\nRegistry id: vr.tr.location-identifier\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this " } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:39:29+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "revisions": [ { "at": "2026-10-07T11:36:50+00:00", "engine": "codex", "fields": [ "definition", "distinguishing_features", "in_scope", "out_of_scope", "scope_statement" ], "answering_review": "6482f9c6aea64448c085e63c8587d7fabdcebb58f0fe5747e0c3d56ac47172f5" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T12:16:33+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q568407", "registryId": "vr.tr.location-identifier", "name": "location identifier", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q568407/", "model": { "registry_id": "vr.tr.location-identifier", "name": "location identifier", "purpose": "Enable an agent to interpret a location identifier, establish which location it denotes in a stated context, assess whether that association remains usable, and choose appropriate lookup or reference actions.", "definition": "A location identifier is a code assigned within a defined scheme to identify an air-navigation location or facility, or a weather station.", "scope_statement": "This model owns codes identifying air-navigation locations or facilities and weather stations, including their namespaces, referents, resolution behavior, validity and relationships to identifiers in other relevant schemes.", "in_scope": [ "Identifier values, representations and namespaces belong to air-navigation or weather-station identification schemes.", "The designated referent is an air-navigation location or facility, or a weather station.", "Assignment authorities and supporting evidence establish the association between a code and its referent.", "Lookup, disambiguation and cross-system mappings concern these air-navigation and weather-station codes.", "Validity periods, retirement, reassignment and replacement affect the interpretation of these codes." ], "out_of_scope": [ "The physical location, its condition and its operational capabilities are outside this identifier model.", "Geometry, surveying observations and coordinate reference systems are outside this identifier model.", "Transport routes and navigation instructions are outside this identifier model.", "Network resource addresses are outside this air-navigation and weather-station code sense.", "Generic geographic identifiers, street addresses, coordinate strings and ordinary place names are outside this sense." ], "distinguishing_features": [ "A qualifying code identifies an air-navigation location or facility, or a weather station, within an established identification scheme.", "The identifier and the location are distinct: changing a designation need not mean the location changed.", "A bare value is insufficient where different namespaces or assignment periods can give it different referents.", "A name, street address or coordinate string does not qualify merely because it can identify a geographic location.", "An identifier for an organisation or asset is not automatically a location identifier merely because that entity occupies a place." ], "characteristics": [ { "name": "Identifier value", "kind": "category", "unit_or_values": "Recorded designation with its original spelling, case, separators and leading zeros", "why_it_matters": "Preserves distinctions that conversion or normalization could erase." }, { "name": "Namespace", "kind": "relation", "unit_or_values": "Reference to the assigning scheme and applicable jurisdiction or context", "why_it_matters": "Determines how a value can be interpreted and compared." }, { "name": "Location referent", "kind": "relation", "unit_or_values": "Reference to the designated location, supported by assignment or lookup evidence", "why_it_matters": "Separates the designation from the place it identifies." }, { "name": "Referent granularity", "kind": "category", "unit_or_values": "Scheme-defined location type, such as site, facility, entrance, room or area; unknown", "why_it_matters": "Prevents a code for an entire site from being treated as an exact access point." }, { "name": "Assignment authority", "kind": "relation", "unit_or_values": "Organisation, system or documented local convention responsible for assignment", "why_it_matters": "Establishes whose records support the identifier-location association." }, { "name": "Assignment status", "kind": "state", "unit_or_values": "Unverified, active, retired, superseded, disputed or unknown, mapped to scheme terminology", "why_it_matters": "Guides whether an identifier can support present use or only historical reference." }, { "name": "Assignment validity interval", "kind": "measurement", "unit_or_values": "Start and end date-times with stated precision; open-ended or unknown where applicable", "why_it_matters": "Distinguishes successive assignments when values are reused." }, { "name": "Resolution outcome", "kind": "state", "unit_or_values": "One matching referent, multiple candidates, no match, lookup unavailable or not checked", "why_it_matters": "Separates ambiguity and absence from a temporary inability to consult records." }, { "name": "Cross-namespace correspondence", "kind": "relation", "unit_or_values": "Evidence-backed equivalent, broader, narrower, overlapping or unresolved location reference", "why_it_matters": "Prevents approximate mappings from becoming false identity claims." } ], "affordances": [ "Validate a designation against the rules of its stated namespace.", "Resolve an identifier to a location using a relevant authority and assignment date.", "Request missing namespace or contextual information when a value is ambiguous.", "Compare identifiers while preserving differences in referent granularity and validity period.", "Follow documented replacements while retaining historical references.", "Determine whether the identified location is specific enough for an intended action." ], "agent_conduct": { "may": [ "Resolve a location identifier to the facility it designates, naming the scheme it comes from.", "Flag codes that are ambiguous across schemes, such as three-letter and four-letter airport codes." ], "must_not": [ "Use an identifier from one scheme as if it belonged to another.", "Present a withdrawn or reassigned code as current.", "Use a location identifier in flight planning or safety messages without checking the official publication.", "Invent a code for a facility that has none." ], "requires_human": [ "Changing a location identifier in operational data such as flight plans or routing systems." ] }, "ethics": { "considerations": [ "Wrong codes in aviation and logistics send people, cargo or emergency help to the wrong place.", "Code assignments can carry political weight where territory is disputed." ], "affected_parties": [ "Passengers and crews", "Airport and air traffic operators", "Shippers and travellers" ] }, "owners": { "steward": "The body that runs the identification scheme, such as a civil aviation authority or an international organization.", "master_systems": [ "Official location indicator publications", "Aeronautical information publications" ] }, "visual_identification": [ "A short code of letters, sometimes digits, printed on tickets, baggage tags, charts and flight plans.", "Four-letter codes usually come from the aviation location indicator scheme and three-letter codes from the airline scheme." ], "failure_modes_and_hazards": [ "Confusing two similar codes misroutes baggage, cargo or travellers.", "Outdated codes in navigation or planning data can cause operational errors." ], "standards_and_regulation": [ "ICAO Doc 7910 Location Indicators, International Civil Aviation Organization." ], "what_it_is_for": [ "Location identifiers are encountered in aeronautical charts, flight plans, weather reports and facility directories.", "They allow people and information systems to reference airports, navigation facilities or weather stations concisely.", "Interpretation requires the identification scheme and a suitable reference date because different schemes can assign different codes to the same place or reuse similar codes." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q568407: location identifier", "url": "https://www.wikidata.org/wiki/Q568407", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Location identifier", "url": "https://en.wikipedia.org/wiki/Location_identifier", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-and-namespace", "name": "Designation and namespace", "description": "Establishes what the recorded value means as an identifier and which rules govern its interpretation.", "rationale": "A location code can look valid while belonging to a different scheme or requiring additional context.", "layers": [ { "id": "identifier-representation", "name": "Identifier representation", "description": "Separates the original designation from permitted comparison or display forms.", "findings": [ { "id": "significant-characters", "name": "Significant characters", "description": "Record which characters and formatting distinctions the scheme treats as meaningful.", "questions": [ { "text": "What is the exact recorded value, including leading zeros, case and separators?", "kind": "definition", "id": "significant-characters-q01" }, { "text": "Which transformations are explicitly permitted without changing the identifier's meaning?", "kind": "action", "id": "significant-characters-q02" } ] } ] }, { "id": "namespace-context", "name": "Namespace context", "description": "Identifies the scheme and any additional context needed to interpret the value.", "findings": [ { "id": "qualified-location-reference", "name": "Qualified location reference", "description": "Record the namespace and contextual qualifiers required to distinguish this assignment from others.", "questions": [ { "text": "Which scheme or local convention assigns this value?", "kind": "provenance", "id": "qualified-location-reference-q01" }, { "text": "Must the value be qualified by a jurisdiction, parent site, issuer or date to identify a location?", "kind": "boundary", "id": "qualified-location-reference-q02" } ] } ] } ] }, { "id": "location-referent-and-granularity", "name": "Location referent and granularity", "description": "Establishes which kind of location is designated and the extent of that reference.", "rationale": "An agent must distinguish a site, a facility and a particular entrance before acting on their identifiers.", "layers": [ { "id": "designated-location-kind", "name": "Designated location kind", "description": "Distinguishes a location reference from references to occupants, assets or services associated with it.", "findings": [ { "id": "direct-referent", "name": "Direct referent", "description": "Record what the identifier directly denotes rather than inferring its referent from nearby entities.", "questions": [ { "text": "Does this designation identify a geographic place, facility, sublocation or another kind of location?", "kind": "definition", "id": "direct-referent-q01" }, { "text": "Does the issuing record identify the location itself or an organisation, asset or service situated there?", "kind": "boundary", "id": "direct-referent-q02" } ] } ] }, { "id": "spatial-specificity", "name": "Spatial specificity", "description": "Captures how precisely the designated location supports the intended use.", "findings": [ { "id": "extent-and-access-point", "name": "Extent and access point", "description": "Distinguish the designated location's extent from any representative point or access point returned with it.", "questions": [ { "text": "What location extent or level of subdivision does the assignment cover?", "kind": "boundary", "id": "extent-and-access-point-q01" }, { "text": "If a lookup returns coordinates, do they represent the location, its centre, an entrance or some other point?", "kind": "definition", "id": "extent-and-access-point-q02" }, { "text": "Is this specificity sufficient for the proposed delivery, navigation or record-linking action?", "kind": "action", "id": "extent-and-access-point-q03" } ] } ] } ] }, { "id": "assignment-and-resolution", "name": "Assignment and resolution", "description": "Connects a designation to evidence of assignment and to a usable lookup procedure.", "rationale": "A plausible code or successful third-party search does not by itself establish an authoritative location association.", "layers": [ { "id": "assignment-evidence", "name": "Assignment evidence", "description": "Records who established the identifier-location association and where it can be checked.", "findings": [ { "id": "supported-association", "name": "Supported association", "description": "Track the source record supporting this particular assignment and distinguish it from inferred matches.", "questions": [ { "text": "Who assigned the designation, and which inspected record supports its association with this location?", "kind": "provenance", "id": "supported-association-q01" }, { "text": "Is the association explicitly recorded, locally asserted or inferred from matching names and addresses?", "kind": "provenance", "id": "supported-association-q02" } ] } ] }, { "id": "lookup-outcome", "name": "Lookup outcome", "description": "Defines how the identifier can be resolved and how unsuccessful or ambiguous results are interpreted.", "findings": [ { "id": "resolution-evidence", "name": "Resolution evidence", "description": "Record the lookup context, returned candidates and limits of the result.", "questions": [ { "text": "Which directory, service or local register can resolve this namespace, and what input qualifiers does it require?", "kind": "action", "id": "resolution-evidence-q01" }, { "text": "Did the lookup yield one location, several candidates, no record or an unavailable service?", "kind": "measurement", "id": "resolution-evidence-q02" }, { "text": "When was the lookup performed, and which record version or effective date did it consult?", "kind": "provenance", "id": "resolution-evidence-q03" } ] } ] } ] }, { "id": "assignment-over-time", "name": "Assignment over time", "description": "Tracks the period during which a designation refers to a particular location and how that association changes.", "rationale": "Historical references can be misinterpreted if current assignments or replacements are applied without checking dates.", "layers": [ { "id": "validity-and-reuse", "name": "Validity and reuse", "description": "Separates the lifespan of an identifier assignment from the lifespan of the location.", "findings": [ { "id": "time-qualified-assignment", "name": "Time-qualified assignment", "description": "Record assignment dates and any evidence that the same value has denoted another location.", "questions": [ { "text": "During which period is this value documented as identifying this location?", "kind": "measurement", "id": "time-qualified-assignment-q01" }, { "text": "Can this namespace reassign retired values, and is any previous or subsequent assignment documented here?", "kind": "boundary", "id": "time-qualified-assignment-q02" } ] } ] }, { "id": "retirement-and-succession", "name": "Retirement and succession", "description": "Distinguishes designation changes from changes to the designated location.", "findings": [ { "id": "replacement-meaning", "name": "Replacement meaning", "description": "Record whether a replacement preserves the referent or follows a relocation, split, merger or other change.", "questions": [ { "text": "Does a replacement identifier designate the same location or a changed successor location?", "kind": "boundary", "id": "replacement-meaning-q01" }, { "text": "For a present lookup or historical citation, should the agent retain this value, follow a successor or present both?", "kind": "action", "id": "replacement-meaning-q02" } ] } ] } ] }, { "id": "comparison-and-use", "name": "Comparison and use", "description": "Supports justified comparisons and decisions about using a resolved location reference.", "rationale": "Different schemes may identify overlapping locations, and successful identification alone does not establish suitability for every action.", "layers": [ { "id": "cross-scheme-matching", "name": "Cross-scheme matching", "description": "Evaluates whether identifiers in different namespaces denote the same location at compatible granularity.", "findings": [ { "id": "mapping-strength", "name": "Mapping strength", "description": "Record the evidence and spatial relationship behind a proposed correspondence.", "questions": [ { "text": "What evidence establishes that the two identifiers designate the same location rather than nearby or similarly named places?", "kind": "provenance", "id": "mapping-strength-q01" }, { "text": "Is the correspondence exact, broader, narrower, overlapping or unresolved, and for which assignment periods?", "kind": "boundary", "id": "mapping-strength-q02" } ] } ] }, { "id": "action-readiness", "name": "Action readiness", "description": "Assesses whether the identifier is sufficiently resolved, current and specific for a proposed use.", "findings": [ { "id": "usable-location-reference", "name": "Usable location reference", "description": "Connect remaining uncertainty to the information an agent must obtain before relying on the identifier.", "questions": [ { "text": "Which unresolved namespace, validity or granularity issue could change the location selected for this action?", "kind": "boundary", "id": "usable-location-reference-q01" }, { "text": "What additional qualifier or authoritative lookup would make the reference usable for the intended task?", "kind": "action", "id": "usable-location-reference-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": [ "The registry supplies no sense; check whether this entry means the aviation term specifically or the broader category of location codes.", "The listed schemes and documents are recalled, not consulted; current editions, assignment rules and code status require verification.", "Identifier uniqueness and persistence are properties of individual schemes, not guarantees inherent in the term." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of location identifier 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": [ "Airport identifiers", "Heliport identifiers", "Navigation-aid identifiers", "Transport and trade location codes", "Supply-chain physical-location identifiers" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of location identifier 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": "ICAO location indicators", "value_or_pattern": "Four letters", "note": "Identify locations used in international aeronautical communications; they are not restricted to commercial passenger airports." }, { "scheme": "IATA location codes", "value_or_pattern": "Three letters", "note": "Used for airports and certain cities, metropolitan areas and intermodal locations." }, { "scheme": "FAA location identifiers", "value_or_pattern": "Three or four alphanumeric characters", "note": "Used for aviation facilities in the United States; an FAA identifier need not equal the corresponding IATA code." }, { "scheme": "UN/LOCODE", "value_or_pattern": "Two-letter country code followed by three location characters", "note": "Identifies locations associated with trade and transport." }, { "scheme": "GS1 Global Location Number (GLN)", "value_or_pattern": "13 digits, including a check digit", "note": "Can identify physical locations, but also parties and functions; only part of its scope concerns geographic locations." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of location identifier 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": [ "ICAO Doc 7910, Location Indicators - International Civil Aviation Organization", "FAA Order JO 7350.9, Location Identifiers - Federal Aviation Administration", "Recommendation No. 16 concerning UN/LOCODE - United Nations Economic Commission for Europe", "GS1 General Specifications - GS1" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of location identifier 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": [ "Identifying departure, destination and alternate locations in aviation operations", "Naming airports and metropolitan destinations in passenger reservations and baggage handling", "Referencing trade and transport locations in logistics records", "Identifying delivery sites, warehouses and other physical locations in supply-chain data", "Linking records about the same location across information systems" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of location identifier 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": [ "Interpreting a code without its scheme can identify the wrong location.", "Confusing a metropolitan-area code with a particular airport can misdirect bookings or routing.", "Retired or reassigned identifiers can produce incorrect historical joins.", "Assuming that every location has an identifier in every scheme creates missing or false matches.", "Treating an identifier as a coordinate or a complete address can leave navigation or delivery information insufficient." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of location identifier 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": [ "The United States uses FAA identifiers alongside ICAO and IATA codes.", "ICAO indicators have regional allocation conventions; conversion from national or IATA codes cannot be assumed.", "UN/LOCODE incorporates a country-code component, whereas IATA codes do not explicitly encode a country." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of location identifier 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": "Geographic coordinate", "difference": "A coordinate specifies position in a reference system; a location identifier designates an entity through an assignment scheme." }, { "name": "Postal address", "difference": "A postal address supplies structured delivery information; a location identifier is a code whose meaning depends on its scheme." }, { "name": "Place name", "difference": "A place name is a linguistic designation and may be shared by many places; a location identifier is assigned within a managed namespace." }, { "name": "Airport code", "difference": "An airport code identifies an airport or an airport-related destination; location identifier also covers other facilities and locations." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of location identifier this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend a general class of location identifiers or a narrower concept such as transport facility codes?", "Does this entry include addresses, place names and coordinate-derived designations when used as identifiers, or do neighbouring entries own those forms?", "Are logical and virtual locations included, or is the intended scope limited to physical and geographic locations?", "Which existing Vercy models already own identifier namespaces, location geometry and assignment authorities, and could any already cover this concept?", "Which representative authoritative schemes should research examine to establish actual rules for uniqueness, normalization, reassignment and historical resolution?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 30 } }