{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:19:32Z", "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: 01a09557-2e21-7ab2-b42d-e3ab874e8844\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: military identity document\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batc", "usd": 0.0, "recall": true }, "codex": { "seconds": 59.1, "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-2e19-75a2-ba7c-b2b6421f4f22\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: military identity document\nRegistry id: vr.tr.military-identity-document\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames fol" } }, "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" ] }, "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-Q563402", "registryId": "vr.tr.military-identity-document", "name": "military identity document", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q563402/", "model": { "registry_id": "vr.tr.military-identity-document", "name": "military identity document", "purpose": "Enable an agent to recognise a military identity document, assess its documented validity and evidential limits, and determine appropriate verification and handling actions.", "definition": "A military identity document is an official credential issued by a competent authority to identify a person and attest to that person's military status or affiliation.", "scope_statement": "This model owns a military identity credential's asserted identity and military affiliation, issuing authority, individual issuance, verification evidence, lifecycle and permitted uses, while keeping the credential distinct from its holder and the underlying personnel record.", "in_scope": [ "The document type and its stated military identification purpose", "Identity and military affiliation assertions associated with the holder", "Issuing authority, credential identifiers and issuance provenance", "Physical or digital manifestations and their connection to an issued credential", "Validity, replacement, cancellation and verification state", "Document-specific presentation, disclosure and handling constraints" ], "out_of_scope": [ "The holder's complete military service history or personnel file", "Military organisations, ranks and appointments as independently modelled entities", "General civilian identity documents without a military identification purpose", "Standalone access permissions, security clearances and benefit entitlements", "Medical records and clinical fitness determinations", "Detailed credential manufacturing or security-feature reproduction procedures" ], "distinguishing_features": [ "The document's declared purpose includes identifying a person in a military administrative or operational context; mentioning past service incidentally is insufficient.", "The military identity assertion is attributable to an identifiable issuing authority and credential scheme, rather than merely inferred from a uniform, insignia or personal claim.", "The credential binds identifying information to a particular holder; an anonymous military pass or equipment label does not meet that test.", "Its primary identification role distinguishes it from a service-history extract, discharge certificate or military order, unless the applicable scheme explicitly combines those functions.", "Any access, benefits or special-status function must be established separately for the relevant document type and context." ], "characteristics": [ { "name": "Credential scheme", "kind": "relation", "unit_or_values": "Reference to the issuing jurisdiction, responsible organisation and document scheme", "why_it_matters": "The scheme determines what the document asserts and how those assertions can be checked." }, { "name": "Holder binding", "kind": "relation", "unit_or_values": "Holder reference and recorded means of associating the credential with its presenter", "why_it_matters": "A genuine credential does not by itself establish that its presenter is the authorised holder." }, { "name": "Military affiliation assertion", "kind": "category", "unit_or_values": "Scheme-defined affiliation or holder category, preserving original terminology; unknown when unresolved", "why_it_matters": "The agent must avoid treating every holder category as equivalent to currently serving military personnel." }, { "name": "Credential identifier", "kind": "category", "unit_or_values": "Identifier value with issuing namespace and identifier role; absent, unreadable or withheld where applicable", "why_it_matters": "A document number must not be silently substituted for a personnel number or digital credential identifier." }, { "name": "Manifestation", "kind": "category", "unit_or_values": "Physical original, native digital credential, scan, photograph, certified copy or other scheme-defined form", "why_it_matters": "Different manifestations can support different verification operations and levels of evidential confidence." }, { "name": "Credential lifecycle state", "kind": "state", "unit_or_values": "Issued, active, expired, suspended, revoked, replaced, surrendered or unknown, subject to scheme terminology", "why_it_matters": "Possession and apparent authenticity do not establish current validity." }, { "name": "Validity interval", "kind": "measurement", "unit_or_values": "Effective and expiry timestamps with precision and timezone where relevant; not stated or unknown", "why_it_matters": "Time-limited assertions need a reference time, and missing expiry information is not proof of indefinite validity." }, { "name": "Verification state", "kind": "state", "unit_or_values": "Not checked, inconclusive, supported or contradicted, recorded separately for authenticity, holder binding and current validity", "why_it_matters": "Separate results prevent one successful check from being mistaken for complete verification." }, { "name": "Recognised use", "kind": "relation", "unit_or_values": "Specific use linked to the accepting authority, applicable rule and conditions", "why_it_matters": "Recognition for one purpose or organisation does not establish recognition elsewhere." } ], "affordances": [ "Classify a presented document against a documented military credential scheme.", "Extract authorised identity and affiliation assertions while preserving their source and temporal context.", "Select an appropriate verification route for the document's scheme and manifestation.", "Compare credential, holder and status evidence without collapsing their separate confidence levels.", "Assess whether a specified recipient accepts the credential for a specified purpose.", "Identify the appropriate reporting, correction or replacement process when the document is lost, damaged or inconsistent." ], "agent_conduct": { "may": [ "Read the visible fields of a military identity document presented by its holder for a stated, lawful check.", "Explain what a type of military identity document attests in general terms, from official sources." ], "must_not": [ "Produce, alter or reproduce a military identity document or anything that imitates one.", "Help a person impersonate service members or gain access to military sites.", "Store or share images or data from a holder's document beyond the check it was shown for.", "Declare a document genuine or fake without the issuing authority's verification." ], "requires_human": [ "Refusing or granting access to a facility based on a military identity document.", "Reporting a suspected forged or stolen document to authorities." ] }, "ethics": { "considerations": [ "A military credential reveals a person's status and can expose them and their family to targeting.", "In armed conflict identity documents protect captured persons and the dead under international law." ], "affected_parties": [ "Service members and veterans", "Their families", "People at sites that rely on the credential" ] }, "owners": { "steward": "The issuing military or defence authority; the holder keeps the document but does not own it.", "master_systems": [ "Military personnel records of the issuing authority" ] }, "visual_identification": [ "A card or booklet showing the holder's photograph, name, rank or status, service number and the issuing authority.", "Often carries national emblems and security features similar to other official identity documents.", "Design varies by state and period, so a sighting is settled only against the issuer's specimen." ], "failure_modes_and_hazards": [ "Forged or stolen documents enable unauthorized access to sensitive sites.", "Loss can expose the holder to identity theft or targeting." ], "standards_and_regulation": [ "Geneva Convention (III) relative to the Treatment of Prisoners of War, 1949, which requires parties to issue identity cards to persons liable to become prisoners of war." ], "what_it_is_for": [ "Military identity documents are encountered during service administration, controlled access checks and verification of military affiliation.", "They may support eligibility checks for services or benefits when the responsible authority accepts that document type.", "Their evidential value depends on the issuing authority, document category, validity and context of presentation." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q563402: military identity document", "url": "https://www.wikidata.org/wiki/Q563402", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Military identity card", "url": "https://en.wikipedia.org/wiki/Military_identity_card", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "military-credential-classification", "name": "Military credential classification", "description": "Establishes which military identification scheme the document belongs to and what kind of credential is being represented.", "rationale": "Military identification can be confused with service records, civilian credentials and access passes that make different assertions.", "layers": [ { "id": "scheme-and-authority", "name": "Scheme and authority", "description": "Connects the credential's claimed military identification role to its issuer and documented scheme.", "findings": [ { "id": "issuing-authority-and-purpose", "name": "Issuing authority and purpose", "description": "Record the claimed issuer, issuing jurisdiction and scheme-defined identification purpose, distinguishing observed markings from verified provenance.", "questions": [ { "text": "Which organisation and credential scheme are claimed to authorise this military identity document?", "kind": "provenance", "id": "issuing-authority-and-purpose-q01" }, { "text": "What does the scheme define as the document's military identification purpose?", "kind": "definition", "id": "issuing-authority-and-purpose-q02" } ] } ] }, { "id": "credential-and-manifestation", "name": "Credential and manifestation", "description": "Separates the credential type, individual issuance and presented representation.", "findings": [ { "id": "issued-credential-boundary", "name": "Issued credential boundary", "description": "Identify whether the presented object is an issued credential, a representation of one or a neighbouring military document.", "questions": [ { "text": "Is this an original physical document, native digital credential, copy or image of a particular issuance?", "kind": "boundary", "id": "issued-credential-boundary-q01" }, { "text": "What scheme evidence distinguishes it from a service record, discharge certificate, military order or standalone access pass?", "kind": "boundary", "id": "issued-credential-boundary-q02" } ] } ] } ] }, { "id": "holder-and-military-assertions", "name": "Holder and military assertions", "description": "Models who the credential identifies and the precise military relationship it asserts.", "rationale": "Identifying a holder, establishing military affiliation and establishing current service status are separate evidential tasks.", "layers": [ { "id": "holder-identification", "name": "Holder identification", "description": "Records the identity information and binding methods used by the military credential scheme.", "findings": [ { "id": "identity-fields-and-binding", "name": "Identity fields and binding", "description": "Preserve the roles of names, portraits, identifiers and any other scheme-defined binding elements without assuming every credential includes them.", "questions": [ { "text": "Which recorded elements identify the holder, and which identify only the document or personnel record?", "kind": "definition", "id": "identity-fields-and-binding-q01" }, { "text": "What authorised comparison can establish whether the presenter corresponds to the credential's holder?", "kind": "action", "id": "identity-fields-and-binding-q02" } ] } ] }, { "id": "affiliation-and-temporal-meaning", "name": "Affiliation and temporal meaning", "description": "Interprets military affiliation fields according to their scheme and reference time.", "findings": [ { "id": "military-status-assertion", "name": "Military status assertion", "description": "Record the asserted service relationship and any rank, branch or unit fields as scoped assertions, retaining uncertainty about their currency.", "questions": [ { "text": "Which holder category or military relationship does the document explicitly assert, using the issuer's terminology?", "kind": "definition", "id": "military-status-assertion-q01" }, { "text": "Do affiliation, rank or unit fields describe issuance-time facts or a status maintained through a separate authoritative record?", "kind": "provenance", "id": "military-status-assertion-q02" } ] } ] } ] }, { "id": "authenticity-and-lifecycle", "name": "Authenticity and lifecycle", "description": "Separates evidence of authentic issuance from evidence that a military credential remains valid and usable.", "rationale": "A military document can be authentic yet expired, replaced or associated with an unresolved holder mismatch.", "layers": [ { "id": "verification-evidence", "name": "Verification evidence", "description": "Records available checks and their specific conclusions for the presented credential.", "findings": [ { "id": "scheme-appropriate-checks", "name": "Scheme-appropriate checks", "description": "Associate each inspection or authorised issuer response with its method, time, result and evidential limits.", "questions": [ { "text": "Which issuer-documented checks are available for this credential type and presented manifestation?", "kind": "action", "id": "scheme-appropriate-checks-q01" }, { "text": "What did each check establish about authentic issuance, alteration, holder binding or current validity, and when?", "kind": "measurement", "id": "scheme-appropriate-checks-q02" } ] } ] }, { "id": "issuance-and-status-transitions", "name": "Issuance and status transitions", "description": "Tracks validity intervals and changes affecting a particular military credential issuance.", "findings": [ { "id": "current-credential-state", "name": "Current credential state", "description": "Record dated lifecycle evidence and relationships to replacement credentials, distinguishing printed dates from authoritative status information.", "questions": [ { "text": "What evidence establishes the effective dates and present state of this specific issuance?", "kind": "provenance", "id": "current-credential-state-q01" }, { "text": "How does the applicable scheme handle loss, damage, replacement or a change in the holder's military relationship?", "kind": "action", "id": "current-credential-state-q02" } ] } ] } ] }, { "id": "recognition-and-controlled-handling", "name": "Recognition and controlled handling", "description": "Connects presentation of the credential to a particular decision and to applicable handling requirements.", "rationale": "Military identity evidence must be interpreted within the receiving authority's rules, while military and personal information may require specific handling.", "layers": [ { "id": "purpose-specific-recognition", "name": "Purpose-specific recognition", "description": "Determines what a recipient may conclude from presentation of this military credential.", "findings": [ { "id": "recognition-and-entitlement-boundary", "name": "Recognition and entitlement boundary", "description": "Record evidence that a named authority accepts this credential for a named purpose, identifying additional requirements for any resulting permission.", "questions": [ { "text": "Which documented rule establishes acceptance of this credential by this recipient for the proposed purpose?", "kind": "provenance", "id": "recognition-and-entitlement-boundary-q01" }, { "text": "What additional evidence or authorisation is needed before granting access, benefits or another permission?", "kind": "boundary", "id": "recognition-and-entitlement-boundary-q02" } ] } ] }, { "id": "disclosure-and-custody", "name": "Disclosure and custody", "description": "Records applicable constraints on inspecting, copying, retaining and transferring the credential or its data.", "findings": [ { "id": "authorised-document-handling", "name": "Authorised document handling", "description": "Link handling decisions to applicable issuer instructions and recipient rules, with attention to personal identifiers and military affiliation information.", "questions": [ { "text": "Which applicable instructions govern inspection, copying, retention, surrender or transfer of this military identity document?", "kind": "provenance", "id": "authorised-document-handling-q01" }, { "text": "What minimum document information is necessary for the authorised task, and how should unnecessary exposure be avoided?", "kind": "action", "id": "authorised-document-handling-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 provides no sense definition; verify whether it intends only service-member credentials or also documents for other military affiliates.", "Document numbers, personnel identifiers, eligibility categories, and legal effects require issuer-specific verification.", "This is a recall-based description; no sources or current regulations were consulted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of military identity document 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": [ "Active-service identity document", "Reserve-service identity document", "Retired military identity document" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of military identity document 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": "Issuing authority's document numbering scheme", "value_or_pattern": "Authority-assigned document or card number", "note": "Identifies the credential; formats vary by issuer." }, { "scheme": "Military personnel identification scheme", "value_or_pattern": "Service number or personnel identifier", "note": "Identifies the person within a personnel system; it is not necessarily printed on every credential." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of military identity document 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": [ "Verifying the holder's identity and military affiliation", "Supporting access checks at military installations", "Demonstrating eligibility for services or benefits associated with the recorded status", "Supporting administrative transactions within military personnel systems" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of military identity document 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": [ "Loss or theft exposing personal information or enabling impersonation", "Forgery or alteration of identity and status information", "Expired or outdated credentials misrepresenting current affiliation", "Treating proof of identity as sufficient authorization for restricted access", "Damage to printed information or electronic components preventing verification" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of military identity document 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": [ "Issuers differ in whether they use cards, booklets, electronic credentials, or combinations of these.", "Eligibility and credential categories vary across active personnel, reservists, retirees, and other affiliated people.", "The information displayed and the credential's acceptance outside military administration vary by jurisdiction." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of military identity document 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": "Civilian identity document", "difference": "Establishes identity under a civilian identification system without necessarily attesting to military affiliation." }, { "name": "Military service record", "difference": "Records a person's service history rather than primarily functioning as a credential presented to verify identity." }, { "name": "Military identification tag", "difference": "A wearable identifier primarily supporting identification of personnel, including casualties, rather than a document used for routine credential checks." }, { "name": "Military access pass", "difference": "Primarily grants or records permission to enter a place; possession need not establish military status." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of military identity document this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend only credentials identifying military personnel, or also credentials for reservists, veterans, dependants and civilian defence personnel under military schemes?", "Which issuing schemes should anchor the model, and what authoritative definitions establish their document boundaries?", "Which schemes combine identification with service-history, access, benefit or other functions, and how should those extensions be represented?", "What authoritative verification routes and lifecycle rules exist for physical and digital variants in the selected schemes?", "Which scheme-specific rules govern copying, retention and disclosure, and how does recognition vary by recipient and purpose?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }