{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:19:41Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.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: 01a09557-637f-78c1-b56c-90094dbc6c8d\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Military Unit Number\nSense to describe: (none recorded)\nDomain code: SOC.ORG\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044:", "usd": 0.0, "recall": true }, "codex": { "seconds": 54.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: 01a09557-6375-7d61-9681-88f37e8362cd\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Military Unit Number\nRegistry id: vr.tr.military-unit-number\nPlane / domain: SOC / SOC.ORG\nRegistry definition: (none recorded)\nNames folded into thi" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:42:51+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners" ] }, "revisions": [ { "at": "2026-10-07T11:19:06+00:00", "engine": "codex", "fields": [ "definition", "distinguishing_features", "in_scope", "owners", "purpose", "scope_statement" ], "answering_review": "cb8d568d5ce795103db243704414d44217fff3abc0ae2b6f44b5e2c6b6b1dc73" } ], "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T12:16:30+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q18713288", "registryId": "vr.tr.military-unit-number", "name": "Military Unit Number", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "SOC.ORG" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q18713288/", "model": { "registry_id": "vr.tr.military-unit-number", "name": "Military Unit Number", "purpose": "Enable an agent to interpret numeric designations of military and paramilitary units of post-Soviet states, establish which unit a designation denotes within its system and period, and judge whether it can safely support identification or reference.", "definition": "A Military Unit Number is a numeric designation assigned to a military or paramilitary unit in the designation systems of post-Soviet states, identifying the unit within a particular authority and period rather than necessarily expressing its descriptive name or tactical designation.", "scope_statement": "This model owns the numeric designation and its contextual assignment to a military or paramilitary unit in post-Soviet states; it does not own the unit itself or cover generic military identifiers worldwide.", "in_scope": [ "The numeric designation is recorded with significant leading zeros and any accompanying prefixes, suffixes or separators.", "The assigning authority and designation system establish the number's meaning within a post-Soviet state.", "The relationship between a number and the military or paramilitary unit it identifies is represented.", "Assignment, retirement, reassignment and periods of uncertain validity are represented.", "Evidence, ambiguity and permitted handling of number-to-unit mappings are assessed." ], "out_of_scope": [ "The unit's command structure, personnel, equipment and operational readiness", "Individual service numbers and personnel identifiers", "Equipment serial numbers and vehicle registration numbers", "Operational call signs, postal routing codes and location codes unless evidence establishes their role as unit numbers", "The complete unit name, insignia and honours beyond their relevance to interpreting the number" ], "distinguishing_features": [ "Its referent is a military or paramilitary unit within the numeric designation systems of post-Soviet states rather than an individual, asset, position or quantity of units.", "Evidence connects the value to the specified designation system; a numeral appearing in military text alone is insufficient.", "The same written value is not presumed to identify the same unit across services, authorities, states or periods.", "Its relationship to an ordinal in a unit title, an administrative identifier or a cover designation must be established rather than inferred from appearance.", "Renumbering a unit and assigning an old number to a different unit are represented as distinct events." ], "characteristics": [ { "name": "Recorded designation", "kind": "category", "unit_or_values": "Exact source string, preserving meaningful formatting", "why_it_matters": "Treating the designation as an integer can erase characters needed to distinguish assignments." }, { "name": "Designation role", "kind": "category", "unit_or_values": "Ordinal in unit title; administrative unit identifier; cover designation; other evidenced role; unresolved", "why_it_matters": "Different roles support different identification and disclosure decisions." }, { "name": "Numbering namespace", "kind": "relation", "unit_or_values": "Issuing authority, armed force or service, and identified numbering system", "why_it_matters": "A number acquires identifying meaning within a defined system." }, { "name": "Assigned unit", "kind": "relation", "unit_or_values": "Referenced unit identity, candidate identities or unresolved referent", "why_it_matters": "The designation must remain distinguishable from the organisation bearing it." }, { "name": "Assignment validity", "kind": "state", "unit_or_values": "Effective start and end dates with precision and uncertainty; unknown where unsupported", "why_it_matters": "A historical mapping may not identify the current bearer." }, { "name": "Assignment status", "kind": "state", "unit_or_values": "Reported assigned; confirmed assigned; retired; superseded; disputed; unknown", "why_it_matters": "Agents need to distinguish evidence of assignment from assumptions about present use." }, { "name": "Designation succession", "kind": "relation", "unit_or_values": "Previous or subsequent number for a unit, or previous or subsequent bearer of a number", "why_it_matters": "Number continuity and unit continuity are separate questions." }, { "name": "Mapping evidence", "kind": "relation", "unit_or_values": "Sources supporting the value, namespace, referent and validity period separately", "why_it_matters": "A source that displays a number may not establish the unit behind it." }, { "name": "Handling constraints", "kind": "state", "unit_or_values": "Documented access or disclosure conditions; no conditions recorded; unresolved", "why_it_matters": "Availability of a designation does not by itself establish permission to disclose its associated mapping." } ], "affordances": [ "Parse a designation while preserving the original written form.", "Resolve a number to candidate units using its numbering system and relevant date.", "Compare two references and identify missing context that prevents a reliable match.", "Trace renumbering and number reuse without automatically merging unit identities.", "Flag conflicting, stale or unsupported number-to-unit mappings for review.", "Prepare a contextualised unit reference with evidence and applicable handling conditions." ], "agent_conduct": { "may": [ "Explain what military unit numbers are and how they are used in records.", "Use declassified unit numbers to help researchers trace historical service records." ], "must_not": [ "Disclose current unit numbers linked to locations, personnel or movements.", "Compile unit numbers with personal data to identify or target soldiers or their families.", "Present a guess linking a number to a unit as confirmed." ], "requires_human": [ "Publishing any unit identifiers from recent conflicts." ] }, "ethics": { "considerations": [ "Unit numbers can reveal deployments and expose soldiers to danger.", "Historical records help families trace relatives, including those who died." ], "affected_parties": [ "Service members", "Their families", "Historians" ] }, "owners": { "steward": "The military or paramilitary authorities of post-Soviet states that assign the numbers are responsible for their records; archives hold historical records.", "master_systems": [ "Official military and paramilitary designation records document assignments.", "National military archives preserve historical records." ] }, "failure_modes_and_hazards": [ "Leaked unit numbers have exposed troop locations and identities.", "Mismatched numbers and names lead to errors in historical research." ], "what_it_is_for": [ "Military unit numbers appear in administrative records, official correspondence, postal addresses and historical sources concerning armed forces and some paramilitary organizations in post-Soviet states.", "They support reference to units within a particular national system and period, although reassignment and organizational changes can prevent a number from identifying the same unit over time." ], "facets_not_applicable": { "interfaces": "No single international standard governs these designations, and applicable administrative rules depend on the issuing state, service and period.", "recognition": "A military unit number is an abstract administrative identifier whose printed appearance alone cannot establish which unit it denotes." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q18713288: Military Unit Number", "url": "https://www.wikidata.org/wiki/Q18713288", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Military Unit Number", "url": "https://en.wikipedia.org/wiki/Military_Unit_Number", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-meaning", "name": "Designation meaning", "description": "Establish what the military unit number represents and which parts of its written form carry meaning.", "rationale": "A numeral in a unit title, an administrative code and a cover designation cannot be treated as interchangeable without evidence.", "layers": [ { "id": "number-role", "name": "Number role", "description": "Determine the identification function performed by the designation.", "findings": [ { "id": "establish-designation-function", "name": "Establish designation function", "description": "Record the evidenced role of the number and leave its role unresolved when the source supplies only a label.", "questions": [ { "text": "Does this number function as an ordinal in a unit title, an administrative identifier, a cover designation or another documented type?", "kind": "definition", "id": "establish-designation-function-q01" }, { "text": "What distinguishes it from a call sign, military postal address, personnel number or equipment number in this source?", "kind": "boundary", "id": "establish-designation-function-q02" } ] } ] }, { "id": "written-form", "name": "Written form", "description": "Preserve and interpret the complete designation string.", "findings": [ { "id": "preserve-significant-characters", "name": "Preserve significant characters", "description": "Separate the observed spelling from any normalised representation and document the basis for treating variants as equivalent.", "questions": [ { "text": "Which prefixes, suffixes, leading zeros, numeral conventions or separators are part of the designation?", "kind": "definition", "id": "preserve-significant-characters-q01" }, { "text": "What evidence permits two differently written forms to be treated as the same unit number?", "kind": "provenance", "id": "preserve-significant-characters-q02" } ] } ] } ] }, { "id": "namespace-and-unit-binding", "name": "Namespace and unit binding", "description": "Connect the designation to its numbering authority and organisational referent.", "rationale": "The number alone may be insufficient to distinguish units or establish whether two references denote the same organisation.", "layers": [ { "id": "numbering-jurisdiction", "name": "Numbering jurisdiction", "description": "Identify the system within which the number is assigned and interpreted.", "findings": [ { "id": "qualify-number-namespace", "name": "Qualify number namespace", "description": "Record the issuing authority and relevant service or organisational scope without assuming universal uniqueness.", "questions": [ { "text": "Which authority and numbering system govern this designation?", "kind": "provenance", "id": "qualify-number-namespace-q01" }, { "text": "Within what service, unit category, territory or period, if any, is the number intended to be unique?", "kind": "boundary", "id": "qualify-number-namespace-q02" } ] } ] }, { "id": "organisational-referent", "name": "Organisational referent", "description": "Establish the unit to which a particular number assignment refers.", "findings": [ { "id": "bind-number-to-unit", "name": "Bind number to unit", "description": "Represent the assignment as an evidenced relationship to a unit, retaining competing candidates when identification is incomplete.", "questions": [ { "text": "Which unit is explicitly associated with this number, and what source establishes that association?", "kind": "provenance", "id": "bind-number-to-unit-q01" }, { "text": "Does the designation refer to the whole unit, its headquarters, a subordinate element or an administrative grouping?", "kind": "boundary", "id": "bind-number-to-unit-q02" } ] } ] } ] }, { "id": "assignment-history", "name": "Assignment history", "description": "Track when the number identifies a unit and how assignments change.", "rationale": "A number can persist while its bearer changes, and a unit can persist through a change of number.", "layers": [ { "id": "validity-and-observation", "name": "Validity and observation", "description": "Distinguish effective assignment dates from dates when a designation was observed or reported.", "findings": [ { "id": "bound-assignment-period", "name": "Bound assignment period", "description": "Record supported temporal bounds and uncertainty without converting a dated mention into proof of continuing assignment.", "questions": [ { "text": "What evidence establishes the assignment's effective start and end, rather than merely a date of mention?", "kind": "provenance", "id": "bound-assignment-period-q01" }, { "text": "How precisely can the validity interval be bounded, and which portions remain unknown?", "kind": "measurement", "id": "bound-assignment-period-q02" } ] } ] }, { "id": "renumbering-and-reuse", "name": "Renumbering and reuse", "description": "Separate changes to a unit's designation from transfers or reuse of a designation.", "findings": [ { "id": "separate-number-and-unit-continuity", "name": "Separate number and unit continuity", "description": "Link preceding and succeeding assignments only to the extent that evidence establishes renumbering, reuse or organisational succession.", "questions": [ { "text": "Did the same unit receive a new number, or did a different unit receive the existing number?", "kind": "boundary", "id": "separate-number-and-unit-continuity-q01" }, { "text": "What evidence is required before references across a renumbering, merger, dissolution or reactivation may be linked?", "kind": "action", "id": "separate-number-and-unit-continuity-q02" } ] } ] } ] }, { "id": "evidence-and-use", "name": "Evidence and use", "description": "Determine how confidently an agent can interpret, cite or share a number-to-unit mapping.", "rationale": "A bare designation, a historical mapping and a verified current assignment support different actions.", "layers": [ { "id": "mapping-confidence", "name": "Mapping confidence", "description": "Assess source support for each component of an identification.", "findings": [ { "id": "evaluate-mapping-support", "name": "Evaluate mapping support", "description": "Distinguish evidence for the existence of a number from evidence for its bearer, numbering system and period of use.", "questions": [ { "text": "Does each source establish only the written number, or also its authority, assigned unit and assignment period?", "kind": "provenance", "id": "evaluate-mapping-support-q01" }, { "text": "Which conflicting mappings or missing contextual details require the agent to retain multiple candidates?", "kind": "action", "id": "evaluate-mapping-support-q02" } ] } ] }, { "id": "reference-and-disclosure", "name": "Reference and disclosure", "description": "Choose an adequately qualified reference and respect documented conditions on its use.", "findings": [ { "id": "qualify-permitted-use", "name": "Qualify permitted use", "description": "Attach sufficient context to avoid misleading identification and carry forward evidenced handling requirements for the mapping.", "questions": [ { "text": "Which authority, service, date and uncertainty qualifiers must accompany this number to identify the intended assignment?", "kind": "action", "id": "qualify-permitted-use-q01" }, { "text": "What documented conditions govern access to or disclosure of this number-to-unit mapping?", "kind": "action", "id": "qualify-permitted-use-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 label has no recorded sense; check whether it denotes a general unit identifier or a particular national military numbering practice.", "The SOC.ORG domain does not make the number itself an organization; distinguish the identifier from its referent.", "Check the issuing authority, historical period and reassignment rules before treating any particular number as a persistent identifier." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Military Unit Number 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": [ "Number forming part of a unit's formal designation", "Administrative unit number", "Cover number used in place of a descriptive unit name" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Military Unit Number 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": "United States Department of Defense Unit Identification Code (UIC)", "value_or_pattern": "Six-character alphanumeric code", "note": "A related administrative identifier; it is distinct from the ordinal number in a numbered unit's name." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Military Unit Number 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": [ "Associating personnel and administrative records with a unit", "Identifying units in logistics and supply records", "Distinguishing units in orders and official correspondence", "Referring to a unit without stating its descriptive name" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Military Unit Number 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": [ "Treating a number as globally unique when its uniqueness depends on the issuing military or administrative system", "Confusing a unit's administrative identifier with the number in its formal title", "Linking historical records incorrectly when numbers are reused or reassigned", "Assuming a number alone establishes a unit's size, function or command relationship" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Military Unit Number 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 militaries use different numbering systems, formats and rules for reassignment.", "Soviet and some post-Soviet military records use numbered military-unit references that can differ from a unit's descriptive formation designation.", "United States administrative records use UICs alongside formal unit designations." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Military Unit Number 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": "Military unit", "difference": "The unit is the organization; the number is a designation referring to it." }, { "name": "Military unit designation", "difference": "A full designation may include branch, echelon, function and honors in addition to a number." }, { "name": "Military service number", "difference": "A service number identifies an individual service member rather than a unit." }, { "name": "Military postal address", "difference": "A postal address routes correspondence; a unit number identifies a unit, although it may appear in that address." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Military Unit Number this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry entry denote unit numbering broadly or a particular national administrative or cover-designation practice?", "Should ordinals embedded in formal unit titles be included as instances, or only linked as neighbouring designations?", "Which authoritative sources define the relevant numbering systems, their assignment rules and their uniqueness boundaries?", "How should concurrent numbers for one unit and shared numbers across organisational elements be represented in the intended registry usage?", "What evidence establishes unit continuity when a number is retained or restored after reorganisation, dissolution or reactivation?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }