{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:45:47Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.7, "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: 01a09537-ee4f-7ec2-bed4-a9403d5a5c70\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: KhTZ-16\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 registe", "usd": 0.0, "recall": true }, "codex": { "seconds": 82.3, "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: 01a09537-ee5a-7092-9460-b6663254bea4\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: KhTZ-16\nRegistry id: vr.tr.khtz-16\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext " } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:49:29+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "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-Q2915405", "registryId": "vr.tr.khtz-16", "name": "KhTZ-16", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2915405/", "model": { "registry_id": "vr.tr.khtz-16", "name": "KhTZ-16", "purpose": "Enable an agent to identify the KhTZ-16 historical armoured-tractor design, evaluate claims about its configuration and surviving representations, and determine appropriate documentation or conservation actions.", "definition": "The KhTZ-16 was a Soviet improvised armoured fighting vehicle developed in 1941 at the Kharkov Tractor Plant, using a modified agricultural tractor chassis with an armoured superstructure and a 45 mm gun.", "scope_statement": "This model owns the design-level identity of KhTZ-16, registry entry vr.tr.khtz-16 in PHY / PHY.OBJ, including configuration evidence and criteria for assessing attributed vehicles; individual machines, components and historical events remain linked entities.", "in_scope": [ "KhTZ-16 designation, historical classification and identification criteria", "Relationship between the agricultural tractor platform and its armoured conversion", "Armoured enclosure, fixed fighting compartment and attributed weapon configuration", "Evidence-qualified mobility, protection and crew-accommodation characteristics", "Production attribution and distinctions among prototypes, production vehicles and reconstructions", "KhTZ-16-specific authenticity and conservation assessment" ], "out_of_scope": [ "Agricultural tractor families except their contribution to KhTZ-16 identification", "Other armoured tractors, including Odessa NI vehicles", "Independent models of installed engines, guns and ammunition", "Individual vehicle ownership, location and maintenance histories", "General histories of the Kharkiv factory and wartime campaigns", "Weapon operation, ammunition preparation and combat employment procedures" ], "distinguishing_features": [ "Require evidence connecting an object or depiction to KhTZ-16; a tracked tractor with added armour is insufficient.", "Compare the fixed fighting-compartment outline and gun opening with authenticated KhTZ-16 photographs rather than identifying it as a turreted tank.", "Compare running gear, engine enclosure and armour geometry together when distinguishing KhTZ-16 from NI and other tractor conversions.", "Separate the KhTZ-16 design designation from the identity of its donor tractor; conflicting chassis names require provenance checks.", "Treat museum labels, scale models and reconstructed vehicles as attribution claims rather than proof of original manufacture." ], "characteristics": [ { "name": "Designation and attribution", "kind": "category", "unit_or_values": "Recorded designation; transliteration; document date; attribution confidence", "why_it_matters": "Connects differently written names without merging unrelated vehicles bearing similar numbers." }, { "name": "Donor-platform relationship", "kind": "relation", "unit_or_values": "Named tractor design and manufacturing plant, supported by drawings or contemporary records", "why_it_matters": "Prevents conflicting tractor designations from becoming an unsupported chassis specification." }, { "name": "Configuration class", "kind": "category", "unit_or_values": "Prototype; documented production configuration; proposed configuration; reconstruction; unresolved", "why_it_matters": "Keeps features of experimental or reconstructed vehicles from defining every KhTZ-16." }, { "name": "Fighting-compartment geometry", "kind": "category", "unit_or_values": "Fixed enclosure profile, gun-opening position, hatch arrangement and observation openings", "why_it_matters": "Provides a combined visual signature for identification." }, { "name": "Attributed armament", "kind": "relation", "unit_or_values": "Weapon model, calibre in mm, mounting arrangement and configuration evidence", "why_it_matters": "Separates documented installations from proposals and later assumptions." }, { "name": "Armour construction", "kind": "measurement", "unit_or_values": "Plate thickness in mm and inclination in degrees by location; material recorded separately", "why_it_matters": "Avoids representing the entire enclosure with one unqualified armour value." }, { "name": "Mass and external envelope", "kind": "measurement", "unit_or_values": "Mass in kg; length, width and height in mm; loading state and measurement reference", "why_it_matters": "Supports comparison of drawings and attributed examples, and informs handling assessments." }, { "name": "Powertrain and mobility evidence", "kind": "relation", "unit_or_values": "Engine and fuel attribution; rated power in kW; reported speed in km/h with test conditions", "why_it_matters": "Distinguishes tractor specifications from performance of the armoured vehicle." }, { "name": "Crew accommodation", "kind": "category", "unit_or_values": "Documented crew count, stations, access routes and visibility constraints", "why_it_matters": "Tests whether reported crew arrangements match the actual enclosure." }, { "name": "Attributed-example integrity", "kind": "state", "unit_or_values": "Original; altered original; composite; reconstruction; replica; unidentified", "why_it_matters": "Determines whether an example can support claims about wartime construction." } ], "affordances": [ "Assess whether a photograph, drawing or attributed vehicle matches KhTZ-16 identification criteria.", "Compare conflicting chassis, armament and performance claims while preserving their source and configuration boundaries.", "Link an attributed vehicle to separate component, factory and historical-event records.", "Identify the archival evidence needed to distinguish prototype features from production features.", "Prepare a non-invasive documentation or conservation assessment for an attributed example.", "Flag when missing authenticity, structural or ordnance evidence prevents a handling recommendation." ], "agent_conduct": { "may": [ "Identify a surviving vehicle, replica or photograph as a KhTZ-16 from documented features.", "Describe its wartime origin and role from historical sources, stating where accounts disagree.", "Record the condition of a museum or reconstructed example for its keeper." ], "must_not": [ "Present a reconstruction or a different armoured tractor as an original KhTZ-16.", "Help restore its armament to a working state or make it able to fire.", "Start or drive a historic example without the keeper's authority and a safety check.", "Misuse its imagery to glorify war or for propaganda." ], "requires_human": [ "Moving, restoring or altering a surviving or reconstructed example.", "Attributing a specific example to a named unit or battle." ] }, "ethics": { "considerations": [ "Improvised fighting vehicles recall the desperate defence of Kharkov and the people who built and died in them.", "Accurate attribution protects museums and collectors from fakes." ], "affected_parties": [ "Museums and collectors", "Visitors near displayed vehicles", "Descendants of those who served" ] }, "owners": { "steward": "The museum or private owner of any example; the state for items in public collections.", "master_systems": [] }, "visual_identification": [ "Agricultural tractor chassis with a boxy armoured superstructure.", "A single small-calibre gun in the front of the hull rather than in a turret.", "Tractor-style tracks and running gear, much smaller than a purpose-built tank." ], "failure_modes_and_hazards": [ "Thin armour and an overloaded tractor drivetrain made it slow and vulnerable in service.", "Surviving or rebuilt hulls may have sharp edges, unstable parts and old fuel or lubricant residues.", "Any remaining or reproduced armament must be confirmed as deactivated before display." ], "what_it_is_for": [ "The KhTZ-16 is encountered in histories of Soviet emergency armoured vehicle production during the Second World War.", "It was developed to provide an improvised armoured fighting vehicle using an agricultural tractor chassis.", "Today its identification is relevant to archival research, museum interpretation and assessment of historical representations." ], "facets_not_applicable": { "interfaces": "No model-specific standard or official classification is identified here as applicable to historical identification of the KhTZ-16." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q2915405: KhTZ-16", "url": "https://www.wikidata.org/wiki/Q2915405", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: KhTZ-16", "url": "https://en.wikipedia.org/wiki/KhTZ-16", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "designation-and-recognition", "name": "Designation and recognition", "description": "Establish what the registry name denotes and how an attribution can be tested.", "rationale": "KhTZ-16 must remain distinct from its tractor platform, unrelated numbered vehicles and other improvised armoured tractors.", "layers": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Connect names to dated records without assuming that every spelling denotes the same configuration.", "findings": [ { "id": "name-to-design-boundary", "name": "Name-to-design boundary", "description": "Record original-script names, transliterations and contextual identifiers as evidence-qualified aliases.", "questions": [ { "text": "Which contemporary records explicitly identify the vehicle as KhTZ-16 or an equivalent original-script designation?", "kind": "provenance", "id": "name-to-design-boundary-q01" }, { "text": "When a source uses T-16 or HTZ-16, what establishes that it refers to this design?", "kind": "boundary", "id": "name-to-design-boundary-q02" } ] } ] }, { "id": "visual-attribution", "name": "Visual attribution", "description": "Use combinations of visible features to assess KhTZ-16 identifications.", "findings": [ { "id": "combined-recognition-signature", "name": "Combined recognition signature", "description": "Compare fighting-compartment shape, gun opening, engine enclosure and running gear against authenticated references.", "questions": [ { "text": "Which combination of visible features distinguishes KhTZ-16 from NI and other armoured tractors?", "kind": "definition", "id": "combined-recognition-signature-q01" }, { "text": "Which reference photographs have sufficiently secure captions and provenance to anchor identification?", "kind": "provenance", "id": "combined-recognition-signature-q02" } ] } ] } ] }, { "id": "tractor-conversion-and-mobility", "name": "Tractor conversion and mobility", "description": "Describe the donor-platform relationship and the effects of conversion into an armoured vehicle.", "rationale": "Agricultural tractor specifications cannot automatically serve as KhTZ-16 specifications.", "layers": [ { "id": "donor-and-modifications", "name": "Donor and modifications", "description": "Separate inherited tractor assemblies from modifications attributable to KhTZ-16.", "findings": [ { "id": "chassis-lineage-resolution", "name": "Chassis lineage resolution", "description": "Keep competing chassis labels unresolved until drawings, plant records or equivalent evidence establish their relationship.", "questions": [ { "text": "Do STZ-3 and SKhTZ-NATI references denote equivalent platform terminology, different manufacturing origins or conflicting attributions here?", "kind": "boundary", "id": "chassis-lineage-resolution-q01" }, { "text": "Which running-gear and frame changes are documented specifically for KhTZ-16?", "kind": "provenance", "id": "chassis-lineage-resolution-q02" } ] } ] }, { "id": "converted-vehicle-performance", "name": "Converted-vehicle performance", "description": "Attach powertrain and mobility values to the tested or described armoured configuration.", "findings": [ { "id": "performance-with-test-context", "name": "Performance with test context", "description": "Distinguish nominal engine ratings from measured vehicle speed, endurance and mechanical limitations.", "questions": [ { "text": "Which engine, fuel and rated-power values are documented for the armoured configuration rather than inferred from its donor?", "kind": "provenance", "id": "performance-with-test-context-q01" }, { "text": "Under what loading, terrain and test conditions were reported speed and endurance values obtained?", "kind": "measurement", "id": "performance-with-test-context-q02" }, { "text": "Which cooling, transmission or track problems are supported by KhTZ-16-specific reports?", "kind": "provenance", "id": "performance-with-test-context-q03" } ] } ] } ] }, { "id": "armoured-enclosure-and-crew", "name": "Armoured enclosure and crew", "description": "Characterise the enclosure as both a protective structure and a constrained crew space.", "rationale": "KhTZ-16 identification and assessment depend on plate layout, openings and internal accommodation together.", "layers": [ { "id": "plate-layout-and-material", "name": "Plate layout and material", "description": "Locate protection claims on specific parts of the enclosure.", "findings": [ { "id": "location-specific-armour", "name": "Location-specific armour", "description": "Record plate geometry, thickness and material evidence without inferring protection solely from appearance.", "questions": [ { "text": "What plate thicknesses and inclinations are documented for the front, sides, roof and engine enclosure?", "kind": "measurement", "id": "location-specific-armour-q01" }, { "text": "What evidence distinguishes specified armour plate from substitute material in particular builds?", "kind": "provenance", "id": "location-specific-armour-q02" } ] } ] }, { "id": "crew-stations-and-openings", "name": "Crew stations and openings", "description": "Relate crew-count claims to access, observation and occupied space.", "findings": [ { "id": "crew-layout-consistency", "name": "Crew layout consistency", "description": "Assess whether attributed crew stations and access arrangements are consistent with the documented hull.", "questions": [ { "text": "Which crew count and station arrangement are supported for each documented configuration?", "kind": "provenance", "id": "crew-layout-consistency-q01" }, { "text": "Where are the access hatches and observation openings, and what dimensions are established?", "kind": "measurement", "id": "crew-layout-consistency-q02" }, { "text": "Which visibility, ventilation or evacuation limitations were actually recorded?", "kind": "provenance", "id": "crew-layout-consistency-q03" } ] } ] } ] }, { "id": "armament-configuration", "name": "Armament configuration", "description": "Identify attributed weapon installations and their relationship to the fixed fighting compartment.", "rationale": "Weapon proposals, trials and production installations must not be collapsed into one specification.", "layers": [ { "id": "installed-versus-proposed-weapons", "name": "Installed versus proposed weapons", "description": "Classify weapon claims by their documentary status and associated configuration.", "findings": [ { "id": "weapon-attribution", "name": "Weapon attribution", "description": "Require evidence for main-gun and secondary-weapon identities rather than extrapolating from calibre or appearance.", "questions": [ { "text": "Which records establish the model and calibre of the production main gun?", "kind": "provenance", "id": "weapon-attribution-q01" }, { "text": "Which alternative-gun and machine-gun claims describe proposals, trials or completed vehicles?", "kind": "boundary", "id": "weapon-attribution-q02" } ] } ] }, { "id": "mount-and-enclosure-interface", "name": "Mount and enclosure interface", "description": "Describe the mounting arrangement as a recognition and spatial-integration feature.", "findings": [ { "id": "fixed-mount-evidence", "name": "Fixed-mount evidence", "description": "Record the gun aperture, mounting structure and compartment relationship without supplying operating procedures.", "questions": [ { "text": "Which drawings or photographs establish how the main-gun mounting occupies the fixed compartment?", "kind": "provenance", "id": "fixed-mount-evidence-q01" }, { "text": "Which enclosure features distinguish the documented mounting from a reconstruction or a different tractor conversion?", "kind": "boundary", "id": "fixed-mount-evidence-q02" } ] } ] } ] }, { "id": "production-and-historical-attribution", "name": "Production and historical attribution", "description": "Connect configuration claims to manufacturing evidence and independently attributed historical appearances.", "rationale": "Emergency production makes planned quantities, completed vehicles and battlefield identifications easy to conflate.", "layers": [ { "id": "manufacture-and-acceptance", "name": "Manufacture and acceptance", "description": "Separate orders, fabrication, completed assembly and acceptance.", "findings": [ { "id": "production-count-boundaries", "name": "Production count boundaries", "description": "Maintain distinct counts and dates for prototypes, ordered vehicles, completed vehicles and accepted deliveries.", "questions": [ { "text": "Which factories are documented as completing KhTZ-16 vehicles rather than supplying components or receiving production orders?", "kind": "provenance", "id": "production-count-boundaries-q01" }, { "text": "What does each quoted production total count, and what period does it cover?", "kind": "measurement", "id": "production-count-boundaries-q02" } ] } ] }, { "id": "service-record-linkage", "name": "Service record linkage", "description": "Use historical records to attribute vehicles without importing campaign narratives into the design model.", "findings": [ { "id": "dated-vehicle-attribution", "name": "Dated vehicle attribution", "description": "Treat unit records and dated images as links whose vehicle identification must be evaluated independently.", "questions": [ { "text": "Which dated unit records or photographs identify KhTZ-16 specifically rather than an unspecified armoured tractor?", "kind": "provenance", "id": "dated-vehicle-attribution-q01" }, { "text": "Does a reported loss or deployment concern an identifiable vehicle, an inferred group or an uncertain vehicle type?", "kind": "boundary", "id": "dated-vehicle-attribution-q02" } ] } ] } ] }, { "id": "survival-authenticity-and-conservation", "name": "Survival, authenticity and conservation", "description": "Assess present-day objects and representations attributed to KhTZ-16.", "rationale": "An exhibit or reconstruction can illustrate the design while providing limited evidence of original construction.", "layers": [ { "id": "originality-assessment", "name": "Originality assessment", "description": "Separate wartime material from later fabrication and interpretive reconstruction.", "findings": [ { "id": "surviving-example-status", "name": "Surviving-example status", "description": "Record component-level authenticity and the evidence supporting an object's KhTZ-16 attribution.", "questions": [ { "text": "Is any claimed surviving KhTZ-16 supported by a continuous provenance or documented archaeological recovery?", "kind": "provenance", "id": "surviving-example-status-q01" }, { "text": "Which components are original, substituted or newly fabricated, and which design details remain conjectural?", "kind": "boundary", "id": "surviving-example-status-q02" } ] } ] }, { "id": "documentation-and-handling", "name": "Documentation and handling", "description": "Translate authenticity and condition evidence into bounded conservation decisions.", "findings": [ { "id": "evidence-led-conservation-actions", "name": "Evidence-led conservation actions", "description": "Require an example-specific assessment before recommending movement, access or intervention.", "questions": [ { "text": "Which non-invasive measurements would resolve uncertainty about the attributed hull and running gear?", "kind": "action", "id": "evidence-led-conservation-actions-q01" }, { "text": "What structural-condition and ordnance-status evidence is needed before moving or opening this attributed example?", "kind": "action", "id": "evidence-led-conservation-actions-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, without source consultation.", "Verify the precise chassis modifications, crew complement, armour thickness and engine specifications before adding detailed technical data.", "Production totals, unit allocations and combat histories require checking; improvised Soviet armoured tractors are sometimes conflated." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of KhTZ-16 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": "Soviet vehicle model designation", "value_or_pattern": "KhTZ-16", "note": "Also written ХТЗ-16 in Cyrillic and transliterated as HTZ-16; the prefix refers to the Kharkov Tractor Plant." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of KhTZ-16 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": [ "Emergency provision of armoured fighting vehicles during the German invasion of the Soviet Union in 1941.", "Limited combat service with Soviet forces during the fighting around Kharkov." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of KhTZ-16 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": "Main gun calibre", "typical_range": "45", "unit": "mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of KhTZ-16 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": [ "Limited armour protection left the vehicle vulnerable to anti-tank weapons.", "Low speed and tractor-derived running gear restricted battlefield mobility.", "Limited gun traverse required repositioning the vehicle to engage targets outside the mounting's firing arc." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of KhTZ-16 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": [ "Kharkov and Kharkiv are Russian-derived and Ukrainian-derived renderings of the city where the vehicle was developed." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of KhTZ-16 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": "Armoured tractor", "difference": "Armoured tractor is the broader vehicle category; KhTZ-16 identifies a particular Soviet design." }, { "name": "STZ-3 agricultural tractor", "difference": "The STZ-3 was an agricultural tractor associated with the KhTZ-16's chassis ancestry; the KhTZ-16 incorporated armour and armament for combat." }, { "name": "NI-1", "difference": "The NI-1 was a separate improvised armoured tractor associated with Odessa, rather than the Kharkov KhTZ-16 design." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of KhTZ-16 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "How should conflicting donor-chassis terminology be reconciled? Preliminary search results disagree; the research article [The first with completely domestic design](https://journals.eco-vector.com/0321-4443/article/view/112160) associates KhTZ-16 with an agricultural tractor platform, but its full text was not accessible for verification.", "Which armour, engine, crew and armament specifications are established by contemporary drawings or trials, and which belong only to prototypes or later accounts?", "What production totals and manufacturing locations remain defensible after separating orders, components, completed vehicles and accepted deliveries?", "Which reported deployments and losses can be securely attributed to KhTZ-16 rather than another armoured tractor?", "Do any original vehicles or substantial authenticated components survive, and how closely do current reconstructions follow documented configurations?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 19, "questions": 33 } }