Ivan Rogov-class landing ship
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.
Bundle → Layer → Finding → Questions Filled
6 bundles · 11 layers · 16 findings · 28 questions
Project and hull identity Establish which design and member ships the Ivan Rogov-class label denotes.
Project boundary
Resolve the registry label against project identifiers and neighbouring classes.
Project number controls identity
Use Project 1174 as the working identity and require explicit evidence for any competing attribution.
- Which registry-linked record establishes that this entry denotes Project 1174? provenance
- Does any associated record actually describe Project 23900 or another ship named Ivan Rogov? boundary
Member hull attribution
Connect class assertions to identifiable hulls without treating every hull as identical.
Membership and configuration
Record hull identity, naming history and the period to which a configuration claim applies.
- Which construction or naval records establish each hull's membership in Project 1174? provenance
- Is the described feature common to the class, specific to one hull or introduced by a later modification? boundary
Landing and transfer architecture Model the distinct physical interfaces used to move carried equipment between ship, craft and shore.
Bow transfer interface
Describe the bow opening, ramp and vehicle route as a connected transfer system.
Direct unloading constraints
Require documented ramp limits and loading conditions before asserting that a vehicle can use the bow route.
- What drawings or manuals establish the bow opening, ramp geometry and internal vehicle route? provenance
- What load, clearance and draught limits govern use of this route? measurement
Well-deck interface
Describe landing-craft accommodation and its relationship to ship loading.
Craft fit and docking state
Treat well-deck compatibility as a type-specific and configuration-dependent relationship.
- Which landing-craft types have documented compatibility with the Project 1174 well deck? provenance
- What usable dimensions and loading restrictions determine the supported craft arrangement? measurement
- What inspection evidence is required before describing the docking systems as usable? action
Embarked load and aviation Represent personnel, vehicles, cargo, landing craft and helicopters as a combined accommodation problem.
Combined load arrangements
Associate each capacity claim with the arrangement and duration it assumes.
Capacity is conditional
Keep vehicle, troop, cargo and landing-craft allowances connected to a single documented loading case.
- Which reported capacities are alternatives, and which are supported simultaneously? boundary
- What vehicle types, cargo mass and embarkation duration underlie each stated capacity? measurement
Helicopter accommodation
Separate flight-deck access, aircraft stowage and onboard support.
Aviation support level
Record helicopter compatibility by hull and period, distinguishing carriage from serviceable support facilities.
- Which helicopter types were supported on each member hull during the period being described? provenance
- Does a quoted aircraft capacity refer to stowage, flight-deck positions or a supported embarked group? definition
- What evidence establishes the present condition of aviation handling and support facilities? action
Ship systems and loading envelope Connect machinery, hydrostatic condition and installed equipment to the amphibious transport role.
Propulsion and support services
Record the machinery and service dependencies relevant to movement and cargo handling.
Machinery configuration and availability
Distinguish installed propulsion and auxiliary equipment from demonstrated availability on a dated hull.
- Which propulsion and auxiliary-system differences are documented between member hulls? provenance
- Which ship services must be available for the bow-transfer and well-deck systems to function? relation
Loading and installed fit
Associate dimensions, displacement and equipment changes with a defined ship configuration.
Configuration-qualified envelope
Record loading limits and installed military equipment at identification level, with modifications and removals dated.
- Which loading condition underlies each displacement and draught figure? measurement
- Which equipment additions or removals require revising the hull's configuration record or loading assessment? boundary
Service state and intervention Determine what remains physically present and what actions have adequate evidence and authorization.
Dated hull status
Separate administrative status, physical survival and equipment condition.
Disposition is not readiness
Treat service, reserve, disposal and dismantling reports as dated claims that do not independently establish machinery or transfer-system condition.
- What is the latest reliable disposition evidence for each member hull, and when was it observed? provenance
- Does the record establish administrative status, physical existence or inspected functional condition? boundary
Inspection and custody
Connect proposed maintenance, access, towing or preservation work to the responsible custodian and relevant surveys.
Intervention evidence
Require hull-specific authority and condition evidence before recommending physical work on surviving Project 1174 structures.
- Who controls access and authorizes the proposed intervention on this hull? action
- Which surveys establish the condition of the hull, transfer openings and relevant machinery for that intervention? provenance
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of Ivan Rogov-class landing ship this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these identifiers and schemes hold for the sense of Ivan Rogov-class landing ship this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of Ivan Rogov-class landing ship this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of Ivan Rogov-class landing ship this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these regional variation hold for the sense of Ivan Rogov-class landing ship this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- 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? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
What it is Filled
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.
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
Why it exists Filled
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.
Distinguishing features Filled
- 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.
What robots and AI may and may not do Filled
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.
Only with a human decision
- Publishing the position or movements of a military vessel in an ongoing conflict.
- Attributing a specific incident or loss to a named hull.
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.
Moral aspects Filled
- Landing ships carry troops and vehicles; information about them can affect lives in conflict.
- Misinformation about warships can inflame tensions between states.
Who is affected
- Crews and embarked troops
- Civilians in coastal areas
- People affected by naval operations
Owners Filled
Steward
The navy of the operating state for each ship; the builder held the design.
Master systems
- Naval vessel registers of the operating state
Links to other meta-models Filled
parent
- Q73618972 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.ivan-rogov-class-landing-ship
- Wikidata: Q1285148 (https://www.wikidata.org/wiki/Q1285148)
Direct properties required Filled
- Project identity: Project 1174; conflicting attribution; unresolved
- Hull and configuration reference: Member hull identifier, configuration date and supporting record
- Displacement basis: Tonnes, explicitly labelled standard, full-load or observed
- Loaded draught: Metres, with loading and trim conditions
- Vehicle and cargo accommodation: Cargo tonnes, usable deck area in square metres, and vehicle counts by identified type
- Personnel accommodation: Persons, separating ship crew, embarked personnel and temporary overload
- Well-deck compatibility: Landing-craft type linked to documented fit, capacity and configuration
- Helicopter-support envelope: Aircraft type linked separately to landing, stowage and maintenance support
- Transfer-system condition: Bow ramp, doors and well-deck systems: verified usable, restricted, unavailable or unknown
- Hull disposition: Commissioned, reserve, decommissioned, awaiting disposal, dismantled or unresolved; dated
Recognition required Filled
- 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.
Capabilities and actions required Filled
- 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.
Hazards and failure modes required Filled
- 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 interfaces required Filled
- Convention on the International Regulations for Preventing Collisions at Sea (COLREGs), International Maritime Organization.
Context of use required Filled
- 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 Filled
- Wikidata item Q1285148: Ivan Rogov-class landing ship - identity and sense of the item
- Wikipedia: Ivan Rogov-class landing ship - general description of the item
Open questions
- 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?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q1285148/spec.json