{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:39:01Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 29.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: 01a09531-cc9b-71e0-a16a-0bf6b463f241\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Ivan Rogov-class landing ship\nSense to describe: (none recorded)\nDomain code: PHY.LIV\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# B", "usd": 0.0, "recall": true }, "codex": { "seconds": 78.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: 01a09531-cca8-7ec0-a319-f964bc3e8469\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Ivan Rogov-class landing ship\nRegistry id: vr.tr.ivan-rogov-class-landing-ship\nPlane / domain: PHY / PHY.LIV\nRegistry definition: (none recorded)\nNam" } }, "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", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:25+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1285148", "registryId": "vr.tr.ivan-rogov-class-landing-ship", "name": "Ivan Rogov-class landing ship", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.LIV" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1285148/", "model": { "registry_id": "vr.tr.ivan-rogov-class-landing-ship", "name": "Ivan Rogov-class landing ship", "purpose": "Enable an agent to recognize the Ivan Rogov-class landing ship, distinguish class capabilities from individual hull condition, and assess documented transport, maintenance and preservation options.", "definition": "The Ivan Rogov class, designated Project 1174 Nosorog, is a Soviet-designed class of large amphibious landing ships combining vehicle and troop transport with landing-craft docking facilities and helicopter operations.", "scope_statement": "This model owns the class-level identity, configuration boundaries and capability-assessment requirements of registry entry vr.tr.ivan-rogov-class-landing-ship, provisionally identified as Soviet Project 1174; individual ships supply dated instances of its characteristics.", "in_scope": [ "Project 1174 identity, aliases and class-membership evidence", "Combined vehicle transport, landing-craft docking and helicopter-support architecture", "Configuration-dependent personnel, vehicle and cargo accommodation", "Hull-specific equipment differences and modifications", "Dated condition, service status and evidence required before asserting usability" ], "out_of_scope": [ "Project 23900 amphibious assault ships sharing the Ivan Rogov name", "Individual ship biographies beyond their relevance to class membership and configuration", "Independent models of embarked helicopters, landing craft and vehicles", "Amphibious assault tactics, targeting and weapons employment", "Fleet command structures and naval procurement policy" ], "distinguishing_features": [ "Require a Project 1174 identifier rather than accepting the Ivan Rogov name alone; the registry title is associated with that project. [Wikidata entry](https://www.wikidata.org/wiki/Q1285148)", "Test for the combination of direct bow-ramp unloading and an internal well deck for landing craft, rather than identifying the class from a bow ramp alone. [Naval Postgraduate School study](https://calhoun.nps.edu/server/api/core/bitstreams/5bd5d483-e329-4480-8a55-2ee61b088a40/content)", "Check for helicopter-support facilities alongside the landing-craft function; the historical design is described as accommodating four medium helicopters. [Naval Postgraduate School study](https://calhoun.nps.edu/server/api/core/bitstreams/5bd5d483-e329-4480-8a55-2ee61b088a40/content)", "Treat the class as a design shared by member hulls, rather than equating it with the individual ship named Ivan Rogov." ], "characteristics": [ { "name": "Project identity", "kind": "category", "unit_or_values": "Project 1174; conflicting attribution; unresolved", "why_it_matters": "Prevents same-name Project 23900 records from contaminating this class." }, { "name": "Hull and configuration reference", "kind": "relation", "unit_or_values": "Member hull identifier, configuration date and supporting record", "why_it_matters": "Equipment and condition claims must apply to an identifiable ship and period." }, { "name": "Displacement basis", "kind": "measurement", "unit_or_values": "Tonnes, explicitly labelled standard, full-load or observed", "why_it_matters": "Displacement figures cannot be compared without their loading convention." }, { "name": "Loaded draught", "kind": "measurement", "unit_or_values": "Metres, with loading and trim conditions", "why_it_matters": "Constrains access to berths and unloading interfaces." }, { "name": "Vehicle and cargo accommodation", "kind": "measurement", "unit_or_values": "Cargo tonnes, usable deck area in square metres, and vehicle counts by identified type", "why_it_matters": "Vehicle counts are meaningful only for a specified load arrangement." }, { "name": "Personnel accommodation", "kind": "measurement", "unit_or_values": "Persons, separating ship crew, embarked personnel and temporary overload", "why_it_matters": "Avoids interpreting short-duration embarkation figures as sustained accommodation." }, { "name": "Well-deck compatibility", "kind": "relation", "unit_or_values": "Landing-craft type linked to documented fit, capacity and configuration", "why_it_matters": "A nominal craft count does not establish compatibility with every landing craft." }, { "name": "Helicopter-support envelope", "kind": "relation", "unit_or_values": "Aircraft type linked separately to landing, stowage and maintenance support", "why_it_matters": "Landing permission, carriage and sustained support are different capabilities." }, { "name": "Transfer-system condition", "kind": "state", "unit_or_values": "Bow ramp, doors and well-deck systems: verified usable, restricted, unavailable or unknown", "why_it_matters": "Design features do not prove that a particular hull can currently use them." }, { "name": "Hull disposition", "kind": "state", "unit_or_values": "Commissioned, reserve, decommissioned, awaiting disposal, dismantled or unresolved; dated", "why_it_matters": "Prevents historical class specifications from implying present availability." } ], "affordances": [ "Disambiguate a ship record or photograph using project identity and documented configuration.", "Compare proposed cargo arrangements against sourced accommodation and interface limits.", "Identify whether a dated configuration supports direct unloading, landing-craft carriage or helicopter support.", "Separate original design capability from inspected condition and authorized use.", "Flag missing evidence before recommending maintenance, towing, access or preservation work." ], "agent_conduct": { "may": [ "Identify ships of this class from published records and distinctive features.", "Report the service history and status of individual hulls from official and reliable sources.", "Distinguish class design data from the condition of a particular ship." ], "must_not": [ "Assist in targeting, tracking or attacking a ship or the people on board.", "Present uncertain or contested claims about a ship's location or fate as fact.", "Spread fabricated imagery or reports about naval operations.", "Disclose non-public operational details obtained without authority." ], "requires_human": [ "Publishing the position or movements of a military vessel in an ongoing conflict.", "Attributing a specific incident or loss to a named hull." ] }, "ethics": { "considerations": [ "Landing ships carry troops and vehicles; information about them can affect lives in conflict.", "Misinformation about warships can inflame tensions between states." ], "affected_parties": [ "Crews and embarked troops", "Civilians in coastal areas", "People affected by naval operations" ] }, "owners": { "steward": "The navy of the operating state for each ship; the builder held the design.", "master_systems": [ "Naval vessel registers of the operating state" ] }, "visual_identification": [ "Large amphibious ship with a bow door and ramp and a stern docking well.", "Raised superstructure with a helicopter deck and hangar.", "Hull number and name settle which ship of the class it is." ], "failure_modes_and_hazards": [ "Docking wells and bow doors bring flooding and stability risks if seals fail.", "Stored fuel, munitions and vehicles create fire and explosion risks on board.", "Decommissioned hulls may hold hazardous materials during scrapping." ], "standards_and_regulation": [ "Convention on the International Regulations for Preventing Collisions at Sea (COLREGs), International Maritime Organization." ], "what_it_is_for": [ "The Ivan Rogov class was developed for Soviet naval amphibious operations involving troops, vehicles, landing craft and helicopters.", "It is encountered in naval histories, ship recognition references and records concerning individual vessels and their service condition." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1285148: Ivan Rogov-class landing ship", "url": "https://www.wikidata.org/wiki/Q1285148", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Ivan Rogov-class landing ship", "url": "https://en.wikipedia.org/wiki/Ivan_Rogov-class_landing_ship", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "project-and-hull-identity", "name": "Project and hull identity", "description": "Establish which design and member ships the Ivan Rogov-class label denotes.", "rationale": "Reused ship names and inconsistent classification labels can merge unrelated projects.", "layers": [ { "id": "project-boundary", "name": "Project boundary", "description": "Resolve the registry label against project identifiers and neighbouring classes.", "findings": [ { "id": "project-number-controls-identity", "name": "Project number controls identity", "description": "Use Project 1174 as the working identity and require explicit evidence for any competing attribution.", "questions": [ { "text": "Which registry-linked record establishes that this entry denotes Project 1174?", "kind": "provenance", "id": "project-number-controls-identity-q01" }, { "text": "Does any associated record actually describe Project 23900 or another ship named Ivan Rogov?", "kind": "boundary", "id": "project-number-controls-identity-q02" } ] } ] }, { "id": "member-hull-attribution", "name": "Member hull attribution", "description": "Connect class assertions to identifiable hulls without treating every hull as identical.", "findings": [ { "id": "membership-and-configuration", "name": "Membership and configuration", "description": "Record hull identity, naming history and the period to which a configuration claim applies.", "questions": [ { "text": "Which construction or naval records establish each hull's membership in Project 1174?", "kind": "provenance", "id": "membership-and-configuration-q01" }, { "text": "Is the described feature common to the class, specific to one hull or introduced by a later modification?", "kind": "boundary", "id": "membership-and-configuration-q02" } ] } ] } ] }, { "id": "landing-and-transfer-architecture", "name": "Landing and transfer architecture", "description": "Model the distinct physical interfaces used to move carried equipment between ship, craft and shore.", "rationale": "The combined unloading architecture is central to identifying this class and evaluating its capabilities.", "layers": [ { "id": "bow-transfer-interface", "name": "Bow transfer interface", "description": "Describe the bow opening, ramp and vehicle route as a connected transfer system.", "findings": [ { "id": "direct-unloading-constraints", "name": "Direct unloading constraints", "description": "Require documented ramp limits and loading conditions before asserting that a vehicle can use the bow route.", "questions": [ { "text": "What drawings or manuals establish the bow opening, ramp geometry and internal vehicle route?", "kind": "provenance", "id": "direct-unloading-constraints-q01" }, { "text": "What load, clearance and draught limits govern use of this route?", "kind": "measurement", "id": "direct-unloading-constraints-q02" } ] } ] }, { "id": "well-deck-interface", "name": "Well-deck interface", "description": "Describe landing-craft accommodation and its relationship to ship loading.", "findings": [ { "id": "craft-fit-and-docking-state", "name": "Craft fit and docking state", "description": "Treat well-deck compatibility as a type-specific and configuration-dependent relationship.", "questions": [ { "text": "Which landing-craft types have documented compatibility with the Project 1174 well deck?", "kind": "provenance", "id": "craft-fit-and-docking-state-q01" }, { "text": "What usable dimensions and loading restrictions determine the supported craft arrangement?", "kind": "measurement", "id": "craft-fit-and-docking-state-q02" }, { "text": "What inspection evidence is required before describing the docking systems as usable?", "kind": "action", "id": "craft-fit-and-docking-state-q03" } ] } ] } ] }, { "id": "embarked-load-and-aviation", "name": "Embarked load and aviation", "description": "Represent personnel, vehicles, cargo, landing craft and helicopters as a combined accommodation problem.", "rationale": "Published maximum capacities may describe alternative arrangements rather than simultaneous loads.", "layers": [ { "id": "combined-load-arrangements", "name": "Combined load arrangements", "description": "Associate each capacity claim with the arrangement and duration it assumes.", "findings": [ { "id": "capacity-is-conditional", "name": "Capacity is conditional", "description": "Keep vehicle, troop, cargo and landing-craft allowances connected to a single documented loading case.", "questions": [ { "text": "Which reported capacities are alternatives, and which are supported simultaneously?", "kind": "boundary", "id": "capacity-is-conditional-q01" }, { "text": "What vehicle types, cargo mass and embarkation duration underlie each stated capacity?", "kind": "measurement", "id": "capacity-is-conditional-q02" } ] } ] }, { "id": "helicopter-accommodation", "name": "Helicopter accommodation", "description": "Separate flight-deck access, aircraft stowage and onboard support.", "findings": [ { "id": "aviation-support-level", "name": "Aviation support level", "description": "Record helicopter compatibility by hull and period, distinguishing carriage from serviceable support facilities.", "questions": [ { "text": "Which helicopter types were supported on each member hull during the period being described?", "kind": "provenance", "id": "aviation-support-level-q01" }, { "text": "Does a quoted aircraft capacity refer to stowage, flight-deck positions or a supported embarked group?", "kind": "definition", "id": "aviation-support-level-q02" }, { "text": "What evidence establishes the present condition of aviation handling and support facilities?", "kind": "action", "id": "aviation-support-level-q03" } ] } ] } ] }, { "id": "ship-systems-and-loading-envelope", "name": "Ship systems and loading envelope", "description": "Connect machinery, hydrostatic condition and installed equipment to the amphibious transport role.", "rationale": "Transfer functions depend on whole-ship services and loading conditions, not just the presence of ramps and docks.", "layers": [ { "id": "propulsion-and-support-services", "name": "Propulsion and support services", "description": "Record the machinery and service dependencies relevant to movement and cargo handling.", "findings": [ { "id": "machinery-configuration-and-availability", "name": "Machinery configuration and availability", "description": "Distinguish installed propulsion and auxiliary equipment from demonstrated availability on a dated hull.", "questions": [ { "text": "Which propulsion and auxiliary-system differences are documented between member hulls?", "kind": "provenance", "id": "machinery-configuration-and-availability-q01" }, { "text": "Which ship services must be available for the bow-transfer and well-deck systems to function?", "kind": "relation", "id": "machinery-configuration-and-availability-q02" } ] } ] }, { "id": "loading-and-installed-fit", "name": "Loading and installed fit", "description": "Associate dimensions, displacement and equipment changes with a defined ship configuration.", "findings": [ { "id": "configuration-qualified-envelope", "name": "Configuration-qualified envelope", "description": "Record loading limits and installed military equipment at identification level, with modifications and removals dated.", "questions": [ { "text": "Which loading condition underlies each displacement and draught figure?", "kind": "measurement", "id": "configuration-qualified-envelope-q01" }, { "text": "Which equipment additions or removals require revising the hull's configuration record or loading assessment?", "kind": "boundary", "id": "configuration-qualified-envelope-q02" } ] } ] } ] }, { "id": "service-state-and-intervention", "name": "Service state and intervention", "description": "Determine what remains physically present and what actions have adequate evidence and authorization.", "rationale": "A historical landing-ship capability must not be mistaken for a currently usable vessel.", "layers": [ { "id": "dated-hull-status", "name": "Dated hull status", "description": "Separate administrative status, physical survival and equipment condition.", "findings": [ { "id": "disposition-is-not-readiness", "name": "Disposition is not readiness", "description": "Treat service, reserve, disposal and dismantling reports as dated claims that do not independently establish machinery or transfer-system condition.", "questions": [ { "text": "What is the latest reliable disposition evidence for each member hull, and when was it observed?", "kind": "provenance", "id": "disposition-is-not-readiness-q01" }, { "text": "Does the record establish administrative status, physical existence or inspected functional condition?", "kind": "boundary", "id": "disposition-is-not-readiness-q02" } ] } ] }, { "id": "inspection-and-custody", "name": "Inspection and custody", "description": "Connect proposed maintenance, access, towing or preservation work to the responsible custodian and relevant surveys.", "findings": [ { "id": "intervention-evidence", "name": "Intervention evidence", "description": "Require hull-specific authority and condition evidence before recommending physical work on surviving Project 1174 structures.", "questions": [ { "text": "Who controls access and authorizes the proposed intervention on this hull?", "kind": "action", "id": "intervention-evidence-q01" }, { "text": "Which surveys establish the condition of the hull, transfer openings and relevant machinery for that intervention?", "kind": "provenance", "id": "intervention-evidence-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 supplied domain PHY.LIV appears inconsistent with a class of naval vessels; this is an engineered artefact, not an organism.", "Confirm that the registry intends Project 1174 rather than the later Project 23900 usage of the Ivan Rogov name.", "This description is recalled knowledge without source consultation; dimensions, capacities, individual ship histories and present fleet status are omitted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Ivan Rogov-class landing ship 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 naval project designation", "value_or_pattern": "Project 1174", "note": "The project name Nosorog means rhinoceros." }, { "scheme": "NATO reporting name", "value_or_pattern": "Ivan Rogov class", "note": "Names the class after its lead ship." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Ivan Rogov-class landing ship 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": [ "Transporting naval infantry, armoured vehicles and supplies.", "Delivering landing forces through bow ramps where shoreline conditions permit.", "Launching landing craft from a floodable well dock.", "Supporting helicopter-assisted amphibious landings." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Ivan Rogov-class landing ship 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": [ "Grounding or hull damage during approaches to shallow or poorly surveyed landing beaches.", "Flooding and stability hazards during well-dock operations.", "Helicopter accidents during flight-deck operations.", "Fire or explosion involving embarked fuel, ammunition or vehicles.", "Exposure to mines, coastal weapons and other threats during amphibious operations." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Ivan Rogov-class landing ship 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": [ "Soviet and Russian terminology classifies these vessels as large landing ships; English-language descriptions also use amphibious transport dock terminology." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Ivan Rogov-class landing ship 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": "Ivan Rogov", "difference": "An individual ship bearing this name is distinct from the class of ships named after it." }, { "name": "Project 23900 amphibious assault ship", "difference": "A separate, much later Russian design also associated with the name Ivan Rogov; Project 1174 identifies the Soviet class described here." }, { "name": "Ropucha-class landing ship", "difference": "Project 775 is a separate landing-ship design without the Project 1174 combination of well dock and helicopter facilities." }, { "name": "Amphibious transport dock", "difference": "A broader functional ship category; the Ivan Rogov class is a particular design within that general operational role." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Ivan Rogov-class landing ship this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry's underlying identity record conclusively resolve this label to Project 1174 rather than Project 23900?", "What does PHY.LIV mean in the registry, and is its assignment appropriate for this engineered ship class?", "Which original drawings, manuals or builder records establish simultaneous loading arrangements and transfer-interface limits?", "Which propulsion, aviation and installed-equipment differences are documented for each hull and modification period?", "What reliable dated evidence settles the latest physical disposition of every member hull?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 28 } }