{ "model": { "rank": 2558, "code": "thing-q5830", "model_id": "vr.tr.airbus-a380", "name": "Airbus A380", "purpose": "Enable an AI agent to recognise an Airbus A380, assess a particular aircraft's configuration and evidenced condition, and identify actions supported by its limitations, maintenance status and operating context.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q5830/", "tier": 2, "score": 102, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 102, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q5830", "url": "https://www.wikidata.org/wiki/Q5830", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:00:51Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.0376171, "turns": 2, "seconds": 148.1, "error": null }, "codex": { "seconds": 101.7, "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: 01a07b4d-fe5c-7b81-a213-93fd99c5ce41\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Airbus A380\nRegistry id: vr.tr.airbus-a380\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA" } } }, "metaModel": { "id": "THING-Q5830", "registryId": "vr.tr.airbus-a380", "name": "Airbus A380", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5830/", "model": { "registry_id": "vr.tr.airbus-a380", "name": "Airbus A380", "purpose": "Enable an AI agent to recognise an Airbus A380, assess a particular aircraft's configuration and evidenced condition, and identify actions supported by its limitations, maintenance status and operating context.", "definition": "A four-turbofan, full-length double-deck, twin-aisle transport-category aeroplane type produced by Airbus S.A.S. as the A380-800 series (EASA models A380-841, A380-842 and A380-861), type-certified as a Large Aeroplane and the largest passenger aircraft placed in commercial service.", "scope_statement": "Own the A380-specific model attached to vr.tr.airbus-a380 in PHY / PHY.OBJ, distinguishing aircraft-type facts from the identity, configuration, condition and constraints of individual airframes; reference authoritative operational decisions rather than issuing them.", "in_scope": [ "A380 identity, documented variant and individual airframe identification", "Two-deck cabin configuration, installed engines and applicable modifications", "Aircraft-specific mass, balance, loading and performance constraints", "Compatibility with airport movement areas, stands and servicing equipment", "Condition, maintenance evidence, operating restrictions and lifecycle transitions" ], "out_of_scope": [ "Airbus corporate organisation and aircraft programme economics", "Airline schedules, ticket sales and fleet profitability", "Airport infrastructure as independently maintained assets", "Engine and component internal engineering beyond aircraft installation interfaces", "Crew qualifications, air traffic control and flight execution procedures" ], "distinguishing_features": [ "Require manufacturer and type documentation identifying an A380; livery, airline name or a booking description cannot establish aircraft identity.", "Check for two full-length passenger decks, distinguishing the A380 from aircraft with only a partial upper passenger deck. [Airbus A380](https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft/a380)", "Check for four installed engine positions alongside the full-length double-deck arrangement; engine count alone does not identify an A380. [Airbus A380](https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft/a380)", "Use the published 79.8 m wingspan and 72.7 m overall length as corroborating geometry, with configuration and measurement provenance recorded. [Airbus facts and figures](https://www.airbus.com/sites/g/files/jlcbta136/files/2021-12/EN-Airbus-A380-Facts-and-Figures-December-2021_0.pdf)", "Separate an actual aircraft configuration from proposed enhancements: an A380plus reference alone establishes a development-study association, not an installed modification. [Airbus A380plus announcement](https://www.airbus.com/en/newsroom/press-releases/2017-06-airbus-presents-the-a380plus)" ], "characteristics": [ { "name": "Identity and variant evidence", "kind": "relation", "unit_or_values": "Manufacturer serial number, registration history, documented model designation and supporting records", "why_it_matters": "Connects observations and limitations to the correct A380 airframe." }, { "name": "Passenger-deck configuration", "kind": "category", "unit_or_values": "Dated main-deck and upper-deck layout references, including seating, stairs, exits and service spaces", "why_it_matters": "Determines usable accommodation and the applicability of cabin access and occupancy constraints." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine model, serial number, rating and installation position for each of four positions", "why_it_matters": "Determines which performance, maintenance and compatibility evidence applies." }, { "name": "Aircraft mass and loading limits", "kind": "measurement", "unit_or_values": "kg for actual and permitted masses, with configuration, flight phase and document revision", "why_it_matters": "Prevents family-level headline weights from replacing the limits of a particular aircraft." }, { "name": "Centre of gravity", "kind": "measurement", "unit_or_values": "% mean aerodynamic chord or approved datum-based units, with loading case and permitted envelope", "why_it_matters": "Supports evaluation of combined passenger-deck, cargo and fuel loading." }, { "name": "Ground clearance envelope", "kind": "measurement", "unit_or_values": "m for dimensions and clearances, with steering, towing and aircraft configuration assumptions", "why_it_matters": "Supports assessment of A380 movement paths, stands and servicing positions." }, { "name": "Maintenance exposure", "kind": "measurement", "unit_or_values": "Flight hours, flight cycles and calendar time, with component or airframe applicability", "why_it_matters": "Makes inspection and life-limit evidence interpretable." }, { "name": "Dispatch evidence status", "kind": "state", "unit_or_values": "Unassessed, evidence incomplete, restricted, released for specified operation, or prohibited; with issuer and validity", "why_it_matters": "Distinguishes observed condition from an authorised, time-bounded release." }, { "name": "Airport compatibility assessment", "kind": "relation", "unit_or_values": "Aircraft configuration linked to airport, runway, taxi route, stand and assessment conditions", "why_it_matters": "Prevents airport-level acceptance from implying that every route and stand is suitable." }, { "name": "Lifecycle condition", "kind": "state", "unit_or_values": "Operating, under maintenance, stored, undergoing reactivation, withdrawn, or dismantling", "why_it_matters": "Determines which evidence and authorisations are needed before a proposed transition." } ], "affordances": [ "Identify an A380 airframe and reconcile conflicting registration, variant or configuration records.", "Determine which approved manuals, limitations and maintenance requirements apply to its installed configuration.", "Screen a proposed airport, taxi route, stand and turnaround arrangement for unresolved A380 compatibility constraints.", "Evaluate a proposed two-deck passenger and cargo loading case against documented mass and balance limits.", "Assemble condition and maintenance evidence for review by authorised personnel before dispatch or return to service.", "Assess readiness for a cabin change, engine replacement, storage transition or reactivation and identify missing prerequisites." ] }, "sources": [ { "id": "easa-tcds-a110", "title": "Type-Certificate Data Sheet No. EASA.A.110 - Airbus A380", "url": "https://www.easa.europa.eu/en/downloads/7309/en", "what_it_supports": "Certified models A380-841/-842 and A380-861, holder Airbus S.A.S., Large Aeroplanes category, JAR 25 certification basis, engine fit, weight variants, usable fuel, and maximum approved evacuation seating (868).", "url_status": "unverified" }, { "id": "easa-tc-page", "title": "EASA.A.110 - Airbus A380 (type certificate record, Issue 17)", "url": "https://www.easa.europa.eu/en/document-library/type-certificates/aircraft-cs-25-cs-22-cs-23-cs-vla-cs-lsa/easaa110-airbus-a380", "what_it_supports": "Current EASA type-certificate identity, CS-25 product class, and TCDS issue status.", "url_status": "unverified" }, { "id": "airbus-a380-product", "title": "Airbus A380 (product page)", "url": "https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft/a380", "what_it_supports": "Manufacturer description as the largest passenger aircraft, dimensions, 853 maximum seating, Trent 900 or GP7000 engines, 251 deliveries to 14 customers, and 25 October 2007 entry into service with Singapore Airlines.", "url_status": "live" }, { "id": "airbus-passenger-family", "title": "Passenger aircraft | Airbus", "url": "https://www.airbus.com/en/products-services/commercial-aircraft/passenger-aircraft", "what_it_supports": "Production has ended; 8,000 nm maximum range, 853 maximum passengers, 251 aircraft delivered; Airbus continues in-service support.", "url_status": "live" }, { "id": "airbus-a380-20th", "title": "Happy 20th anniversary, A380!", "url": "https://www.airbus.com/en/newsroom/stories/2025-04-happy-20th-anniversary-a380", "what_it_supports": "First flight 27 April 2005 (MSN001, Toulouse); about 180 still in service in 2025; more than 800,000 flights and 300 million passengers carried.", "url_status": "live" }, { "id": "wikidata-q5830", "title": "Airbus A380 (Q5830)", "url": "https://www.wikidata.org/wiki/Q5830", "what_it_supports": "Wikidata item, classing as a wide-body double-deck four-engine aircraft family, principal dimensions, service entry date, and total produced.", "url_status": "live" }, { "id": "flugzeuginfo-a380", "title": "Airbus A380 - Specifications - Technical Data / Description", "url": "https://www.flugzeuginfo.net/acdata_php/acdata_a380_en.php", "what_it_supports": "ICAO type A388, IATA type 380, FAA TCDS A58NM, EASA TCDS A.110, and compiled performance figures for the A380-800.", "url_status": "live" }, { "id": "faa-sc-25-832", "title": "Special Conditions: Airbus SAS Model A380-800 Series Airplanes; Electronic System Security Protection From Unauthorized External Access", "url": "https://www.federalregister.gov/documents/2022/11/25/2022-25633/special-conditions-airbus-sas-model-a380-800-series-airplanes-electronic-system-security-protection", "what_it_supports": "FAA transport-category basis (14 CFR Part 25) and Type Certificate A58NM; states maximum passenger seating 868 and MTOW band for the A380-800 series.", "url_status": "live" } ], "structure": { "bundles": [ { "id": "a380-identity-and-applicability", "name": "A380 identity and applicability", "description": "Establish which A380 is represented and which technical baseline governs it.", "rationale": "A family name cannot determine the configuration or limitations of an individual aircraft.", "layers": [ { "id": "type-and-airframe-identity", "name": "Type and airframe identity", "description": "Separate registry concept, documented aircraft model and individual airframe.", "findings": [ { "id": "documented-a380-identity", "name": "Documented A380 identity", "description": "Record evidence connecting the airframe to the A380 registry entry, treating visual recognition as corroboration.", "questions": [ { "text": "Which manufacturer record identifies this aircraft's serial number and exact model designation?", "kind": "provenance", "id": "documented-a380-identity-q01" }, { "text": "Does the record describe an aircraft type, a particular airframe, a simulator or a proposed design?", "kind": "boundary", "id": "documented-a380-identity-q02" } ] } ] }, { "id": "configuration-effectivity", "name": "Configuration effectivity", "description": "Connect the installed A380 configuration to the documents that apply to it.", "findings": [ { "id": "applicable-technical-baseline", "name": "Applicable technical baseline", "description": "Record variant, modification status and document effectivity together, including conflicting or missing evidence.", "questions": [ { "text": "Which installed modifications affect this A380's cabin, engines, mass limits or airport interfaces?", "kind": "definition", "id": "applicable-technical-baseline-q01" }, { "text": "Which approved document revisions explicitly apply to this serial number and modification state?", "kind": "provenance", "id": "applicable-technical-baseline-q02" } ] } ] } ] }, { "id": "double-deck-accommodation-and-loading", "name": "Double-deck accommodation and loading", "description": "Represent the usable passenger decks and their relationship to exits, cargo and aircraft balance.", "rationale": "An A380's capacity and loading constraints depend on its installed layout across both passenger decks.", "layers": [ { "id": "deck-layout-and-access", "name": "Deck layout and access", "description": "Describe each passenger deck and the connections and exits available in the current configuration.", "findings": [ { "id": "installed-two-deck-layout", "name": "Installed two-deck layout", "description": "Record actual seating, service spaces, stairs and exit availability without substituting advertised family capacity.", "questions": [ { "text": "What approved layout is installed on each passenger deck, and when was it verified?", "kind": "provenance", "id": "installed-two-deck-layout-q01" }, { "text": "How do unavailable seats, stairs, doors or cabin facilities affect permitted occupancy and boarding arrangements?", "kind": "action", "id": "installed-two-deck-layout-q02" } ] } ] }, { "id": "distributed-payload-and-balance", "name": "Distributed payload and balance", "description": "Relate passenger zones, cargo compartments and fuel to the applicable aircraft loading envelope.", "findings": [ { "id": "configuration-specific-load-case", "name": "Configuration-specific load case", "description": "Record a dated load case with deck and compartment distribution, actual masses and applicable limits.", "questions": [ { "text": "What passenger, baggage, cargo and fuel distribution produces the proposed mass and centre of gravity?", "kind": "measurement", "id": "configuration-specific-load-case-q01" }, { "text": "Which aircraft-specific limits constrain this load case, including local loading limits?", "kind": "boundary", "id": "configuration-specific-load-case-q02" }, { "text": "What changes or authorised review are required when a loading limit is exceeded or unknown?", "kind": "action", "id": "configuration-specific-load-case-q03" } ] } ] } ] }, { "id": "four-engine-and-system-configuration", "name": "Four-engine and system configuration", "description": "Represent installed propulsion and the aircraft-system dependencies relevant to interpreting defects.", "rationale": "A380 configuration and defect assessment require position-specific engine evidence and applicable system dependencies.", "layers": [ { "id": "engine-installations", "name": "Engine installations", "description": "Identify the engine and associated installation baseline at each position.", "findings": [ { "id": "position-specific-propulsion", "name": "Position-specific propulsion", "description": "Associate each installed engine with its identity, approved rating, installation evidence and relevant restrictions.", "questions": [ { "text": "Which engine model, serial number and approved rating is installed at each of the four positions?", "kind": "definition", "id": "position-specific-propulsion-q01" }, { "text": "Which records establish installation compatibility and the applicability of engine-related restrictions?", "kind": "provenance", "id": "position-specific-propulsion-q02" } ] } ] }, { "id": "system-dependencies-and-defects", "name": "System dependencies and defects", "description": "Connect reported defects to affected functions using the applicable A380 technical baseline.", "findings": [ { "id": "combined-defect-assessment", "name": "Combined defect assessment", "description": "Record interactions among propulsion, electrical, hydraulic, flight-control and other relevant defects rather than inferring availability from engine count.", "questions": [ { "text": "Which functions and remaining capabilities are affected by the currently reported combination of defects?", "kind": "boundary", "id": "combined-defect-assessment-q01" }, { "text": "Which applicable approved instructions govern assessment, rectification or permitted deferral of that combination?", "kind": "provenance", "id": "combined-defect-assessment-q02" }, { "text": "What authorised decision is required before the aircraft's operating status can change?", "kind": "action", "id": "combined-defect-assessment-q03" } ] } ] } ] }, { "id": "a380-airport-and-turnaround-fit", "name": "A380 airport and turnaround fit", "description": "Evaluate the aircraft's fit with a specific movement path, parking position and servicing arrangement.", "rationale": "A380 geometric clearance, pavement compatibility and two-deck access must be resolved for the actual airport arrangement.", "layers": [ { "id": "movement-and-stand-compatibility", "name": "Movement and stand compatibility", "description": "Connect aircraft geometry and loading to the proposed runway, taxi route and stand.", "findings": [ { "id": "assessed-ground-path", "name": "Assessed ground path", "description": "Record an assessed path with clearances, pavement conditions and operational restrictions.", "questions": [ { "text": "Which assessed runway, taxi route and stand accommodate this A380 configuration and operating mass?", "kind": "provenance", "id": "assessed-ground-path-q01" }, { "text": "What wingtip, tail, engine and turning clearances constrain the proposed movement?", "kind": "measurement", "id": "assessed-ground-path-q02" }, { "text": "Which restrictions or unresolved compatibility issues prevent acceptance of the proposed path?", "kind": "boundary", "id": "assessed-ground-path-q03" } ] } ] }, { "id": "two-deck-servicing", "name": "Two-deck servicing", "description": "Describe compatible passenger access and ground-service equipment for the installed configuration.", "findings": [ { "id": "supported-turnaround-arrangement", "name": "Supported turnaround arrangement", "description": "Record how passengers, cargo and services reach their intended interfaces, including any restricted access.", "questions": [ { "text": "Which doors and decks will be served by each bridge, stair, loader or service vehicle?", "kind": "definition", "id": "supported-turnaround-arrangement-q01" }, { "text": "What equipment compatibility and positioning evidence supports the proposed servicing arrangement?", "kind": "provenance", "id": "supported-turnaround-arrangement-q02" }, { "text": "What approved alternative is available if direct upper-deck access or another planned interface is unavailable?", "kind": "action", "id": "supported-turnaround-arrangement-q03" } ] } ] } ] }, { "id": "a380-condition-and-operating-readiness", "name": "A380 condition and operating readiness", "description": "Connect observed condition, maintenance obligations and configuration-specific operating evidence.", "rationale": "Recognising an A380 and knowing its nominal capabilities does not establish that a particular aircraft is ready for a proposed operation.", "layers": [ { "id": "airframe-condition-and-obligations", "name": "Airframe condition and obligations", "description": "Track significant structural and system findings against the applicable A380 maintenance requirements.", "findings": [ { "id": "evidenced-maintenance-state", "name": "Evidenced maintenance state", "description": "Record inspection results, repairs and outstanding requirements with location, effectivity and validity.", "questions": [ { "text": "Which applicable inspections, directives and life-limited items are due given this airframe's hours, cycles and calendar exposure?", "kind": "provenance", "id": "evidenced-maintenance-state-q01" }, { "text": "What unresolved findings affect the wings, fuselage, landing gear or double-deck cabin structure?", "kind": "definition", "id": "evidenced-maintenance-state-q02" }, { "text": "Which findings require rectification, further inspection or an authorised restriction?", "kind": "action", "id": "evidenced-maintenance-state-q03" } ] } ] }, { "id": "operation-specific-readiness", "name": "Operation-specific readiness", "description": "Represent the evidence supporting an operating decision for a particular aircraft and set of conditions.", "findings": [ { "id": "bounded-operating-decision", "name": "Bounded operating decision", "description": "Link operating status to aircraft configuration, loading, conditions, approved performance evidence and the responsible authority.", "questions": [ { "text": "Which approved performance assessment applies to this A380's engines, mass, configuration and proposed operating conditions?", "kind": "provenance", "id": "bounded-operating-decision-q01" }, { "text": "What restrictions and validity conditions accompany the recorded maintenance release and operating decision?", "kind": "boundary", "id": "bounded-operating-decision-q02" }, { "text": "Which changes in defects, loading, weather or airport availability require the decision to be reassessed?", "kind": "action", "id": "bounded-operating-decision-q03" } ] } ] } ] }, { "id": "a380-modification-storage-and-return", "name": "A380 modification, storage and return", "description": "Represent changes that alter the aircraft's technical baseline or readiness after inactivity.", "rationale": "Cabin retrofits, installation changes and storage can invalidate previously applicable A380 configuration and readiness evidence.", "layers": [ { "id": "configuration-change-acceptance", "name": "Configuration change acceptance", "description": "Track the effects and acceptance evidence of changes to the installed aircraft.", "findings": [ { "id": "accepted-a380-modification", "name": "Accepted A380 modification", "description": "Connect a modification to its approved applicability, embodiment evidence and updated aircraft records.", "questions": [ { "text": "Does the proposed cabin, engine or other modification have approved applicability to this A380 airframe?", "kind": "boundary", "id": "accepted-a380-modification-q01" }, { "text": "Which completion records establish what was actually installed and accepted?", "kind": "provenance", "id": "accepted-a380-modification-q02" }, { "text": "Which mass, balance, cabin, maintenance or airport-interface records must be revised before further use?", "kind": "action", "id": "accepted-a380-modification-q03" } ] } ] }, { "id": "preservation-and-reactivation", "name": "Preservation and reactivation", "description": "Represent storage exposure, preservation evidence and prerequisites for return to service.", "findings": [ { "id": "evidenced-return-to-service", "name": "Evidenced return to service", "description": "Record preservation and reactivation status across the airframe, four engine installations and both passenger decks.", "questions": [ { "text": "What storage duration, environment, preservation actions and removed equipment are documented?", "kind": "provenance", "id": "evidenced-return-to-service-q01" }, { "text": "Which applicable A380 reactivation tasks and acceptance checks remain incomplete?", "kind": "definition", "id": "evidenced-return-to-service-q02" }, { "text": "What evidence and authorised release are required before the intended return-to-service operation?", "kind": "action", "id": "evidenced-return-to-service-q03" } ] } ] } ] }, { "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": [ "A380-800 (the only series produced and delivered)", "A380-841 (Rolls-Royce Trent 970)", "A380-842 (Rolls-Royce Trent 972 / 972E)", "A380-861 (Engine Alliance GP7270)", "Certified weight variants (TCDS variants with MTOW from about 560 t to 575 t)", "A380-800F / A380F (freighter; launched then cancelled, none delivered)", "A380plus (2017 upgrade proposal with winglets and higher MTOW; not produced)", "A380-900 (proposed stretch; not launched)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q5830", "note": "Item for the Airbus A380 aircraft family." }, { "scheme": "ICAO aircraft type designator (Doc 8643)", "value_or_pattern": "A388", "note": "Type designator used in flight plans and surveillance for the A380-800." }, { "scheme": "IATA aircraft type code", "value_or_pattern": "380", "note": "SSIM/schedule type code; not the same string as the ICAO designator." }, { "scheme": "EASA type certificate", "value_or_pattern": "EASA.A.110", "note": "Covers models A380-841, A380-842 and A380-861; holder Airbus S.A.S., Blagnac." }, { "scheme": "FAA type certificate", "value_or_pattern": "A58NM", "note": "US type certificate for the Airbus A380-800 series." }, { "scheme": "Airbus certified model", "value_or_pattern": "A380-841 | A380-842 | A380-861", "note": "TCDS models: 841/842 are Rolls-Royce Trent 900; 861 is Engine Alliance GP7270. Marketing name of the produced series is A380-800." }, { "scheme": "Airbus manufacturer serial number (MSN)", "value_or_pattern": "integer MSN unique to each airframe", "note": "Production identity used in delivery, continuing airworthiness and retirement records (e.g. flight-test MSN001)." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "EASA Type-Certificate Data Sheet EASA.A.110 (European Union Aviation Safety Agency) - airworthiness definition of the type.", "Certification basis JAR 25 Change 15, with JAR 1 Change 5 and JAR AWO Change 2 for autoland (Joint Aviation Authorities / taken up by EASA) - original Large Aeroplane airworthiness standard for the type.", "EASA CS-25 Large Aeroplanes (European Union Aviation Safety Agency) - current European large-aeroplane certification specification under which the type certificate is maintained.", "FAA Type Certificate A58NM and 14 CFR Part 25 (Federal Aviation Administration) - US transport-category certification of the A380-800 series.", "FAA Special Conditions No. 25-832-SC (Federal Aviation Administration) - electronic-system security protection from unauthorized external access on A380-800 series changes.", "EASA engine type certificates E.012 (Rolls-Royce RB211 Trent 900) and IM.E.026 (Engine Alliance GP7270) - approved powerplants listed on the airframe TCDS.", "ICAO aerodrome reference code F practice (ICAO Annex 14, as applied by airport authorities) - operations constrained by a geometric wingspan of about 79.8 m, at the Code F limit of 80 m." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Scheduled long-haul, high-capacity passenger service on trunk routes between congested mega-hubs; entered commercial service on 25 October 2007 with Singapore Airlines.", "251 aircraft delivered to 14 customers; serial production has ended (last deliveries in 2021). Airbus continues to support the in-service fleet; about 180 remained in service in 2025.", "Cabin use is operator-specific: typical airline layouts around 525 seats in three classes or about 544 in four classes, versus a certified high-density maximum of 853 (evacuation approval up to 868).", "Some airframes fly as VIP, government or private configurations; Airbus also uses A380 airframes as a FlightLab for propulsion and systems trials.", "Ground operations are Code F: the type needs wide runways, taxiways, gates and pavement bearing suitable for a ~80 m span and MTOW around 560-575 t." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "overall length", "typical_range": "72.72-73", "unit": "m" }, { "quantity": "wingspan (geometric)", "typical_range": "79.75-79.8", "unit": "m" }, { "quantity": "height", "typical_range": "24.09-24.1", "unit": "m" }, { "quantity": "reference wing area", "typical_range": "845", "unit": "m²" }, { "quantity": "maximum take-off weight (certified weight variants)", "typical_range": "560-575", "unit": "t" }, { "quantity": "maximum landing weight", "typical_range": "386-395", "unit": "t" }, { "quantity": "usable fuel capacity", "typical_range": "310000-324339", "unit": "L" }, { "quantity": "design range with typical passenger load", "typical_range": "8000 (about 14800-15400 km)", "unit": "nmi" }, { "quantity": "maximum operating Mach number (Mmo)", "typical_range": "0.89", "unit": "Mach" }, { "quantity": "take-off thrust per engine (certified ratings)", "typical_range": "311-357", "unit": "kN" }, { "quantity": "approved passenger seating (marketing max vs TCDS evacuation)", "typical_range": "853-868", "unit": "persons" }, { "quantity": "typical airline seating (3- or 4-class)", "typical_range": "525-544", "unit": "persons" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Engine failure on take-off or go-around: the TCDS allows take-off thrust to be held for 10 minutes in the engine-out case; remaining three-engine performance and continued-airworthiness of the Trent 900 or GP7270 installation is a primary hazard class.", "Two-deck emergency evacuation of up to 868 occupants (TCDS: 330 upper deck, 538 main deck), with stair and door-arrangement constraints and a large minimum cabin-crew complement.", "Airport incompatibility and ground damage: 79.8 m span sits at the ICAO Code F limit; wingtip, gate, taxiway and pavement overloading are operational hazards at airports not built for the type.", "Weight-limit exceedance: multiple certified weight variants (MTOW, MLW, MZFW) mean a given airframe may be legally lighter than the family maximum; using the wrong variant limits is an operational failure mode.", "Fuel-system complexity: many wing tanks plus a large trim tank (TCDS usable fuel on the order of 324 000 L) create imbalance, unusable-fuel and centre-of-gravity hazards if transfer fails.", "Avionics network exposure: FAA special conditions for the A380-800 address unauthorized external access to previously isolated electronic assets.", "Economic withdrawal: four-engine fuel burn and high empty weight made the type uncompetitive on thinner long-haul routes, driving production shutdown and early retirements - a commercial failure mode, not an airworthiness one." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "English-language marketing and press often use Superjumbo; Wikidata records the Chinese label 空中巴士A380.", "Engine choice is operator-specific: Rolls-Royce Trent 900 (A380-841/-842) versus Engine Alliance GP7270 (A380-861), which splits spares, shop visits and noise/emissions paperwork.", "Fleet geography is highly skewed: Emirates took a large share of deliveries and still uses the type as a flagship; several European carriers stored or retired A380s after the COVID traffic collapse; no US major ever ordered the type, so US contact is mainly foreign-carrier arrivals at a few Code F gateways.", "ICAO flight-plan type is A388 while IATA schedules use 380; mixing the two codes is a common documentation error." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Boeing 747-8 Intercontinental", "difference": "Both are four-engine passenger jumbos; the 747-8 has only a partial upper deck and a lower certified passenger maximum, whereas the A380 has two full-length passenger decks and a larger cabin (Airbus states 550 m² of cabin area)." }, { "name": "Airbus A350-1000", "difference": "Same maker's current long-haul flagship; it is a twin-engine, single-deck widebody still in production, with far lower maximum seating than the out-of-production four-engine A380." }, { "name": "Boeing 777-300ER / 777-9", "difference": "High-capacity long-haul twins on similar city pairs; two engines and one passenger deck versus the A380's four engines and two full-length decks." }, { "name": "Airbus A340-600", "difference": "Earlier four-engine Airbus widebody; single passenger deck, much lower capacity, and a different type certificate - not a double-deck type." }, { "name": "Antonov An-225 Mriya", "difference": "Larger overall cargo transport, not a certified passenger airliner; the A380 is the largest passenger aircraft, not the largest aeroplane ever flown." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Airbus A380 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own the A380 concept or aircraft-level bundles that this registry entry should reference?", "Should this entry encompass proposed and unbuilt A380 derivatives as historical configurations, or only documented physical aircraft, without creating new registry entries?", "Which authoritative type-design records establish the exact variant, engine-installation and weight-option boundaries to represent?", "Which approved, revision-controlled maintenance, loading and operating documents can agents access to assess applicability without relying on public headline specifications?", "What evidence freshness, authorised sign-off and conflict-resolution rules are required before recorded condition may support a proposed aircraft action?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 20, "questions": 40 } }, "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 Airbus A380, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an Airbus A380, assess a particular aircraft's configuration and evidenced condition, and identify actions supported by its limitations, maintenance status and operating context.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 102 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 Airbus A380, 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 Airbus A380 looks like has to come from research." ], "relatedModels": [], "standing": "Described in 102 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 Airbus A380 from another, and a Airbus A380 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 Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Airbus A380 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 Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Airbus A380 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Airbus A380 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 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 Airbus A380 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 Airbus A380 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Airbus A380, 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 Airbus A380, 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 Airbus A380 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 } } } }