{ "model": { "rank": 5626, "code": "thing-q579421", "model_id": "vr.tr.soyuz", "name": "Soyuz", "purpose": "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.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q579421/", "tier": 2, "score": 66, "payload": { "layer": "wikidata", "aliases": [ "Soyuz 7K-VI", "Soyuz TMA-M", "Soyuz 7K-TM", "Soyuz 7K-T", "Soyuz 7K-OK", "Soyuz 7K-OKS", "Soyuz-TMA", "Soyuz-T", "Soyuz-TM", "Soyuz 7K-L1E" ], "aliasCount": 10, "merged": 10, "knownIn": 66, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q579421", "url": "https://www.wikidata.org/wiki/Q579421", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:47:58Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22.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: 01a0885a-5b00-7e23-9dbd-9be46303d9b4\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Soyuz\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 188 things:\n# Batch 006: 1001 registered", "usd": 0, "recall": true }, "codex": { "seconds": 60.6, "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: 01a0885a-5b09-7c91-8f3d-0ec7629d5f4f\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Soyuz\nRegistry id: vr.tr.soyuz\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for " } } }, "metaModel": { "id": "THING-Q579421", "registryId": "vr.tr.soyuz", "name": "Soyuz", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q579421/", "model": { "registry_id": "vr.tr.soyuz", "name": "Soyuz", "purpose": "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.", "definition": "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.", "scope_statement": "Provisionally interpret Soyuz as the crewed spacecraft family, owning its distinctive architecture, variant-dependent capabilities, crew accommodation, orbital interfaces and return constraints; the registry referent requires confirmation before publication.", "in_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" ], "out_of_scope": [ "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" ], "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." ], "characteristics": [ { "name": "Documented family and variant", "kind": "category", "unit_or_values": "Documented Soyuz variant designation; unresolved", "why_it_matters": "Architecture, interfaces and operating limits must be attributed to the applicable variant." }, { "name": "Configuration evidence", "kind": "relation", "unit_or_values": "Applicable technical document, revision and configuration identifier", "why_it_matters": "Prevents capabilities from different Soyuz generations being combined into an unsupported configuration." }, { "name": "Module attachment state", "kind": "state", "unit_or_values": "For each module: attached, separated, unknown; interpreted by mission phase", "why_it_matters": "The vehicle's available functions and return readiness change when modules separate." }, { "name": "Crew and seat configuration", "kind": "relation", "unit_or_values": "Occupant-to-seat, restraint and pressure-suit compatibility records", "why_it_matters": "A nominal seat count does not establish that a particular crew can safely return." }, { "name": "Available crew places", "kind": "measurement", "unit_or_values": "persons, conditional on variant and installed equipment", "why_it_matters": "Supports transport and evacuation assessments without assuming all configurations have identical capacity." }, { "name": "Autonomous endurance", "kind": "measurement", "unit_or_values": "hours or days, with crew load and operating assumptions", "why_it_matters": "Separates free-flight support capability from permissible time attached to a station." }, { "name": "Permitted attached duration", "kind": "measurement", "unit_or_values": "days, with configuration-specific limits and extension authority", "why_it_matters": "A spacecraft attached to a station still has time-limited return capabilities." }, { "name": "Rendezvous and docking compatibility", "kind": "relation", "unit_or_values": "Spacecraft equipment configuration matched to target port and supporting systems", "why_it_matters": "Mechanical compatibility alone does not demonstrate an achievable rendezvous and docking." }, { "name": "Mission phase", "kind": "state", "unit_or_values": "Prelaunch, ascent, free flight, rendezvous, docked, departure, deorbit, descent, landed, unknown", "why_it_matters": "Determines which capabilities, hazards and readiness criteria apply." }, { "name": "Return-system readiness", "kind": "state", "unit_or_values": "Verified ready, restricted, unavailable, unknown; supported by subsystem evidence", "why_it_matters": "An intact or docked Soyuz cannot automatically be treated as an available return vehicle." } ], "affordances": [ "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." ] }, "sources": [], "structure": { "bundles": [ { "id": "soyuz-identity-and-applicability", "name": "Soyuz identity and applicability", "description": "Resolve the Soyuz referent and establish which spacecraft configuration a claim describes.", "rationale": "Soyuz names both spacecraft and launch vehicles, while spacecraft variants cannot safely share every capability claim.", "layers": [ { "id": "registry-referent", "name": "Registry referent", "description": "Establish the intended kind and its boundary.", "findings": [ { "id": "spacecraft-family-boundary", "name": "Spacecraft family boundary", "description": "The draft assumes the crewed spacecraft family; registry provenance must support that interpretation.", "questions": [ { "text": "Which originating registry or Wikidata record establishes whether Soyuz denotes the spacecraft family or the launch-vehicle family?", "kind": "provenance", "id": "spacecraft-family-boundary-q01" }, { "text": "Does an existing Vercy model already own this concept and require linking rather than another publication?", "kind": "boundary", "id": "spacecraft-family-boundary-q02" } ] } ] }, { "id": "variant-applicability", "name": "Variant applicability", "description": "Attach capability claims to documented Soyuz variants and configurations.", "findings": [ { "id": "configuration-specific-claims", "name": "Configuration-specific claims", "description": "Record the variant and document applicability before treating a feature or limit as usable evidence.", "questions": [ { "text": "Which documented Soyuz variant and equipment configuration does this description cover?", "kind": "definition", "id": "configuration-specific-claims-q01" }, { "text": "Which source revision supports extending each capability claim to that configuration?", "kind": "provenance", "id": "configuration-specific-claims-q02" } ] } ] } ] }, { "id": "modules-and-flight-functions", "name": "Modules and flight functions", "description": "Describe Soyuz's module arrangement and the functions available in each flight configuration.", "rationale": "Soyuz operates as a joined spacecraft before returning its descent module, so module boundaries determine capability and loss of capability.", "layers": [ { "id": "module-function-allocation", "name": "Module function allocation", "description": "Identify functions and interfaces associated with the three principal modules.", "findings": [ { "id": "three-module-architecture", "name": "Three-module architecture", "description": "Use the orbital, descent and instrumentation/propulsion modules as the starting architectural distinction, verified for the applicable variant.", "questions": [ { "text": "Which habitation, docking, control, power and propulsion functions are assigned to each module in this variant?", "kind": "definition", "id": "three-module-architecture-q01" }, { "text": "Which intermodule connections must remain available for the current mission phase?", "kind": "boundary", "id": "three-module-architecture-q02" } ] } ] }, { "id": "orbital-resource-state", "name": "Orbital resource state", "description": "Relate usable electrical and propulsion resources to Soyuz flight tasks.", "findings": [ { "id": "maneuver-and-power-margin", "name": "Maneuver and power margin", "description": "Represent resource sufficiency against named rendezvous, departure and return obligations rather than a generic operational label.", "questions": [ { "text": "What usable propulsion and electrical reserves are established, in which units and under which operating assumptions?", "kind": "measurement", "id": "maneuver-and-power-margin-q01" }, { "text": "Which planned maneuvers or contingency obligations become unsupported when those reserves fall below documented limits?", "kind": "action", "id": "maneuver-and-power-margin-q02" } ] } ] } ] }, { "id": "crew-support-and-endurance", "name": "Crew support and endurance", "description": "Represent crew accommodation and time-dependent support constraints during free flight and station attachment.", "rationale": "Soyuz's transport and return roles depend on actual crew compatibility and consumable margins, not simply nominal occupancy.", "layers": [ { "id": "crew-return-fit", "name": "Crew return fit", "description": "Connect occupants to the equipment required for their flight and return.", "findings": [ { "id": "occupant-equipment-compatibility", "name": "Occupant equipment compatibility", "description": "Treat seats, restraints, suits and applicable occupant limits as evidence needed to assign crew places.", "questions": [ { "text": "What seat, restraint, pressure-suit and occupant-fit requirements apply to this Soyuz configuration?", "kind": "definition", "id": "occupant-equipment-compatibility-q01" }, { "text": "What verified equipment allocation supports each proposed occupant's return?", "kind": "provenance", "id": "occupant-equipment-compatibility-q02" } ] } ] }, { "id": "support-duration", "name": "Support duration", "description": "Separate autonomous life-support endurance from allowable attached service duration.", "findings": [ { "id": "duration-limits-and-consumables", "name": "Duration limits and consumables", "description": "State duration limits with crew loading, resource assumptions and documented extension conditions.", "questions": [ { "text": "What autonomous endurance is supported by the available atmosphere-control resources, water, power and other limiting provisions?", "kind": "measurement", "id": "duration-limits-and-consumables-q01" }, { "text": "What attached-duration limit applies, and what evidence and authority support any extension?", "kind": "provenance", "id": "duration-limits-and-consumables-q02" } ] } ] } ] }, { "id": "rendezvous-docking-and-station-role", "name": "Rendezvous, docking and station role", "description": "Capture target compatibility, relative-flight capabilities and Soyuz's role while attached.", "rationale": "A Soyuz serving a station must both reach a compatible port and retain the capability required for its assigned departure or return role.", "layers": [ { "id": "target-and-control-compatibility", "name": "Target and control compatibility", "description": "Match Soyuz rendezvous and docking equipment to a specific target interface.", "findings": [ { "id": "compatible-approach-and-capture", "name": "Compatible approach and capture", "description": "Assess docking hardware, relative-navigation support and available control modes together.", "questions": [ { "text": "Which target ports and supporting rendezvous systems are compatible with this Soyuz configuration?", "kind": "boundary", "id": "compatible-approach-and-capture-q01" }, { "text": "Which automatic and crew-controlled approach capabilities are documented, and what conditions restrict their use?", "kind": "action", "id": "compatible-approach-and-capture-q02" } ] } ] }, { "id": "attached-return-availability", "name": "Attached return availability", "description": "Assess Soyuz as an attached vehicle with a continuing departure and return obligation.", "findings": [ { "id": "station-return-role", "name": "Station return role", "description": "Represent assigned occupants, station dependencies and readiness evidence for the attached spacecraft's return role.", "questions": [ { "text": "Which crew members and return obligations are assigned to this Soyuz while it is attached?", "kind": "boundary", "id": "station-return-role-q01" }, { "text": "What documented checks establish that station-supported operation can transition to autonomous departure and return?", "kind": "action", "id": "station-return-role-q02" } ] } ] } ] }, { "id": "return-descent-and-recovery", "name": "Return, descent and recovery", "description": "Represent the irreversible transition from orbital spacecraft to descending capsule and recovered vehicle.", "rationale": "Soyuz return depends on coordinated deorbit, module separation, descent protection and landing systems whose readiness must be assessed by phase.", "layers": [ { "id": "deorbit-and-module-separation", "name": "Deorbit and module separation", "description": "Connect orbital departure conditions to the configuration required for atmospheric entry.", "findings": [ { "id": "entry-configuration-readiness", "name": "Entry configuration readiness", "description": "Track evidence for deorbit capability and required module separation without turning the model into an execution procedure.", "questions": [ { "text": "Which configuration-specific conditions establish deorbit and module-separation readiness?", "kind": "action", "id": "entry-configuration-readiness-q01" }, { "text": "What evidence distinguishes confirmed separation from an indication whose reliability remains unresolved?", "kind": "provenance", "id": "entry-configuration-readiness-q02" } ] } ] }, { "id": "descent-and-ground-recovery", "name": "Descent and ground recovery", "description": "Relate descent-system condition, landing expectations and recovery support.", "findings": [ { "id": "landing-and-recovery-constraints", "name": "Landing and recovery constraints", "description": "Record variant-specific descent modes, thermal protection, parachute and landing-system requirements alongside recovery dependencies.", "questions": [ { "text": "Which descent modes and thermal-protection, parachute and landing-system limits are documented for this variant?", "kind": "definition", "id": "landing-and-recovery-constraints-q01" }, { "text": "Which landing-area, environmental and crew-condition constraints determine required recovery support?", "kind": "action", "id": "landing-and-recovery-constraints-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 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." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Soyuz 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": [ "Early Soyuz 7K-series spacecraft", "Soyuz T", "Soyuz TM", "Soyuz TMA", "Soyuz TMA-M", "Soyuz MS" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Soyuz 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": "Soyuz flight designation", "value_or_pattern": "Soyuz or Soyuz -", "note": "Names a mission or its spacecraft, rather than the entire family; examples include Soyuz 1 and Soyuz MS-01." }, { "scheme": "COSPAR International Designator", "value_or_pattern": "YYYY-NNNAAA", "note": "Identifies an individual launched space object using launch year, launch sequence and an alphabetic component suffix." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Soyuz 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 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." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Soyuz 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": "Crew capacity", "typical_range": "2-3, depending on variant", "unit": "people" }, { "quantity": "Launch mass of later variants", "typical_range": "approximately 7,000-7,300", "unit": "kg" }, { "quantity": "Overall spacecraft length", "typical_range": "approximately 7.2", "unit": "m" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Soyuz 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": [ "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." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Soyuz 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": [ "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." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Soyuz 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": "Soyuz launch vehicle", "difference": "The rocket delivers payloads into orbit; the spacecraft carries occupants in orbit and returns them to Earth." }, { "name": "Progress spacecraft", "difference": "Progress is a related uncrewed cargo spacecraft whose routine mission ends in destructive atmospheric reentry." }, { "name": "Shenzhou spacecraft", "difference": "Shenzhou is a separate Chinese spacecraft family with a similar three-module arrangement." }, { "name": "Soyuz mission", "difference": "A mission is a particular flight or operational event; this entry describes the spacecraft family." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Soyuz this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "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?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a Soyuz, record what state it is in, and decide what may be done with it.", "whatItIs": "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.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Soyuz 7K-VI, Soyuz TMA-M, Soyuz 7K-TM, Soyuz 7K-T, Soyuz 7K-OK, Soyuz 7K-OKS, Soyuz-TMA, Soyuz-T, Soyuz-TM, Soyuz 7K-L1E.", "10 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 66 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a Soyuz, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form and material. The registry holds no appearance data, so what a Soyuz looks like has to come from research." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Soyuz 7K-VI", "Soyuz TMA-M", "Soyuz 7K-TM", "Soyuz 7K-T", "Soyuz 7K-OK", "Soyuz 7K-OKS", "Soyuz-TMA", "Soyuz-T", "Soyuz-TM", "Soyuz 7K-L1E" ] } ], "standing": "Described in 66 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 10 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Soyuz from another, and a Soyuz from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a Soyuz sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a Soyuz from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a Soyuz is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a Soyuz is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a Soyuz is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a Soyuz is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a Soyuz is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a Soyuz is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a Soyuz passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a Soyuz between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a Soyuz, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Soyuz is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "use-and-operation", "name": "Use and operation", "description": "What can be done with a Soyuz and what it takes to do it.", "rationale": "An agent that can recognise a thing but not act on it has only half a model.", "layers": [ { "id": "intended-use", "name": "Intended use and function", "description": "What a Soyuz is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Soyuz performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "function-and-purpose-q02", "text": "Who or what asserted this about the use of a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "function-and-purpose-q03", "text": "What may an agent decide or do once the use of a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "handling-and-procedure", "name": "Handling and procedure", "description": "The steps, skills and tools involved in using a Soyuz.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Soyuz at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "procedures-and-skills-q02", "text": "Who or what asserted this about handling a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "procedures-and-skills-q03", "text": "What may an agent decide or do once handling a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Soyuz came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a Soyuz and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a Soyuz is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Soyuz, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a Soyuz, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a Soyuz is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 13, "findings": 15, "questions": 45 } } } }