{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:35:58Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 21.2, "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: 01a094f8-3da7-7f20-a79f-4e2644ab4ffd\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: expeditionary force\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: ", "usd": 0.0, "recall": true }, "codex": { "seconds": 67.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: 01a094f8-3da2-7671-a682-6f8d22b51ae8\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: expeditionary force\nRegistry id: vr.tr.expeditionary-force\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this " } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:43:02+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-08T19:09:47+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q106823225", "registryId": "vr.tr.expeditionary-force", "name": "expeditionary force", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q106823225/", "model": { "registry_id": "vr.tr.expeditionary-force", "name": "expeditionary force", "purpose": "Enable an agent to recognise an expeditionary force, assess its readiness and deployment state, and identify decisions permitted by its mission, authority and support arrangements.", "definition": "An expeditionary force is a military force organized and deployed to conduct operations away from its home territory, with command, support, and sustainment arrangements suited to the assigned mission.", "scope_statement": "This model owns the expeditionary force as an organised military grouping constituted or assigned to deploy away from its home base for a bounded mission, including its command, composition, deployment dependencies, sustainment and transition; geographic and doctrinal thresholds remain attributable to the authority using the term.", "in_scope": [ "Force identity, constituting authority and relationship to contributing services or states", "Expeditionary designation, assigned mission and geographic or temporal limits", "Task-organised capabilities, readiness and dependencies on external support", "Deployment, reception, sustainment and recovery arrangements", "Command relationships, operating constraints and mission transition" ], "out_of_scope": [ "The campaign or military operation as a sequence of activities and outcomes", "The contributing armed forces as permanent institutions", "Individual personnel records and equipment specifications", "Detailed tactical plans, targeting decisions and weapon employment", "The host territory, transport infrastructure or supply network as independent things" ], "distinguishing_features": [ "Identify evidence that the grouping is constituted or assigned for an expeditionary mission; a unit being stationed abroad does not by itself establish this classification.", "Record the operational relationship to a home base and the movement or support needed to operate away from it; overseas location alone is an insufficient test.", "Distinguish the force, whose identity follows its command and assigned elements, from the expedition or campaign in which it participates.", "Check whether expeditionary capability is merely a standing readiness role or whether a particular force has received a deployment assignment.", "Do not infer amphibious, marine, multinational or combat-only status from the expeditionary designation; record those attributes separately." ], "characteristics": [ { "name": "Basis of expeditionary classification", "kind": "category", "unit_or_values": "Official designation; attributed doctrinal classification; analytical classification; disputed; unknown", "why_it_matters": "Separates an authority's designation from an agent's interpretation." }, { "name": "Force lifecycle state", "kind": "state", "unit_or_values": "Forming; preparing; deploying; operating; transitioning; redeploying; dissolved; unknown", "why_it_matters": "Determines which readiness, support and transition decisions are relevant." }, { "name": "Home and deployment relationship", "kind": "relation", "unit_or_values": "Links to home bases, staging locations and assigned operating areas, with effective dates", "why_it_matters": "Makes the expeditionary relationship explicit without assuming that it must cross an ocean or national border." }, { "name": "Mission and authority", "kind": "relation", "unit_or_values": "Links to assigned missions, constituting instruments, applicable mandates and authorising bodies", "why_it_matters": "Establishes why the force exists and the limits of its assignment." }, { "name": "Assigned force strength", "kind": "measurement", "unit_or_values": "Personnel count at a stated date, distinguishing authorised, assigned and deployed strength", "why_it_matters": "Prevents nominal establishment from being mistaken for personnel actually available." }, { "name": "Mission readiness", "kind": "state", "unit_or_values": "Assessed against named mission criteria, with assessor, date, limitations and reassessment trigger", "why_it_matters": "Readiness depends on the assignment and cannot be inferred solely from force size." }, { "name": "Support endurance", "kind": "measurement", "unit_or_values": "Days under stated activity, consumption, resupply and support assumptions; unknown where unassessed", "why_it_matters": "Expresses how long the deployed force can sustain its assigned activity under specified conditions." }, { "name": "Command and support dependencies", "kind": "relation", "unit_or_values": "Dated relationships to commanders, national authorities, transport providers and sustainment organisations", "why_it_matters": "Shows which decisions and capabilities depend on organisations outside the force." } ], "affordances": [ "Classify a candidate grouping as expeditionary while preserving the designation's source and unresolved boundary cases.", "Compare assigned capabilities and readiness evidence with mission requirements.", "Identify missing deployment permissions, reception arrangements or external support commitments.", "Assess whether a proposed change in mission or duration requires renewed authority, resources or readiness assessment.", "Track changes in force composition and command without confusing the force with its campaign.", "Record the conditions and responsibilities for relief, handover, redeployment or dissolution." ], "agent_conduct": { "may": [ "Describe expeditionary forces and their history from cited, public sources.", "Explain the legal framework governing deployment in general terms." ], "must_not": [ "Assist in planning military operations or targeting.", "Disclose troop locations, movements or identities beyond what is public.", "Present propaganda or unverified claims about operations as fact.", "Glorify violations of the laws of war." ], "requires_human": [ "Publishing information about ongoing operations that may endanger people." ] }, "ethics": { "considerations": [ "Deployments abroad affect civilians in the host country and the troops sent.", "Accountability for conduct abroad depends on accurate reporting." ], "affected_parties": [ "Civilians in operational areas", "Service members", "Their families" ] }, "owners": { "steward": "The state that raises and deploys it, under its constitutional authority.", "master_systems": [] }, "visual_identification": [ "Units deployed abroad with the uniforms, vehicles and insignia of the sending state.", "Often supported by visible logistics such as transport ships, aircraft and bases." ], "failure_modes_and_hazards": [ "Operations abroad can cause civilian harm.", "Leaked operational information endangers personnel." ], "standards_and_regulation": [ "Geneva Conventions of 1949 and their Additional Protocols, with the International Committee of the Red Cross as custodian." ], "what_it_is_for": [ "An expeditionary force is encountered in military deployments conducted away from home territory under a defined mission and command structure.", "It combines operational units with transport, logistics and other support needed for missions such as combat, evacuation, peace support or disaster assistance.", "Its organization depends on the deployment environment, available host support and expected duration." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q106823225: expeditionary force", "url": "https://www.wikidata.org/wiki/Q106823225", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-de", "title": "Wikipedia (de): Expeditionsstreitkräfte", "url": "https://de.wikipedia.org/wiki/Expeditionsstreitkr%C3%A4fte", "url_status": "live", "checked_by": "wikidata-api sitelink", "what_it_supports": "general description of the item" } ], "structure": { "bundles": [ { "id": "force-identity-and-boundaries", "name": "Force identity and boundaries", "description": "Establishes what grouping the record represents and why it is treated as expeditionary.", "rationale": "An expeditionary name, an overseas posting and an expeditionary capability can describe different things.", "layers": [ { "id": "designation-and-constitution", "name": "Designation and constitution", "description": "Records the basis for recognising and naming the force.", "findings": [ { "id": "expeditionary-status-basis", "name": "Expeditionary status basis", "description": "Record who identifies the grouping as an expeditionary force, the definition used and the instrument or evidence supporting that identification.", "questions": [ { "text": "Which authority or source calls this grouping an expeditionary force, and under what definition?", "kind": "provenance", "id": "expeditionary-status-basis-q01" }, { "text": "Is the designation a standing organisational title, a mission-specific assignment or a later analytical description?", "kind": "definition", "id": "expeditionary-status-basis-q02" } ] } ] }, { "id": "continuity-and-membership", "name": "Continuity and membership", "description": "Separates the force's continuing identity from changes in its constituent units.", "findings": [ { "id": "force-identity-through-change", "name": "Force identity through change", "description": "Record which headquarters, formation decisions and membership changes establish continuity or create a successor force.", "questions": [ { "text": "Which headquarters and assigned elements belong to this force at the date being assessed?", "kind": "boundary", "id": "force-identity-through-change-q01" }, { "text": "Does a rotation, redesignation or change of commander preserve this force's identity or establish a successor?", "kind": "boundary", "id": "force-identity-through-change-q02" } ] } ] } ] }, { "id": "mission-authority-and-command", "name": "Mission, authority and command", "description": "Connects the force's assignment to the authorities and command relationships governing it.", "rationale": "An expeditionary force may operate away from its national support structure while remaining subject to several distinct sources of direction and constraint.", "layers": [ { "id": "assignment-and-permissions", "name": "Assignment and permissions", "description": "Records mission limits and the applicable basis for deployment and presence.", "findings": [ { "id": "bounded-mission", "name": "Bounded mission", "description": "Record assigned purposes, operating areas, duration or review conditions, and permissions or contested authority relevant to deployment.", "questions": [ { "text": "What mission, area and termination or review conditions has the assigning authority specified?", "kind": "definition", "id": "bounded-mission-q01" }, { "text": "Which authorisations, access agreements or other asserted bases support the force's deployment and presence, and which are disputed?", "kind": "provenance", "id": "bounded-mission-q02" }, { "text": "Which proposed changes would require a new assignment or renewed permission?", "kind": "action", "id": "bounded-mission-q03" } ] } ] }, { "id": "distributed-command", "name": "Distributed command", "description": "Distinguishes operational direction from retained national, administrative and support responsibilities.", "findings": [ { "id": "command-transfer-and-reservations", "name": "Command transfer and reservations", "description": "Record the authority exercised over each contingent or component, including effective dates and retained restrictions.", "questions": [ { "text": "Who may assign tasks to each component, and which responsibilities remain with its contributing authority?", "kind": "boundary", "id": "command-transfer-and-reservations-q01" }, { "text": "What documented restrictions or approval requirements limit the expeditionary commander's use of assigned elements?", "kind": "action", "id": "command-transfer-and-reservations-q02" } ] } ] } ] }, { "id": "composition-and-expeditionary-readiness", "name": "Composition and expeditionary readiness", "description": "Describes the force package and whether it can perform its assignment after deployment.", "rationale": "Available personnel and equipment do not by themselves establish that a force can move, integrate and function away from home support.", "layers": [ { "id": "mission-capability-package", "name": "Mission capability package", "description": "Relates assigned components and enabling support to mission requirements.", "findings": [ { "id": "organic-and-provided-capabilities", "name": "Organic and provided capabilities", "description": "Distinguish capabilities within the force from those promised by higher commands, partners, contractors or hosts.", "questions": [ { "text": "Which capabilities required by the mission are assigned to the force, and which must be provided externally?", "kind": "boundary", "id": "organic-and-provided-capabilities-q01" }, { "text": "What evidence confirms that externally provided capabilities will be available for the required period?", "kind": "provenance", "id": "organic-and-provided-capabilities-q02" } ] } ] }, { "id": "deployment-specific-readiness", "name": "Deployment-specific readiness", "description": "Assesses preparation for the intended deployment conditions and component integration.", "findings": [ { "id": "readiness-evidence-and-gaps", "name": "Readiness evidence and gaps", "description": "Record dated assessments of personnel availability, equipment serviceability, preparation and interoperability against the assigned mission.", "questions": [ { "text": "What mission-specific readiness criteria have been assessed, by whom and on what date?", "kind": "measurement", "id": "readiness-evidence-and-gaps-q01" }, { "text": "Which unresolved preparation or interoperability gaps constrain deployment or require reassessment?", "kind": "action", "id": "readiness-evidence-and-gaps-q02" } ] } ] } ] }, { "id": "deployment-and-sustainment", "name": "Deployment and sustainment", "description": "Records the dependencies that allow the force to arrive, become operational and remain supported away from its home bases.", "rationale": "Movement and continued support are defining practical constraints on an expeditionary assignment.", "layers": [ { "id": "movement-and-reception", "name": "Movement and reception", "description": "Tracks deployment feasibility and readiness to receive the force.", "findings": [ { "id": "arrival-to-operational-availability", "name": "Arrival to operational availability", "description": "Distinguish permission to move, transport availability, physical arrival and readiness to undertake the mission.", "questions": [ { "text": "Which transport commitments, transit permissions and reception arrangements remain prerequisites for deployment?", "kind": "action", "id": "arrival-to-operational-availability-q01" }, { "text": "What criteria distinguish an element's arrival from its availability for assigned duties?", "kind": "measurement", "id": "arrival-to-operational-availability-q02" } ] } ] }, { "id": "support-and-endurance", "name": "Support and endurance", "description": "Makes resupply and deployed support assumptions explicit.", "findings": [ { "id": "sustainment-dependency-envelope", "name": "Sustainment dependency envelope", "description": "Record support endurance and dependencies for supply, maintenance, medical care, personnel replacement and other mission-relevant services.", "questions": [ { "text": "How long can the force sustain its assigned activity under the stated consumption and resupply assumptions?", "kind": "measurement", "id": "sustainment-dependency-envelope-q01" }, { "text": "Which support services depend on home bases, host arrangements or third parties, and what limits apply to those commitments?", "kind": "boundary", "id": "sustainment-dependency-envelope-q02" }, { "text": "What changes in support availability require the force's mission or duration to be reviewed?", "kind": "action", "id": "sustainment-dependency-envelope-q03" } ] } ] } ] }, { "id": "deployment-state-and-transition", "name": "Deployment state and transition", "description": "Tracks the force's actual status and the conditions for changing or ending its assignment.", "rationale": "A deployed force may rotate, transfer responsibilities or return home without the wider campaign ending.", "layers": [ { "id": "current-state-and-review", "name": "Current state and review", "description": "Separates the force's current availability from the progress of the operation it supports.", "findings": [ { "id": "dated-force-state", "name": "Dated force state", "description": "Record lifecycle state, deployed composition and material limitations as dated assessments.", "questions": [ { "text": "Which elements are preparing, moving, available for duty or returning at the assessment date?", "kind": "measurement", "id": "dated-force-state-q01" }, { "text": "Which changes in mission, composition or support trigger a formal review of the force's assignment?", "kind": "action", "id": "dated-force-state-q02" } ] } ] }, { "id": "relief-and-redeployment", "name": "Relief and redeployment", "description": "Defines force-level handover, recovery and closure responsibilities.", "findings": [ { "id": "transition-completion", "name": "Transition completion", "description": "Record conditions for relief, transfer of responsibilities, return or reassignment of elements, and formal dissolution where applicable.", "questions": [ { "text": "Who authorises relief or redeployment, and what responsibilities must be accepted by a successor or host?", "kind": "action", "id": "transition-completion-q01" }, { "text": "What evidence establishes that personnel, equipment and outstanding support obligations have been accounted for?", "kind": "provenance", "id": "transition-completion-q02" }, { "text": "Does completion end this force's existence, return it to standing readiness or continue it under another assignment?", "kind": "boundary", "id": "transition-completion-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes a military organization or grouping, rather than an abstract activity; the registry's intended classification should be checked.", "The listed kinds overlap and are descriptive distinctions, not a universal formal taxonomy.", "Recall only: exact doctrinal definitions and named formations' current organization require verification; no universal size, readiness threshold, or dedicated identifier is asserted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of expeditionary force 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": [ "Land expeditionary force", "Naval expeditionary force", "Amphibious expeditionary force", "Air expeditionary force", "Joint expeditionary force", "Multinational expeditionary force" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of expeditionary force 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": [ "Conducting overseas military campaigns.", "Reinforcing allies or supporting coalition operations.", "Evacuating nationals from overseas crises.", "Providing military support for humanitarian assistance and disaster relief.", "Conducting peace support or stabilization operations." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of expeditionary force 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": "Personnel strength", "typical_range": "No defining range; depends on mission and force composition.", "unit": "personnel" }, { "quantity": "Deployment readiness time", "typical_range": "Specified for the particular force and readiness posture.", "unit": "hours or days" }, { "quantity": "Sustainment endurance before replenishment", "typical_range": "Depends on consumption, carried supplies, and operational conditions.", "unit": "days" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of expeditionary force 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": [ "Extended supply lines and dependence on vulnerable ports, airfields, or transport routes.", "Insufficient transport capacity or denied access delaying deployment and reinforcement.", "Inadequate medical support, evacuation capacity, or environmental preparation.", "Command and interoperability failures among services or coalition partners.", "Mission expansion exceeding available forces and sustainment capacity." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of expeditionary force 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": [ "United States Marine Corps usage includes Marine Expeditionary Forces and smaller expeditionary formations; these are specific organizational categories.", "British historical usage includes the British Expeditionary Force, while the UK-led Joint Expeditionary Force is a named multinational framework.", "Across national doctrines, 'expeditionary' may emphasize overseas deployment, rapid response, or operating with limited established support; these emphases are not identical." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of expeditionary force 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": "Expedition", "difference": "An expedition is an undertaking or journey; an expeditionary force is the military organization conducting operations." }, { "name": "Task force", "difference": "A task force is organized for a specific task and need not operate away from home territory." }, { "name": "Rapid reaction force", "difference": "Rapid reaction describes readiness and response speed; expeditionary describes the deployment and operating context." }, { "name": "Amphibious force", "difference": "An amphibious force is organized for operations involving movement from sea to shore; expeditionary forces need not be amphibious." }, { "name": "Occupation force", "difference": "Occupation concerns exercising authority over foreign territory; an expeditionary force can have missions that do not involve occupation." }, { "name": "Overseas garrison", "difference": "An overseas garrison is stationed to hold or support a location; foreign stationing alone does not make it an expeditionary force." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of expeditionary force this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which doctrinal and historical definitions require foreign or overseas deployment, and which admit operations elsewhere within the contributing state's territory?", "How should a permanently named expeditionary formation be distinguished from the mission-specific force it generates?", "What minimum organisational cohesion distinguishes an expeditionary force from several independently deployed contingents?", "How much independent sustainment, if any, is required by particular definitions rather than merely desirable for a specific mission?", "Does an existing Vercy world model already own this concept, requiring the registry entry to link to it rather than receive a separate publication?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 30 } }