{ "model": { "rank": 6567, "code": "thing-q486066", "model_id": "vr.tr.yakovlev-sj-100", "name": "Yakovlev SJ-100", "purpose": "Enable an agent to identify the Yakovlev SJ-100 design, distinguish its configurations from earlier Superjets, and determine which capability, approval and support claims apply.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q486066/", "tier": 2, "score": 60, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 60, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q486066", "url": "https://www.wikidata.org/wiki/Q486066", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:02:29Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.9, "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: 01a08867-5aa8-7550-abd4-575cc89b8263\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Yakovlev SJ-100\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 007: 1001", "usd": 0, "recall": true }, "codex": { "seconds": 80.2, "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: 01a08867-5a5d-7c33-a484-42ea9130e7a9\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Yakovlev SJ-100\nRegistry id: vr.tr.yakovlev-sj-100\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (" } } }, "metaModel": { "id": "THING-Q486066", "registryId": "vr.tr.yakovlev-sj-100", "name": "Yakovlev SJ-100", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q486066/", "model": { "registry_id": "vr.tr.yakovlev-sj-100", "name": "Yakovlev SJ-100", "purpose": "Enable an agent to identify the Yakovlev SJ-100 design, distinguish its configurations from earlier Superjets, and determine which capability, approval and support claims apply.", "definition": "The Yakovlev SJ-100 is a Russian twin-engine regional passenger jet developed from the Sukhoi Superjet 100, with redesigned systems intended to replace imported equipment and use Russian PD-8 turbofan engines.", "scope_statement": "This model owns vr.tr.yakovlev-sj-100 in PHY / PHY.OBJ as an aircraft design entry, provisionally centred on the import-substituted Superjet derivative; it records configuration-dependent distinctions while leaving the registry's intended coverage of earlier Superjets unresolved.", "in_scope": [ "SJ-100 designation, Superjet ancestry and configuration boundaries", "PD-8 propulsion integration and the treatment of development aircraft with other engines", "Replacement aircraft systems and their configuration dependencies", "Configuration-specific passenger capacity, performance and airport requirements", "Certification evidence, operating limitations and maintenance applicability" ], "out_of_scope": [ "Generic aircraft aerodynamics and jet propulsion principles", "Earlier SSJ100 configurations except where needed to establish ancestry or differences", "PD-8 and SaM146 engine designs as independent products", "Individual aircraft ownership, flight histories and live technical logs", "Airline scheduling, ticket sales and route economics", "Yakovlev corporate governance and manufacturing-site management" ], "distinguishing_features": [ "Require a documented SJ-100 design or configuration reference; a Superjet name, photograph or airline livery alone does not establish membership.", "Check the propulsion baseline: Yakovlev lists two PD-8 turbofans for its SJ-100 product. [Manufacturer product page](https://yakovlev.ru/products/sj-100/)", "Do not use engine type as the sole identity test: Yakovlev explicitly identifies its first SJ-100 prototype as using SaM146 engines. [Manufacturer first-flight release](https://eng.yakovlev.ru/press-centre/releases/import-substituted-superjet-performed-its-maiden-flight/)", "Distinguish the derivative through documented replacement-system configurations, including avionics, landing gear, auxiliary power and control systems, rather than assuming it is only an engine change. [Manufacturer test-program release](https://yakovlev.ru/press-centre/releases/importozameshchennyy-sj-100-zavershil-zavodskie-dovodochnye-ispytaniya/)" ], "characteristics": [ { "name": "Design identity and ancestry", "kind": "relation", "unit_or_values": "Registry entry linked to manufacturer designation, predecessor design and authoritative type-design reference", "why_it_matters": "Prevents branding changes from creating duplicate models or incorrectly merging distinct configurations." }, { "name": "Configuration baseline", "kind": "category", "unit_or_values": "Documented baseline identifier; prototype, certification-test or production configuration", "why_it_matters": "Determines which specifications and evidence can be applied." }, { "name": "Propulsion installation", "kind": "relation", "unit_or_values": "Engine model, installation standard, control-system revision and applicability", "why_it_matters": "Separates PD-8 product claims from SaM146 development evidence and identifies integration dependencies." }, { "name": "Replacement-system coverage", "kind": "relation", "unit_or_values": "Subsystem mapped to equipment identity, supplier evidence, revision and applicable baseline", "why_it_matters": "Makes import-substitution claims inspectable without treating national origin as proof of compatibility." }, { "name": "Passenger accommodation", "kind": "measurement", "unit_or_values": "Seats by cabin layout, seat pitch in mm and approved occupancy limit", "why_it_matters": "Separates advertised capacity from the capacity supported by a particular cabin and approval." }, { "name": "Mass and payload limits", "kind": "measurement", "unit_or_values": "kg; maximum take-off, landing and zero-fuel masses, with payload assumptions and configuration", "why_it_matters": "Supports meaningful comparisons without borrowing predecessor limits." }, { "name": "Mission performance", "kind": "measurement", "unit_or_values": "Range in km, cruise speed in Mach or km/h, fuel in kg; payload, reserves and atmospheric assumptions attached", "why_it_matters": "Prevents an advertised range from being mistaken for a guaranteed route capability." }, { "name": "Airport compatibility envelope", "kind": "measurement", "unit_or_values": "Dimensions and runway distances in m; pavement, servicing and environmental constraints", "why_it_matters": "Identifies the evidence needed before claiming compatibility with an airport." }, { "name": "Approval status", "kind": "state", "unit_or_values": "Unknown, under evaluation, approved, restricted, suspended or superseded; dated by authority and configuration", "why_it_matters": "Keeps demonstrated flight capability separate from permission for a specified operation." }, { "name": "Maintenance applicability", "kind": "relation", "unit_or_values": "Applicable manual revisions, directives, service bulletins, parts eligibility and life limits in hours, cycles or calendar time", "why_it_matters": "Prevents unsupported reuse of earlier Superjet maintenance assumptions." } ], "affordances": [ "Classify a supplied aircraft description against documented SJ-100 baselines and flag ambiguous Superjet naming.", "Compare SJ-100 and predecessor capabilities using matched configurations and measurement assumptions.", "Identify the approval documents required to evaluate a proposed operation.", "Trace a subsystem replacement to affected performance claims, manuals and support requirements.", "Screen cabin or airport suitability using configuration-specific evidence.", "Flag missing evidence that prevents a compatibility, maintenance or operational decision." ] }, "sources": [], "structure": { "bundles": [ { "id": "superjet-identity", "name": "Superjet identity and design boundary", "description": "Establish what the registered SJ-100 name denotes and how it relates to earlier Superjets.", "rationale": "The entry lacks a definition, and name continuity can conceal differences between a family, derivative and test configuration.", "layers": [ { "id": "designation-lineage", "name": "Designation and lineage", "description": "Connect registry naming to manufacturer and approval terminology.", "findings": [ { "id": "name-does-not-fix-coverage", "name": "Naming does not settle registry coverage", "description": "Record the evidence needed to decide whether this entry denotes the import-substituted derivative or a broader renamed family.", "questions": [ { "text": "Which manufacturer or registry provenance record defines the intended coverage of vr.tr.yakovlev-sj-100?", "kind": "provenance", "id": "name-does-not-fix-coverage-q01" }, { "text": "Does an existing Superjet world model already own this concept, requiring a link instead of a second model?", "kind": "boundary", "id": "name-does-not-fix-coverage-q02" } ] } ] }, { "id": "baseline-membership", "name": "Baseline membership", "description": "Distinguish development configurations from the product baseline.", "findings": [ { "id": "prototype-engine-exception", "name": "Prototype engine exception", "description": "The first SJ-100 prototype used SaM146 engines, so membership cannot be inferred from PD-8 installation alone. [Yakovlev release](https://eng.yakovlev.ru/press-centre/releases/import-substituted-superjet-performed-its-maiden-flight/)", "questions": [ { "text": "Which design records establish an aircraft's SJ-100 baseline independently of its installed engines?", "kind": "definition", "id": "prototype-engine-exception-q01" }, { "text": "Which results from a SaM146-equipped prototype are explicitly applicable to a PD-8 configuration?", "kind": "boundary", "id": "prototype-engine-exception-q02" } ] } ] } ] }, { "id": "propulsion-and-replacement-systems", "name": "Propulsion and replacement systems", "description": "Describe the equipment changes that distinguish the SJ-100 derivative.", "rationale": "Replacing propulsion and onboard systems creates interfaces and evidence requirements that predecessor specifications cannot settle.", "layers": [ { "id": "pd-8-installation", "name": "PD-8 installation", "description": "Model the aircraft-level consequences of the propulsion baseline.", "findings": [ { "id": "installed-propulsion-baseline", "name": "Installed propulsion baseline", "description": "Yakovlev identifies two PD-8 turbofans for the SJ-100; installation-specific limits must be obtained separately. [Product page](https://yakovlev.ru/products/sj-100/)", "questions": [ { "text": "Which PD-8 installation and control-system standards belong to each SJ-100 baseline?", "kind": "definition", "id": "installed-propulsion-baseline-q01" }, { "text": "What approved thrust ratings, fuel specifications and installation limits apply to that baseline?", "kind": "measurement", "id": "installed-propulsion-baseline-q02" } ] } ] }, { "id": "replacement-system-integration", "name": "Replacement-system integration", "description": "Track equipment changes and dependencies across the aircraft.", "findings": [ { "id": "replacement-is-system-specific", "name": "Replacement is system-specific", "description": "Manufacturer reporting identifies replacement avionics, landing gear, auxiliary power, integrated control and electrical systems; each needs its own applicability evidence. [Yakovlev test release](https://yakovlev.ru/press-centre/releases/importozameshchennyy-sj-100-zavershil-zavodskie-dovodochnye-ispytaniya/)", "questions": [ { "text": "Which equipment identifiers and revisions substantiate replacement claims for each SJ-100 baseline?", "kind": "provenance", "id": "replacement-is-system-specific-q01" }, { "text": "Which equipment or software changes require coordinated changes elsewhere in the aircraft?", "kind": "action", "id": "replacement-is-system-specific-q02" } ] } ] } ] }, { "id": "regional-transport-capability", "name": "Regional transport capability", "description": "Capture usable passenger, payload and airport envelopes for a specified SJ-100 configuration.", "rationale": "The derivative's capability must be supported by its own configuration evidence instead of inherited Superjet marketing figures.", "layers": [ { "id": "cabin-and-mission", "name": "Cabin and mission", "description": "Relate passenger accommodation to payload and range assumptions.", "findings": [ { "id": "configuration-bound-capacity", "name": "Configuration-bound capacity", "description": "Treat seating, payload and range as linked claims whose layout, mass and reserve assumptions must be recorded.", "questions": [ { "text": "What passenger layouts and occupancy limits are documented specifically for the SJ-100 configuration?", "kind": "measurement", "id": "configuration-bound-capacity-q01" }, { "text": "Under which payload, fuel-reserve and atmospheric assumptions are its range and fuel-consumption figures stated?", "kind": "measurement", "id": "configuration-bound-capacity-q02" } ] } ] }, { "id": "airport-and-environment", "name": "Airport and environment", "description": "Connect the aircraft configuration to airport and operating-condition constraints.", "findings": [ { "id": "airport-compatibility-evidence", "name": "Airport compatibility evidence", "description": "Require SJ-100-specific geometry, ground-service interfaces and performance evidence before transferring predecessor airport compatibility claims.", "questions": [ { "text": "What dimensions, pavement requirements and ground-service interfaces are documented for this baseline?", "kind": "measurement", "id": "airport-compatibility-evidence-q01" }, { "text": "Which approved performance data support assessment of a proposed runway, elevation, temperature and surface condition?", "kind": "action", "id": "airport-compatibility-evidence-q02" } ] } ] } ] }, { "id": "approval-and-operating-authority", "name": "Approval and operating authority", "description": "Separate design maturity, regulatory approval and permission for particular operations.", "rationale": "Prototype flights, production milestones and certification announcements support different conclusions about the SJ-100.", "layers": [ { "id": "certification-applicability", "name": "Certification applicability", "description": "Identify the governing authority, approval instrument and covered configuration.", "findings": [ { "id": "dated-approval-evidence", "name": "Dated approval evidence", "description": "Current approval status remains unresolved until supported by an authoritative record with configuration and jurisdiction coverage.", "questions": [ { "text": "Which Rosaviatsiya certificate, amendment or other approval instrument covers the SJ-100, and what certification basis does it name?", "kind": "provenance", "id": "dated-approval-evidence-q01" }, { "text": "Which engine, equipment and cabin configurations are included or excluded by that approval?", "kind": "boundary", "id": "dated-approval-evidence-q02" } ] } ] }, { "id": "limitations-and-dispatch", "name": "Limitations and dispatch", "description": "Identify the documents needed to assess operating modes and degraded-system conditions.", "findings": [ { "id": "sj-100-operating-documentation", "name": "SJ-100 operating documentation", "description": "Record applicable flight-manual limitations, protection descriptions and dispatch provisions without presuming earlier SSJ100 procedures transfer.", "questions": [ { "text": "Which SJ-100 manual revisions define control modes, protections, warnings and operating limitations?", "kind": "provenance", "id": "sj-100-operating-documentation-q01" }, { "text": "What configuration-specific dispatch provisions and aircraft-instance evidence are required to assess operation with a reported defect?", "kind": "action", "id": "sj-100-operating-documentation-q02" } ] } ] } ] }, { "id": "continued-airworthiness-and-support", "name": "Continued airworthiness and support", "description": "Determine how the SJ-100 configuration is maintained and which support resources apply.", "rationale": "Replacement equipment changes parts eligibility, maintenance tasks and the relevance of predecessor service experience.", "layers": [ { "id": "maintenance-and-parts", "name": "Maintenance and parts", "description": "Connect the baseline to maintenance instructions, consumables and eligible components.", "findings": [ { "id": "maintenance-transfer-needs-evidence", "name": "Maintenance transfer needs evidence", "description": "Require explicit applicability for inherited Superjet tasks, tools, consumables and parts, particularly across propulsion and replacement-system boundaries.", "questions": [ { "text": "Which manuals establish SJ-100 inspection intervals, life limits and approved consumables?", "kind": "provenance", "id": "maintenance-transfer-needs-evidence-q01" }, { "text": "Which predecessor parts, tools or maintenance tasks are explicitly approved for reuse on each SJ-100 baseline?", "kind": "boundary", "id": "maintenance-transfer-needs-evidence-q02" } ] } ] }, { "id": "service-evidence-and-corrective-action", "name": "Service evidence and corrective action", "description": "Associate reported defects and corrective measures with the configurations they concern.", "findings": [ { "id": "configuration-specific-reliability", "name": "Configuration-specific reliability", "description": "Separate prototype observations, predecessor fleet experience and SJ-100 service evidence when assessing failure modes and support maturity.", "questions": [ { "text": "Which documented failures concern SJ-100 replacement systems, and what test or service exposure supports their interpretation?", "kind": "provenance", "id": "configuration-specific-reliability-q01" }, { "text": "Which directives or service bulletins require action for the affected configuration, and how is compliance established?", "kind": "action", "id": "configuration-specific-reliability-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": [ "Check the formal boundary between SJ-100, SSJ-New and older Superjet designations before assigning certification or aircraft-type identifiers.", "Certification status, deliveries and commercial service require current verification; intended uses do not establish operational deployment.", "Prototype engine installations can differ from the intended production configuration; the hazards listed are general transport-aircraft hazards, not documented SJ-100 defects." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Yakovlev SJ-100 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": "Manufacturer model designation", "value_or_pattern": "SJ-100", "note": "Identifies the aircraft model, not an individual airframe; certification documents may use a different formal designation." }, { "scheme": "Manufacturer serial number", "value_or_pattern": "An airframe-specific production serial number", "note": "Distinguishes individual aircraft independently of their changeable registration marks." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Yakovlev SJ-100 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": [ "Designed for scheduled regional passenger transport.", "Intended to connect smaller cities with airline hubs.", "Development aircraft support flight testing and certification of replacement systems and engines." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Yakovlev SJ-100 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": "Passenger seating capacity", "typical_range": "Approximately 100, depending on cabin configuration", "unit": "passengers" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Yakovlev SJ-100 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": [ "Engine failure or bird ingestion can reduce available thrust.", "Airframe or engine icing can impair aerodynamic performance or propulsion.", "Failures of flight-control systems or their electrical supplies can degrade controllability.", "Loss of cabin pressurization creates a high-altitude hypoxia hazard.", "Fatigue cracking and corrosion require continuing structural inspection." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Yakovlev SJ-100 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": [ "The programme emphasizes Russian replacement of imported components used in the earlier Superjet.", "Approval for operation outside Russia depends on the destination jurisdiction's certification and operating requirements." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Yakovlev SJ-100 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": "Sukhoi Superjet 100", "difference": "The predecessor aircraft family uses substantial internationally supplied equipment and SaM146 engines; the SJ-100 is the redevelopment intended to substitute Russian systems and PD-8 engines." }, { "name": "PD-8", "difference": "A turbofan engine intended to power the SJ-100, rather than the complete aircraft." }, { "name": "Yakovlev MC-21", "difference": "A larger single-aisle passenger aircraft programme, distinct from the approximately 100-seat regional SJ-100." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Yakovlev SJ-100 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does registry provenance intend the import-substituted SJ-100 derivative or the wider Superjet family, and does an existing world model already cover that scope?", "What is the authoritative SJ-100 aircraft and PD-8 installation approval status as of 2026-09-10, including jurisdiction, limitations and configuration coverage?", "Which approved specifications establish seating, masses, payload-range performance and runway requirements for each SJ-100 baseline?", "Which replacement-system configurations are approved for production, and what evidence establishes component or software interchangeability?", "What SJ-100-specific maintenance instructions, operational experience and corrective-action records are available beyond prototype testing and predecessor fleet evidence?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 27 } }, "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 Yakovlev SJ-100, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to identify the Yakovlev SJ-100 design, distinguish its configurations from earlier Superjets, and determine which capability, approval and support claims apply.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 60 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 looks like has to come from research." ], "relatedModels": [], "standing": "Described in 60 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Yakovlev SJ-100 from another, and a Yakovlev SJ-100 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 Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Yakovlev SJ-100 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 Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Yakovlev SJ-100 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Yakovlev SJ-100 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 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 Yakovlev SJ-100 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 Yakovlev SJ-100 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Yakovlev SJ-100, 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 Yakovlev SJ-100, 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 Yakovlev SJ-100 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 } } } }