{ "model": { "rank": 5821, "code": "thing-q200038", "model_id": "vr.tr.dassault-mirage-2000", "name": "Dassault Mirage 2000", "purpose": "Enable an AI agent to recognise a Dassault Mirage 2000, establish its individual configuration and condition, and determine which inspection, maintenance, movement or use requests its documented status permits.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q200038/", "tier": 2, "score": 64, "payload": { "layer": "wikidata", "aliases": [ "Mirage 2000C", "Mirage 2000B", "Mirage 2000E", "Mirage 2000M", "Mirage 2000BM", "Mirage 2000H", "Mirage 2000TH", "Mirage 2000P", "Mirage 2000DP", "Mirage 2000-5", "Mirage 2000EAD", "Mirage 2000DAD", "Mirage 2000RAD", "Mirage 2000EG", "Mirage 2000BG", "Mirage 2000D/N", "Dassault Mirage 2000D", "Mirage 2000N" ], "aliasCount": 18, "merged": 18, "knownIn": 64, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q200038", "url": "https://www.wikidata.org/wiki/Q200038", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:28:00Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00521322, "turns": 1, "seconds": 15.2, "error": null }, "codex": { "seconds": 96.6, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07b30-b221-7bc3-926b-f935f50f8bc4\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Dassault Mirage 2000\nRegistry id: vr.tr.dassault-mirage-2000\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into thi" } } }, "metaModel": { "id": "THING-Q200038", "registryId": "vr.tr.dassault-mirage-2000", "name": "Dassault Mirage 2000", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q200038/", "model": { "registry_id": "vr.tr.dassault-mirage-2000", "name": "Dassault Mirage 2000", "purpose": "Enable an AI agent to recognise a Dassault Mirage 2000, establish its individual configuration and condition, and determine which inspection, maintenance, movement or use requests its documented status permits.", "definition": "The Dassault Mirage 2000 is a French single-engine, delta-wing, fly-by-wire multirole combat aircraft designed by Dassault Aviation as a fourth-generation successor to the Mirage III/5/F1 family, first flown in 1978 and introduced to French Air Force service in 1984.", "scope_statement": "This model owns the physical aircraft family registered as vr.tr.dassault-mirage-2000 in PHY / PHY.OBJ and the identity, configuration, condition and action constraints of individual airframes, keeping variants and upgrades within this entry.", "in_scope": [ "Mirage 2000 family membership, variant identification and individual airframe identity", "As-built configuration, subsequent conversions and installed equipment", "Airframe, propulsion, flight-control and crew-system condition", "Aircraft-side compatibility of external tanks, pods and other stores", "Maintenance evidence, remaining service life and applicable release restrictions", "Transitions between operational service, maintenance, storage, display and disposal" ], "out_of_scope": [ "Dassault corporate history and aircraft procurement programmes", "Other aircraft families, including Mirage III, Mirage F1, Mirage 4000 and Rafale", "Internal design and independent lifecycle of engines, radars, weapons and removable stores", "Squadron organisation, personnel records and fleet allocation", "Mission planning, targeting, combat tactics and weapon employment", "Airfield infrastructure and airspace management" ], "distinguishing_features": [ "Confirm a manufacturer identity or traceable airframe record naming Mirage 2000; the word Mirage, a painted number or a delta silhouette alone is insufficient.", "Check delta-wing geometry against a documented Mirage 2000 reference; the Mirage F1 has a swept-wing configuration. [Dassault Mirage F1](https://www.dassault-aviation.com/en/passion/aircraft/military-dassault-aircraft/mirage-f1/)", "Check for a single-engine installation; the Mirage 4000 is a separate twin-engine design. [Dassault Mirage 4000](https://www.dassault-aviation.com/en/passion/aircraft/military-dassault-aircraft/mirage-4000/)", "For confusion with earlier Mirage deltas, corroborate the airframe identity with its documented engine installation and fly-by-wire architecture; Dassault identifies fly-by-wire controls as a Mirage 2000 development feature. [Dassault technology history](https://www.dassault-aviation.com/wp-content/blogs.dir/2/files/2016/03/DA100years-CP05.pdf)", "Accept either single-seat or two-seat aircraft as potential family members; seat count narrows identification but does not establish the variant. [Dassault Mirage 2000](https://www.dassault-aviation.com/en/defense/customer-support/operational-aircraft/mirage-2000/)" ], "characteristics": [ { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial linked to dated operator identifiers and registry entry", "why_it_matters": "Keeps maintenance and conversion history attached to the same aircraft when markings or operators change." }, { "name": "Variant and modification standard", "kind": "category", "unit_or_values": "Documented full designation, operator suffix, modification standard and effective date; unknown permitted", "why_it_matters": "Prevents equipment and capabilities from one Mirage 2000 version being assigned to another." }, { "name": "Cockpit arrangement", "kind": "category", "unit_or_values": "Single-seat; two-seat; altered or incomplete; unverified", "why_it_matters": "Supports recognition and determines which crew-system documentation applies." }, { "name": "Installed propulsion", "kind": "relation", "unit_or_values": "Engine model, serial, installation date and applicable configuration record", "why_it_matters": "Separates engine condition and replacement history from airframe identity." }, { "name": "Avionics configuration", "kind": "relation", "unit_or_values": "Installed radar, navigation, communications and other avionics linked to hardware and software standards", "why_it_matters": "A family or upgrade label alone cannot establish the equipment actually present." }, { "name": "Recorded utilisation", "kind": "measurement", "unit_or_values": "Flight hours, landings, cycles and authority-defined fatigue indices, each with date and counting basis", "why_it_matters": "Supports life assessment without treating hours, cycles and fatigue consumption as interchangeable." }, { "name": "Configuration-dependent mass", "kind": "measurement", "unit_or_values": "kg, with weighing or calculation basis, installed equipment and fuel/store state", "why_it_matters": "Makes handling and release assessments specific to the aircraft's actual configuration." }, { "name": "External-station configuration", "kind": "relation", "unit_or_values": "Station-to-pylon, adapter and store assignments with clearance references", "why_it_matters": "Distinguishes physical attachment from documented compatibility." }, { "name": "Technical disposition", "kind": "state", "unit_or_values": "Released with stated scope; restricted; grounded; under maintenance; unassessed", "why_it_matters": "Separates apparent completeness from an authorised technical release." }, { "name": "Lifecycle disposition", "kind": "state", "unit_or_values": "In service; stored; undergoing restoration; display; dismantling; disposed; unknown", "why_it_matters": "Determines which maintenance, preservation and handling expectations apply." } ], "affordances": [ "Match an observed aircraft to a Mirage 2000 identity and flag unresolved variant evidence.", "Compare installed equipment with the documented Mirage 2000 configuration and identify discrepancies.", "Assemble an inspection or maintenance review using documents applicable to the airframe and modification standard.", "Check whether a proposed component or external-store installation has applicable aircraft-side compatibility evidence.", "Assess whether records support towing, transport, storage, display or referral for flight release.", "Record an authorised lifecycle or configuration change while preserving the aircraft's identity and evidence history." ] }, "sources": [ { "id": "placeholder", "title": "Research in progress", "url": "", "what_it_supports": "Will be replaced after lookups" } ], "structure": { "bundles": [ { "id": "mirage-2000-identity", "name": "Mirage 2000 identity", "description": "Establish family membership and distinguish the enduring airframe identity from variant labels and changing markings.", "rationale": "Similar Mirage names and silhouettes cannot establish which aircraft or configuration an agent is examining.", "layers": [ { "id": "family-recognition", "name": "Family recognition", "description": "Combine physical observations with documentary evidence of Mirage 2000 membership.", "findings": [ { "id": "corroborated-family-membership", "name": "Corroborated family membership", "description": "Record the identifying evidence, competing identifications and confidence rather than treating appearance as conclusive.", "questions": [ { "text": "Which manufacturer or operator record identifies this aircraft as a Mirage 2000?", "kind": "provenance", "id": "corroborated-family-membership-q01" }, { "text": "Which observed features support that identification, and which could also fit another Mirage family?", "kind": "boundary", "id": "corroborated-family-membership-q02" } ] } ] }, { "id": "airframe-and-variant-continuity", "name": "Airframe and variant continuity", "description": "Keep serial identity stable through operator changes, upgrades and revised designations.", "findings": [ { "id": "serial-and-designation-history", "name": "Serial and designation history", "description": "Record manufacturer serial, dated markings, full variant designation and documented conversion history.", "questions": [ { "text": "Which serial anchors this airframe, and which dated records connect its successive operator markings?", "kind": "provenance", "id": "serial-and-designation-history-q01" }, { "text": "What evidence establishes its original variant and current modification standard?", "kind": "definition", "id": "serial-and-designation-history-q02" } ] } ] } ] }, { "id": "delta-airframe-and-flight-systems", "name": "Delta airframe and flight systems", "description": "Describe the physical integrity and installed systems needed to assess this Mirage 2000 as an aircraft.", "rationale": "Recognition of the delta airframe does not establish structural integrity or the condition of its propulsion and flight-control systems.", "layers": [ { "id": "structure-and-life-consumption", "name": "Structure and life consumption", "description": "Relate structural findings and repairs to the applicable airframe standard and utilisation history.", "findings": [ { "id": "airframe-integrity-evidence", "name": "Airframe integrity evidence", "description": "Record inspections, damage, repairs and life assessments for the delta wing, fuselage, attachments and landing gear.", "questions": [ { "text": "Which inspection and repair records apply to this serial and its current structural standard?", "kind": "provenance", "id": "airframe-integrity-evidence-q01" }, { "text": "What utilisation and fatigue measures were recorded, when, and under which assessment method?", "kind": "measurement", "id": "airframe-integrity-evidence-q02" } ] } ] }, { "id": "propulsion-and-control-installation", "name": "Propulsion and control installation", "description": "Establish the installed engine and flight-control configuration and their documented condition.", "findings": [ { "id": "engine-and-control-status", "name": "Engine and control status", "description": "Link engine identity and flight-control equipment to applicable test results, defects and restrictions.", "questions": [ { "text": "Which engine and flight-control equipment standards are installed, and what records verify them?", "kind": "provenance", "id": "engine-and-control-status-q01" }, { "text": "Which unresolved engine, control, electrical or hydraulic findings restrict maintenance release or movement?", "kind": "action", "id": "engine-and-control-status-q02" } ] } ] } ] }, { "id": "variant-equipment-and-crew", "name": "Variant equipment and crew", "description": "Resolve what this Mirage 2000 actually contains and what its cockpit arrangement supports.", "rationale": "The family includes different cockpit arrangements and equipment standards; capability cannot be inherited indiscriminately from the family name.", "layers": [ { "id": "avionics-standard", "name": "Avionics standard", "description": "Distinguish advertised variant equipment from installed and serviceable equipment.", "findings": [ { "id": "installed-avionics-baseline", "name": "Installed avionics baseline", "description": "Record radar and other avionics identities, software standards, modification evidence and known limitations.", "questions": [ { "text": "Which radar and avionics configuration is documented for this airframe today?", "kind": "definition", "id": "installed-avionics-baseline-q01" }, { "text": "Which claimed functions depend on equipment or software whose installation or serviceability remains unverified?", "kind": "boundary", "id": "installed-avionics-baseline-q02" } ] } ] }, { "id": "cockpit-and-crew-systems", "name": "Cockpit and crew systems", "description": "Record seat arrangement and the installed systems supporting each occupied crew station.", "findings": [ { "id": "crew-station-configuration", "name": "Crew-station configuration", "description": "Establish each station's documented role, installed controls and life-support and escape-system status.", "questions": [ { "text": "How many crew stations are fitted, and what role and controls does the applicable variant documentation assign to each?", "kind": "definition", "id": "crew-station-configuration-q01" }, { "text": "What current maintenance evidence establishes the status of the canopy, escape and life-support systems?", "kind": "provenance", "id": "crew-station-configuration-q02" } ] } ] } ] }, { "id": "external-stations-and-servicing", "name": "External stations and servicing", "description": "Capture aircraft-side installation compatibility and support interfaces for the actual Mirage 2000 configuration.", "rationale": "A store, tank or support device associated with one Mirage 2000 standard is not automatically compatible with every airframe.", "layers": [ { "id": "station-installation-compatibility", "name": "Station installation compatibility", "description": "Relate each fitted external item to its station, attachment hardware and applicable clearance.", "findings": [ { "id": "documented-store-fit", "name": "Documented store fit", "description": "Record installed external tanks, pods and other stores without inferring compatibility from photographs or family-level lists.", "questions": [ { "text": "What is fitted at each station, including pylons and adapters, and when was that configuration verified?", "kind": "measurement", "id": "documented-store-fit-q01" }, { "text": "Which clearance covers this combination on this variant and modification standard?", "kind": "provenance", "id": "documented-store-fit-q02" } ] } ] }, { "id": "fuel-and-ground-support-interfaces", "name": "Fuel and ground-support interfaces", "description": "Identify fitted refuelling equipment and the documentation governing servicing and ground handling.", "findings": [ { "id": "verified-support-compatibility", "name": "Verified support compatibility", "description": "Record aircraft-side fuel, power, towing and lifting interfaces with references to applicable Mirage 2000 instructions.", "questions": [ { "text": "Which refuelling equipment and servicing interfaces are fitted and documented on this aircraft?", "kind": "definition", "id": "verified-support-compatibility-q01" }, { "text": "Which approved instructions and compatible support equipment govern the proposed servicing or ground movement?", "kind": "action", "id": "verified-support-compatibility-q02" } ] } ] } ] }, { "id": "mirage-2000-release-and-lifecycle", "name": "Mirage 2000 release and lifecycle", "description": "Connect configuration and condition evidence to bounded permissions throughout service, storage and preservation.", "rationale": "A complete-looking Mirage 2000 may be grounded, preserved or demilitarised, and an upgrade designation does not itself establish readiness.", "layers": [ { "id": "configuration-specific-release", "name": "Configuration-specific release", "description": "Assess release evidence against the aircraft's current equipment, defects and intended activity.", "findings": [ { "id": "bounded-technical-permission", "name": "Bounded technical permission", "description": "Record the issuing authority, scope, validity and restrictions of technical releases; keep agent assessment distinct from authorised sign-off.", "questions": [ { "text": "Which current release or restriction applies to this serial, equipment state and proposed activity?", "kind": "provenance", "id": "bounded-technical-permission-q01" }, { "text": "Which missing records, overdue tasks or unresolved defects require withholding a recommendation and referring the decision to the responsible authority?", "kind": "action", "id": "bounded-technical-permission-q02" } ] } ] }, { "id": "storage-display-and-return", "name": "Storage, display and return", "description": "Track changes that affect whether the aircraft can be maintained, moved, displayed or considered for return to service.", "findings": [ { "id": "preservation-and-removal-history", "name": "Preservation and removal history", "description": "Record preservation work, removed equipment, substitutions and demilitarisation evidence without assuming that an intact exterior implies an intact aircraft.", "questions": [ { "text": "Which systems or structural elements were removed, substituted, inhibited or altered during storage or preparation for display?", "kind": "provenance", "id": "preservation-and-removal-history-q01" }, { "text": "What inspections, restoration evidence and authorised decisions are required before the proposed lifecycle transition?", "kind": "action", "id": "preservation-and-removal-history-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Mirage 2000C (single-seat air-defence interceptor)", "Mirage 2000B (two-seat conversion trainer)", "Mirage 2000N (nuclear-strike, ASMP missile)", "Mirage 2000D (conventional all-weather strike, derived from 2000N)", "Mirage 2000-5 / 2000-5F (multirole upgrade with RDY radar and MICA)", "Mirage 2000-5 Mk2 / 2000-9 (export, glass cockpit, improved avionics)", "Mirage 2000E / 2000H / 2000I / 2000-5EI (export fighter and dual-seat variants)", "Mirage 2000-5EDA / 2000EG / 2000P (operator-specific export batches)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Dassault Mirage 2000 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own the Mirage 2000 concept, requiring this registry entry to link to it rather than introduce a duplicate?", "Which authoritative designation and conversion records establish the boundaries among French variants, export suffixes and operator-specific upgrade standards?", "Which controlled maintenance and airworthiness documents can be consulted to establish variant-specific life measures, inspection requirements and release criteria?", "Which sources can reliably establish an individual airframe's current engine, avionics, software and external-station clearances when public descriptions cover only a family or fleet?", "How should incomplete aircraft, prototypes, reconstructed museum exhibits and demilitarised examples retain Mirage 2000 identity, and what evidence defines their action restrictions?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 11, "questions": 21 } }, "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 Dassault Mirage 2000, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a Dassault Mirage 2000, establish its individual configuration and condition, and determine which inspection, maintenance, movement or use requests its documented status permits.", "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: Mirage 2000C, Mirage 2000B, Mirage 2000E, Mirage 2000M, Mirage 2000BM, Mirage 2000H, Mirage 2000TH, Mirage 2000P, Mirage 2000DP, Mirage 2000-5, Mirage 2000EAD, Mirage 2000DAD.", "18 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 64 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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": [ "Mirage 2000C", "Mirage 2000B", "Mirage 2000E", "Mirage 2000M", "Mirage 2000BM", "Mirage 2000H", "Mirage 2000TH", "Mirage 2000P", "Mirage 2000DP", "Mirage 2000-5", "Mirage 2000EAD", "Mirage 2000DAD" ] } ], "standing": "Described in 64 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 18 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 Dassault Mirage 2000 from another, and a Dassault Mirage 2000 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 Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Dassault Mirage 2000 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 Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Dassault Mirage 2000 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Dassault Mirage 2000 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 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 Dassault Mirage 2000 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 Dassault Mirage 2000 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Dassault Mirage 2000, 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 Dassault Mirage 2000, 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 Dassault Mirage 2000 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 } } } }