Soyuz
Enable an AI agent to recognise a Soyuz crewed spacecraft, assess its configuration and mission state, and identify actions supported by configuration-specific evidence and authority.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an AI agent to recognise a Soyuz crewed spacecraft, assess its configuration and mission state, and identify actions supported by configuration-specific evidence and authority.
Soyuz is a Soviet-origin family of crewed orbital spacecraft with an orbital module, a reentry capsule and a service module, designed to transport people to and from low Earth orbit.
It can be Classify a Soyuz reference as spacecraft family, variant, individual vehicle or launch-vehicle namesake.; Compare a documented configuration with crew transport and return requirements.; Check proposed rendezvous and docking compatibility against target-interface evidence.; Assess whether endurance and attached-duration limits support a proposed mission interval.; Identify missing evidence or restrictions affecting departure, return or recovery readiness.; Route a proposed action to the applicable approved procedure and responsible authority..
Distinguishing features
Determine whether the referent is the crewed spacecraft or the launch vehicle: the shared Soyuz name alone does not establish identity.
Check for the characteristic orbital module, descent module and instrumentation/propulsion module arrangement against documentation for the stated variant.
Establish that the descent module supports crewed atmospheric return; a related cargo vehicle with similar external features is not sufficient.
Require an explicit Soyuz variant or documented family relationship rather than classifying every Russian crewed capsule as Soyuz.
Distinguish a reusable family description from a named mission, serial-numbered spacecraft or museum article.
Scope
+ Soyuz spacecraft family identity, variants and configuration applicability
+ Orbital, descent, and instrumentation/propulsion module architecture
+ Crew accommodation, life support and mission-duration constraints
+ Rendezvous, docking, attached operations and departure readiness
+ Module separation, atmospheric return, landing and recovery interfaces
- Soyuz launch-vehicle family design and launch-site infrastructure
- The wider Soyuz programme and its institutional history
- Individual mission histories and individual spacecraft asset records
- Space-station architecture beyond interfaces used by Soyuz
- Progress cargo-spacecraft design
- Detailed flight procedures and operational command authority
Characteristics
- Documented family and variant
- Documented Soyuz variant designation; unresolved Architecture, interfaces and operating limits must be attributed to the applicable variant.
- Configuration evidence
- Applicable technical document, revision and configuration identifier Prevents capabilities from different Soyuz generations being combined into an unsupported configuration.
- Module attachment state
- For each module: attached, separated, unknown; interpreted by mission phase The vehicle's available functions and return readiness change when modules separate.
- Crew and seat configuration
- Occupant-to-seat, restraint and pressure-suit compatibility records A nominal seat count does not establish that a particular crew can safely return.
- Available crew places
- persons, conditional on variant and installed equipment Supports transport and evacuation assessments without assuming all configurations have identical capacity.
- Autonomous endurance
- hours or days, with crew load and operating assumptions Separates free-flight support capability from permissible time attached to a station.
- Permitted attached duration
- days, with configuration-specific limits and extension authority A spacecraft attached to a station still has time-limited return capabilities.
- Rendezvous and docking compatibility
- Spacecraft equipment configuration matched to target port and supporting systems Mechanical compatibility alone does not demonstrate an achievable rendezvous and docking.
- Mission phase
- Prelaunch, ascent, free flight, rendezvous, docked, departure, deorbit, descent, landed, unknown Determines which capabilities, hazards and readiness criteria apply.
- Return-system readiness
- Verified ready, restricted, unavailable, unknown; supported by subsystem evidence An intact or docked Soyuz cannot automatically be treated as an available return vehicle.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 18 findings · 28 questions.
Soyuz identity and applicability Resolve the Soyuz referent and establish which spacecraft configuration a claim describes.
Soyuz names both spacecraft and launch vehicles, while spacecraft variants cannot safely share every capability claim.
Registry referent
Establish the intended kind and its boundary.
Spacecraft family boundary
The draft assumes the crewed spacecraft family; registry provenance must support that interpretation.
- Which originating registry or Wikidata record establishes whether Soyuz denotes the spacecraft family or the launch-vehicle family? provenance
- Does an existing Vercy model already own this concept and require linking rather than another publication? boundary
Variant applicability
Attach capability claims to documented Soyuz variants and configurations.
Configuration-specific claims
Record the variant and document applicability before treating a feature or limit as usable evidence.
- Which documented Soyuz variant and equipment configuration does this description cover? definition
- Which source revision supports extending each capability claim to that configuration? provenance
Modules and flight functions Describe Soyuz's module arrangement and the functions available in each flight configuration.
Soyuz operates as a joined spacecraft before returning its descent module, so module boundaries determine capability and loss of capability.
Module function allocation
Identify functions and interfaces associated with the three principal modules.
Three-module architecture
Use the orbital, descent and instrumentation/propulsion modules as the starting architectural distinction, verified for the applicable variant.
- Which habitation, docking, control, power and propulsion functions are assigned to each module in this variant? definition
- Which intermodule connections must remain available for the current mission phase? boundary
Orbital resource state
Relate usable electrical and propulsion resources to Soyuz flight tasks.
Maneuver and power margin
Represent resource sufficiency against named rendezvous, departure and return obligations rather than a generic operational label.
- What usable propulsion and electrical reserves are established, in which units and under which operating assumptions? measurement
- Which planned maneuvers or contingency obligations become unsupported when those reserves fall below documented limits? action
Crew support and endurance Represent crew accommodation and time-dependent support constraints during free flight and station attachment.
Soyuz's transport and return roles depend on actual crew compatibility and consumable margins, not simply nominal occupancy.
Crew return fit
Connect occupants to the equipment required for their flight and return.
Occupant equipment compatibility
Treat seats, restraints, suits and applicable occupant limits as evidence needed to assign crew places.
- What seat, restraint, pressure-suit and occupant-fit requirements apply to this Soyuz configuration? definition
- What verified equipment allocation supports each proposed occupant's return? provenance
Support duration
Separate autonomous life-support endurance from allowable attached service duration.
Duration limits and consumables
State duration limits with crew loading, resource assumptions and documented extension conditions.
- What autonomous endurance is supported by the available atmosphere-control resources, water, power and other limiting provisions? measurement
- What attached-duration limit applies, and what evidence and authority support any extension? provenance
Rendezvous, docking and station role Capture target compatibility, relative-flight capabilities and Soyuz's role while attached.
A Soyuz serving a station must both reach a compatible port and retain the capability required for its assigned departure or return role.
Target and control compatibility
Match Soyuz rendezvous and docking equipment to a specific target interface.
Compatible approach and capture
Assess docking hardware, relative-navigation support and available control modes together.
- Which target ports and supporting rendezvous systems are compatible with this Soyuz configuration? boundary
- Which automatic and crew-controlled approach capabilities are documented, and what conditions restrict their use? action
Attached return availability
Assess Soyuz as an attached vehicle with a continuing departure and return obligation.
Station return role
Represent assigned occupants, station dependencies and readiness evidence for the attached spacecraft's return role.
- Which crew members and return obligations are assigned to this Soyuz while it is attached? boundary
- What documented checks establish that station-supported operation can transition to autonomous departure and return? action
Return, descent and recovery Represent the irreversible transition from orbital spacecraft to descending capsule and recovered vehicle.
Soyuz return depends on coordinated deorbit, module separation, descent protection and landing systems whose readiness must be assessed by phase.
Deorbit and module separation
Connect orbital departure conditions to the configuration required for atmospheric entry.
Entry configuration readiness
Track evidence for deorbit capability and required module separation without turning the model into an execution procedure.
- Which configuration-specific conditions establish deorbit and module-separation readiness? action
- What evidence distinguishes confirmed separation from an indication whose reliability remains unresolved? provenance
Descent and ground recovery
Relate descent-system condition, landing expectations and recovery support.
Landing and recovery constraints
Record variant-specific descent modes, thermal protection, parachute and landing-system requirements alongside recovery dependencies.
- Which descent modes and thermal-protection, parachute and landing-system limits are documented for this variant? definition
- Which landing-area, environmental and crew-condition constraints determine required recovery support? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
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.
- The unqualified name Soyuz also denotes a launch vehicle family; the spacecraft sense is assumed and should be checked against the registry identifier.
- Dimensions, mass, crew capacity and operating capabilities vary by generation; the measurements here are approximate.
- The early 7K-series grouping compresses several distinct designs; no applicable technical standards are asserted from recall.
- Which of these check these first hold for the sense of Soyuz this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Early Soyuz 7K-series spacecraft
- Soyuz T
- Soyuz TM
- Soyuz TMA
- Soyuz TMA-M
- Soyuz MS
- Which of these kinds and varieties hold for the sense of Soyuz this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Soyuz flight designation - Soyuz <number> or Soyuz <variant>-<number> - Names a mission or its spacecraft, rather than the entire family; examples include Soyuz 1 and Soyuz MS-01.
- COSPAR International Designator - YYYY-NNNAAA - Identifies an individual launched space object using launch year, launch sequence and an alphabetic component suffix.
- Which of these identifiers and schemes hold for the sense of Soyuz this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Transporting crews to and from Salyut, Mir and the International Space Station.
- Remaining docked to a space station as a crew return vehicle.
- Conducting independent crewed orbital missions and rendezvous operations.
- Carrying limited supplies to orbit and returning limited cargo with the crew.
- Which of these real-world use hold for the sense of Soyuz this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Crew capacity - 2-3, depending on variant - people
- Launch mass of later variants - approximately 7,000-7,300 - kg
- Overall spacecraft length - approximately 7.2 - m
- Which of these typical measurements hold for the sense of Soyuz 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.
- Cabin depressurization can cause fatal loss of breathable atmosphere.
- Parachute deployment or inflation failure can prevent a survivable landing.
- Module separation or attitude-control failures can disrupt reentry and expose occupants to excessive acceleration or heating.
- Rendezvous or docking failures can cause collision or prevent access to a station.
- Launch vehicle failure can require emergency separation using the launch escape system.
- Which of these failure modes and hazards hold for the sense of Soyuz this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Developed in the Soviet Union and subsequently operated within Russia's space programme.
- Historically launched from Baikonur in Kazakhstan, with routine land landings also occurring in Kazakhstan.
- Which of these regional variation hold for the sense of Soyuz 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.
- Soyuz launch vehicle - The rocket delivers payloads into orbit; the spacecraft carries occupants in orbit and returns them to Earth.
- Progress spacecraft - Progress is a related uncrewed cargo spacecraft whose routine mission ends in destructive atmospheric reentry.
- Shenzhou spacecraft - Shenzhou is a separate Chinese spacecraft family with a similar three-module arrangement.
- Soyuz mission - A mission is a particular flight or operational event; this entry describes the spacecraft family.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Soyuz this model covers, and on what evidence? provenance
What the second pass must settle
- Does vr.tr.soyuz identify the spacecraft family, launch-vehicle family or another referent, and does an existing world model already cover it?
- Which Soyuz variants belong within the registry entry, and which architectural or operational claims are demonstrably shared across them?
- Which authoritative, accessible sources establish capacities, endurance, attached-duration limits and docking compatibility for each included configuration?
- Where should ascent escape and abort provisions be divided between this spacecraft model and the launch-vehicle or integrated launch-system model?
- Which readiness criteria can public documentation substantiate, and which must remain unresolved without controlled technical records or operational authority?