{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:20:29Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 15.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-f169-7d80-b31e-f20b422c249f\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mingghan\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: 1001 regist", "usd": 0.0, "recall": true }, "codex": { "seconds": 65.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: 01a09557-f168-7263-8f72-47400997a64a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Mingghan\nRegistry id: vr.tr.mingghan\nPlane / domain: SOC / SOC.ORG\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContex" } }, "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" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:29+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q2640414", "registryId": "vr.tr.mingghan", "name": "Mingghan", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "SOC.ORG" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2640414/", "model": { "registry_id": "vr.tr.mingghan", "name": "Mingghan", "purpose": "Enable an agent to recognise a Mingghan, assess its documented military and administrative organisation, and distinguish nominal establishment from actual people, obligations and command.", "definition": "A mingghan was a military-administrative unit in the Mongol decimal system, nominally comprising one thousand soldiers and associated with the population responsible for supplying them.", "scope_statement": "This model owns the Mingghan as a Mongol decimal military-administrative unit conventionally associated with a thousand, including its constituent population, command relationships and historically specific continuity; registry identity is vr.tr.mingghan in SOC / SOC.ORG.", "in_scope": [ "Identification of a documented Mingghan within a particular period and polity", "Nominal decimal establishment and separately evidenced household and troop counts", "Constituent subdivisions and higher command attachments", "Command appointments, subordinate authority and dependent population", "Military service, administrative obligations and organisational change" ], "out_of_scope": [ "The Mongol Empire's entire governmental and military system", "The personal biography of a Mingghan commander", "Individual soldiers, households, horses and equipment as independent entities", "Campaigns and battles in which a Mingghan participated", "Other decimal institutions whose equivalence to a Mingghan has not been established" ], "distinguishing_features": [ "Identification requires evidence of a Mongol organisational thousand, rather than merely a group counted as one thousand.", "The unit must be distinguished from its commander: a person commanding a thousand is not the organisation itself.", "Its decimal level differs from a hundred-level subdivision and a ten-thousand-level formation; actual attachments require evidence.", "A reported strength below or above one thousand does not by itself disqualify an otherwise attested Mingghan.", "A household-based administrative constituency and a deployed troop contingent must be distinguishable even where they belong to the same unit." ], "characteristics": [ { "name": "Attested designation", "kind": "category", "unit_or_values": "Source spelling, transliteration, translated designation and named unit identifier", "why_it_matters": "Separates terminology variants from distinct organisations and commander titles." }, { "name": "Historical setting", "kind": "relation", "unit_or_values": "Polity, ruler, region and dated interval", "why_it_matters": "Prevents arrangements from one period or jurisdiction being imposed on another." }, { "name": "Nominal establishment", "kind": "measurement", "unit_or_values": "Conventional thousand-level designation; specify whether a source describes troops, households or another basis", "why_it_matters": "Preserves the organising number without treating it as a census." }, { "name": "Recorded population and strength", "kind": "measurement", "unit_or_values": "Separately dated counts of assigned households, liable personnel and deployed troops, with uncertainty", "why_it_matters": "These quantities answer different questions and must not be substituted for one another." }, { "name": "Decimal composition", "kind": "relation", "unit_or_values": "Attested hundred-level subdivisions and higher formations, with dates", "why_it_matters": "Allows comparison of the decimal ideal with documented organisation." }, { "name": "Command authority", "kind": "relation", "unit_or_values": "Commander, appointing authority, superior and evidenced powers", "why_it_matters": "Identifies who could command, administer or reorganise the unit." }, { "name": "Obligation profile", "kind": "category", "unit_or_values": "Attested military, provisioning, fiscal or labour obligations; unknown where unestablished", "why_it_matters": "Shows what membership entailed without assuming a universal service regime." }, { "name": "Organisational status", "kind": "state", "unit_or_values": "Attested functioning, reorganised, divided, amalgamated, terminated or uncertain", "why_it_matters": "Distinguishes documented institutional change from gaps in surviving records." } ], "affordances": [ "Classify a historical reference as a Mingghan unit, commander title, numerical expression or uncertain identification.", "Reconstruct dated command and subdivision relationships.", "Compare nominal establishment with household assignments and deployed strength.", "Trace changes in membership, obligations and superior authority.", "Evaluate whether two references describe the same continuing unit.", "Flag unsupported equivalences and request the evidence needed to resolve them." ], "agent_conduct": { "may": [ "Describe the mingghan and the Mongol decimal system from historical sources.", "Explain how units of one thousand linked military service to supporting households." ], "must_not": [ "Present nominal unit strengths as exact historical numbers.", "Glorify conquest violence or erase the suffering of conquered peoples.", "Confuse it with later units of similar names without explaining the difference." ], "requires_human": [ "Publishing reconstructions of disputed historical figures as fact." ] }, "ethics": { "considerations": [ "Accounts of Mongol history affect national identity in Mongolia and across Eurasia.", "Conquests brought mass killing that deserves honest recognition." ], "affected_parties": [ "Historians and readers", "Mongolian and Central Asian communities", "Descendants of conquered peoples" ] }, "owners": { "steward": "Nobody: a historical institution.", "master_systems": [] }, "failure_modes_and_hazards": [ "Taking nominal unit sizes literally distorts estimates of army sizes." ], "what_it_is_for": [ "A mingghan is encountered in historical accounts of Mongol military organisation and imperial administration.", "It describes a unit within a decimal hierarchy that connected military command with obligations imposed on supporting populations.", "Historical analysis uses the term to examine command, mobilisation and social organisation while distinguishing nominal strength from actual personnel." ], "facets_not_applicable": { "interfaces": "This historical unit has no applicable modern standard, and its particular obligations require evidence from the relevant period and polity.", "recognition": "A historical military-administrative unit cannot be identified by visual appearance or an apparent headcount alone." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q2640414: Mingghan", "url": "https://www.wikidata.org/wiki/Q2640414", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Mingghan", "url": "https://en.wikipedia.org/wiki/Mingghan", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "historical-identification", "name": "Historical identification", "description": "Establish which organisational thousand a reference denotes and the limits of that identification.", "rationale": "A translated numerical label alone cannot establish a Mingghan's identity or institutional form.", "layers": [ { "id": "designation-and-referent", "name": "Designation and referent", "description": "Separate the organisation from its name, numerical meaning and command office.", "findings": [ { "id": "unit-identification", "name": "Unit identification", "description": "Record the original expression and evidence that it denotes a military-administrative unit rather than a person or a count.", "questions": [ { "text": "What expression does the source use, and does its context identify an organisation, a commander or a numerical quantity?", "kind": "definition", "id": "unit-identification-q01" }, { "text": "Which passage supports mapping this reference to vr.tr.mingghan?", "kind": "provenance", "id": "unit-identification-q02" } ] } ] }, { "id": "period-and-institutional-boundary", "name": "Period and institutional boundary", "description": "Anchor interpretation to the relevant polity and historical interval.", "findings": [ { "id": "contextual-equivalence", "name": "Contextual equivalence", "description": "Treat similarly translated decimal institutions as comparison candidates until their relationship is established.", "questions": [ { "text": "Under which ruler, polity and dated institutional arrangement is this Mingghan attested?", "kind": "provenance", "id": "contextual-equivalence-q01" }, { "text": "Does a proposed equivalent denote the same institution, a successor form or only another organisation called a thousand?", "kind": "boundary", "id": "contextual-equivalence-q02" } ] } ] } ] }, { "id": "decimal-establishment-and-strength", "name": "Decimal establishment and strength", "description": "Represent the thousand-level ideal separately from counted membership and field strength.", "rationale": "Historical synthesis explicitly distinguishes theoretical establishment from variable actual strength. See [The Cambridge History of the Mongol Empire](https://api.pageplace.de/preview/DT0400.9781009301985_A49234927/preview-9781009301985_A49234927.pdf).", "layers": [ { "id": "establishment-and-subdivision", "name": "Establishment and subdivision", "description": "Record the stated decimal arrangement and its evidenced implementation.", "findings": [ { "id": "documented-decimal-composition", "name": "Documented decimal composition", "description": "Distinguish an expected arrangement of hundreds from named or enumerated constituent units.", "questions": [ { "text": "What subdivisions are actually attested, and which are inferred only from the decimal ideal?", "kind": "measurement", "id": "documented-decimal-composition-q01" }, { "text": "Which higher formation, if any, contained this Mingghan at the date being modelled?", "kind": "boundary", "id": "documented-decimal-composition-q02" } ] } ] }, { "id": "households-and-fielded-personnel", "name": "Households and fielded personnel", "description": "Keep administrative membership, service liability and mobilisation counts distinct.", "findings": [ { "id": "count-basis-and-date", "name": "Count basis and date", "description": "Every strength figure requires a counted population, date and evidential basis; missing troop figures must not be calculated automatically from households.", "questions": [ { "text": "Does each reported number count households, assigned servicemen, available fighters or troops deployed on a particular occasion?", "kind": "measurement", "id": "count-basis-and-date-q01" }, { "text": "What dated evidence supports the number, and is it an establishment figure, enumeration or estimate?", "kind": "provenance", "id": "count-basis-and-date-q02" } ] } ] } ] }, { "id": "command-and-dependent-population", "name": "Command and dependent population", "description": "Model who exercised authority over the Mingghan and how its constituent people were attached to it.", "rationale": "Command appointments and population organisation are necessary to understand a Mingghan beyond its nominal size.", "layers": [ { "id": "appointment-and-command", "name": "Appointment and command", "description": "Record command holders, superior authorities and the scope of each appointment.", "findings": [ { "id": "command-tenure-and-powers", "name": "Command tenure and powers", "description": "Separate a commander's identity and tenure from the unit's identity, and distinguish attested authority from assumed powers.", "questions": [ { "text": "Who commanded this Mingghan, during which interval, and through whose appointment or recognition?", "kind": "provenance", "id": "command-tenure-and-powers-q01" }, { "text": "What evidence establishes the commander's powers over mobilisation, subordinate appointments and household administration?", "kind": "action", "id": "command-tenure-and-powers-q02" } ] } ] }, { "id": "population-attachment", "name": "Population attachment", "description": "Represent household assignment and affiliation without equating the unit automatically with a kinship group.", "findings": [ { "id": "membership-and-transfer", "name": "Membership and transfer", "description": "Record how people belonged to the unit and which movements or reassignments are evidenced.", "questions": [ { "text": "What identifies the households or groups assigned to this Mingghan, and how does that assignment relate to earlier affiliations?", "kind": "boundary", "id": "membership-and-transfer-q01" }, { "text": "What source establishes whether members could transfer, who could authorise transfer and whether a recorded transfer occurred?", "kind": "action", "id": "membership-and-transfer-q02" } ] } ] } ] }, { "id": "obligations-and-organisational-continuity", "name": "Obligations and organisational continuity", "description": "Track the unit's documented duties and persistence through changes in command, population and attachment.", "rationale": "An agent needs to judge what a particular Mingghan was required to provide and whether later references identify its continuation.", "layers": [ { "id": "service-and-support", "name": "Service and support", "description": "Describe military and administrative obligations at the level supported by local historical evidence.", "findings": [ { "id": "attested-obligation-regime", "name": "Attested obligation regime", "description": "Separate duties imposed on the unit from contributions attributed to individual households and from service actually delivered.", "questions": [ { "text": "Which military, provisioning, fiscal or labour duties are explicitly attributed to this Mingghan and its constituent households?", "kind": "definition", "id": "attested-obligation-regime-q01" }, { "text": "What evidence distinguishes an ordered contribution from resources or personnel actually supplied?", "kind": "measurement", "id": "attested-obligation-regime-q02" } ] } ] }, { "id": "reorganisation-and-persistence", "name": "Reorganisation and persistence", "description": "Assess continuity when rulers, commanders, constituents or higher attachments change.", "findings": [ { "id": "continuity-decision", "name": "Continuity decision", "description": "Make same-unit judgements explicit and preserve uncertainty where names or command succession are insufficient.", "questions": [ { "text": "Does a later reference preserve this unit's identity, describe a division or amalgamation, or reuse a name for a different formation?", "kind": "boundary", "id": "continuity-decision-q01" }, { "text": "What evidence permits linking the records, and which unresolved discontinuities require keeping them separate?", "kind": "action", "id": "continuity-decision-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": [ "This account is recalled knowledge; no sources were consulted.", "A researcher should verify the relationship between troop strength, households and administrative population for the particular period and territory.", "The decimal figures describe nominal organization; actual strengths and the persistence of subdivisions require historical evidence." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Mingghan 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": [ "Organizing military recruitment, command and mobilization in the Mongol Empire.", "Assigning populations and their military obligations to designated commanders.", "Organizing forces within larger units nominally numbering ten thousand." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Mingghan 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 military strength", "typical_range": "1000", "unit": "soldiers" }, { "quantity": "Nominal constituent hundred-man units", "typical_range": "10", "unit": "jaghun" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Mingghan 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 nominal strength as an actual troop count can misrepresent forces available for a campaign.", "Equating soldiers, households and the associated population can produce incorrect estimates of a unit's size." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Mingghan 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": "Jaghun", "difference": "A nominal hundred-man unit, one level below a mingghan in the decimal hierarchy." }, { "name": "Tumen", "difference": "A nominal ten-thousand-man unit, one level above a mingghan." }, { "name": "Arban", "difference": "A nominal ten-man unit at the base of the decimal military hierarchy." }, { "name": "Mingghan commander", "difference": "The officeholder exercising authority over the unit, rather than the unit itself." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Mingghan this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Across which periods and polities should this registry entry encompass later institutions called Mingghan, and where does institutional equivalence cease?", "How do contemporary sources distinguish a thousand households, a thousand service obligations and a nominal thousand troops?", "How consistently were hundred-level subdivisions and higher decimal attachments implemented in documented Mingghans?", "Which appointment, succession, membership-transfer and administrative rules varied by ruler, region or period?", "What evidence can establish continuity of a particular Mingghan through redistribution, conquest or changes of commander?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 13, "questions": 21 } }