{ "model": { "rank": 5666, "code": "thing-q6423", "model_id": "vr.tr.boeing-767", "name": "Boeing 767", "purpose": "Enable an AI agent to recognise a Boeing 767, establish its individual configuration and condition, and assess whether proposed operation, loading, maintenance or modification is supported by applicable evidence.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q6423/", "tier": 2, "score": 65, "payload": { "layer": "wikidata", "aliases": [ "KC-767", "Boeing 767-200", "Boeing 767-300", "Boeing 767-400ER", "Boeing 767-200SF", "Boeing 767-200BDSF", "Boeing 767-200PC" ], "aliasCount": 7, "merged": 7, "knownIn": 65, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q6423", "url": "https://www.wikidata.org/wiki/Q6423", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T08:57:25Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 15.8, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 99.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: 01a07b14-a942-73b0-9b7b-5b94c2a9a523\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Boeing 767\nRegistry id: vr.tr.boeing-767\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA V" } } }, "metaModel": { "id": "THING-Q6423", "registryId": "vr.tr.boeing-767", "name": "Boeing 767", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q6423/", "model": { "registry_id": "vr.tr.boeing-767", "name": "Boeing 767", "purpose": "Enable an AI agent to recognise a Boeing 767, establish its individual configuration and condition, and assess whether proposed operation, loading, maintenance or modification is supported by applicable evidence.", "definition": "", "scope_statement": "This model owns the Boeing 767 family identity and the configuration, physical condition, limitations and action prerequisites of individual airframes under vr.tr.boeing-767; variant distinctions remain within this entry, while military-derivative membership requires an explicit boundary decision.", "in_scope": [ "Family, series and individual airframe identification, including evidence distinguishing marketed designations from approved model identities.", "As-built and current passenger, factory-freighter or converted-freighter configuration.", "Installed engines, airframe modifications and equipment that determine applicable limits and procedures.", "Airframe condition, utilisation, maintenance evidence and unresolved discrepancies.", "Aircraft-specific loading, airport compatibility and operational eligibility." ], "out_of_scope": [ "Airline organisation, commercial schedules, fares and fleet economics.", "Airport infrastructure and air traffic management, except their compatibility with the particular aircraft.", "Engine and component internal engineering, except installed identity, condition and aircraft interfaces.", "Individual flight planning and execution, except the aircraft capabilities and restrictions supplied to those models.", "Crew licensing and maintenance-provider qualification, except evidence of authority required for a proposed action.", "Military mission systems and mission execution associated with 767-derived platforms." ], "distinguishing_features": [ "Require manufacturer and approved model evidence tied to an airframe serial number; a registration, operator nickname or visual resemblance alone must not establish Boeing 767 identity.", "Match observed geometry to the specific 767 series: Boeing identifies the 767-300/-300ER as longer than the 767-200, so fuselage length must be checked against the candidate series. [Boeing airport planning manual](https://www.boeing.com/content/dam/boeing/v2/airports/acaps/767_REV_K.pdf)", "Do not infer extended-range status from external shape: Boeing reports identical outside dimensions for corresponding standard and extended-range models. [Boeing airport planning manual](https://www.boeing.com/content/dam/boeing/v2/airports/acaps/767_REV_K.pdf)", "For a candidate 767-400ER, corroborate its elongated fuselage and raked wingtips with model records; Boeing also identifies a different main landing gear and upgraded flight deck. [Boeing 767-400ER introduction](https://boeing.mediaroom.com/2000-07-26-The-Newest-Boeing-767-Is-Inspired-By-The-Future-Introducing-The-Boeing-767-400ER)", "Distinguish a factory freighter from a converted passenger airframe using production and modification records; cargo doors, painted windows or an operator's freighter label alone do not establish the approval basis." ], "characteristics": [ { "name": "Approved model and series", "kind": "category", "unit_or_values": "Exact designation from applicable aircraft approval records; retain marketing designation separately.", "why_it_matters": "Selects the correct 767 configuration baseline and prevents assumptions from transferring between series." }, { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer serial number linked to identity evidence and dated registration history.", "why_it_matters": "Maintains continuity through registration, operator and configuration changes." }, { "name": "Payload configuration", "kind": "category", "unit_or_values": "Passenger, factory freighter, converted freighter, other documented configuration or unresolved.", "why_it_matters": "Determines which occupancy, restraint, loading and fire-protection requirements must be established." }, { "name": "Installed propulsion configuration", "kind": "relation", "unit_or_values": "Engine position linked to manufacturer, model, serial number, rating and installation approval.", "why_it_matters": "Binds performance, maintenance applicability and interchangeability decisions to the actual installation." }, { "name": "Physical envelope", "kind": "measurement", "unit_or_values": "Length, wingspan and height in metres, with series and modification applicability.", "why_it_matters": "Supports stand, hangar, taxiway and servicing clearance checks." }, { "name": "Approved mass limits", "kind": "measurement", "unit_or_values": "Ramp, takeoff, landing and zero-fuel mass in kilograms, each linked to applicable approved documentation.", "why_it_matters": "Prevents a family-level maximum from being treated as the limit of a particular aircraft." }, { "name": "Current mass and balance", "kind": "measurement", "unit_or_values": "Mass in kilograms; centre of gravity in the units used by the approved envelope; configuration and effective date.", "why_it_matters": "Establishes whether a proposed passenger or cargo load fits the current aircraft." }, { "name": "Accumulated utilisation", "kind": "measurement", "unit_or_values": "Flight hours, flight cycles and calendar age with a dated record boundary.", "why_it_matters": "Supports evaluation of inspections, life limits and ageing-airframe exposure." }, { "name": "Technical availability", "kind": "state", "unit_or_values": "Released with stated conditions, restricted, under maintenance, stored, retired or unknown; dated supporting evidence.", "why_it_matters": "Separates physical presence and apparent serviceability from supported readiness for a particular action." }, { "name": "Modification and repair baseline", "kind": "relation", "unit_or_values": "Applicable design changes, conversion approvals, repair records and incorporated revisions.", "why_it_matters": "Explains departures from the original 767 build and identifies superseded limits or procedures." }, { "name": "Extended-diversion eligibility", "kind": "state", "unit_or_values": "Documented aircraft capability and maintenance status, linked separately to operator authorisation; unknown where unsupported.", "why_it_matters": "Prevents the 767 designation or an ER label from being treated as permission for a proposed extended-diversion operation." } ], "affordances": [ "Resolve a reported aircraft to a documented 767 series and individual airframe, retaining conflicting identification evidence.", "Select the manuals, limitations and maintenance requirements applicable to its installed engines and modification baseline.", "Screen a proposed passenger or freight load against the aircraft's documented layout, restraints, mass and balance limits.", "Check preliminary airport, stand, hangar and ground-equipment compatibility using configuration-specific geometry and interfaces.", "Identify discrepancies and missing evidence that prevent a supported dispatch or return-to-service decision.", "Assess the prerequisites for a proposed repair, freighter conversion, storage programme or reactivation and route the decision to the responsible authority." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-variant", "name": "Identity and variant", "description": "Establish which 767 is being described and which family distinctions govern interpretation.", "rationale": "A generic Boeing 767 label is insufficient to select limits, recognise conversion history or distinguish family members.", "layers": [ { "id": "airframe-identification", "name": "Airframe identification", "description": "Connect the observed aircraft to enduring manufacturer identity.", "findings": [ { "id": "documented-767-identity", "name": "Documented 767 identity", "description": "Record the evidence linking the airframe to its manufacturer serial number and approved model, with registration treated as a dated association.", "questions": [ { "text": "Which manufacturer and registration records establish that this serial-numbered airframe is a Boeing 767?", "kind": "provenance", "id": "documented-767-identity-q01" }, { "text": "Do observed dimensions and identifying features agree with the recorded series, and how are conflicts resolved?", "kind": "measurement", "id": "documented-767-identity-q02" } ] } ] }, { "id": "family-membership", "name": "Family membership", "description": "Separate series, commercial labels and derivative relationships.", "findings": [ { "id": "variant-boundary", "name": "Variant boundary", "description": "Preserve approved model identity alongside ER, freighter and derivative labels without assuming they are equivalent classifications.", "questions": [ { "text": "What approved model and configuration evidence underlies the aircraft's series, ER or freighter designation?", "kind": "definition", "id": "variant-boundary-q01" }, { "text": "If the aircraft is a military derivative, which aspects belong under this entry and which require a linked model?", "kind": "boundary", "id": "variant-boundary-q02" } ] } ] } ] }, { "id": "configuration-and-modifications", "name": "Configuration and modifications", "description": "Describe the particular 767 as built and as currently equipped.", "rationale": "Engine installations, wing changes, flight-deck differences and cargo conversions can make superficially similar 767s require different evidence and procedures.", "layers": [ { "id": "installed-equipment", "name": "Installed equipment", "description": "Establish the equipment baseline that controls technical applicability.", "findings": [ { "id": "propulsion-and-equipment-baseline", "name": "Propulsion and equipment baseline", "description": "Identify installed engines, relevant flight-deck equipment and wingtip configuration with their approval and manual applicability.", "questions": [ { "text": "Which engine models, ratings and serial numbers are installed at each position on this 767?", "kind": "provenance", "id": "propulsion-and-equipment-baseline-q01" }, { "text": "Which flight-deck or wingtip modifications change the applicable limitations, geometry or procedures?", "kind": "boundary", "id": "propulsion-and-equipment-baseline-q02" } ] } ] }, { "id": "configuration-history", "name": "Configuration history", "description": "Track changes between original delivery and the current approved aircraft.", "findings": [ { "id": "conversion-and-repair-lineage", "name": "Conversion and repair lineage", "description": "Link freighter conversions, structural repairs and other material alterations to their approval evidence and continuing obligations.", "questions": [ { "text": "Was this aircraft delivered as a freighter or converted, and which records establish its current cargo configuration?", "kind": "provenance", "id": "conversion-and-repair-lineage-q01" }, { "text": "Which supplements, inspections and limitations must accompany each incorporated conversion or major repair?", "kind": "action", "id": "conversion-and-repair-lineage-q02" } ] } ] } ] }, { "id": "payload-and-loading", "name": "Payload and loading", "description": "Determine what the configured 767 can carry and how a proposed load must be evaluated.", "rationale": "Passenger and freighter configurations require different evidence about usable spaces, restraint, evacuation and load distribution.", "layers": [ { "id": "usable-payload-spaces", "name": "Usable payload spaces", "description": "Describe approved passenger accommodation and cargo positions.", "findings": [ { "id": "layout-and-loading-interfaces", "name": "Layout and loading interfaces", "description": "Record the installed cabin or cargo layout, accessible loading openings and compatible restraint arrangements.", "questions": [ { "text": "Which seating and exit arrangement or main-deck cargo-position plan is approved for this aircraft?", "kind": "provenance", "id": "layout-and-loading-interfaces-q01" }, { "text": "What door clearances, loading heights, cargo-unit dimensions and restraint interfaces constrain loading?", "kind": "measurement", "id": "layout-and-loading-interfaces-q02" } ] } ] }, { "id": "load-acceptability", "name": "Load acceptability", "description": "Evaluate proposed loads against the current aircraft's limits.", "findings": [ { "id": "mass-balance-and-local-loads", "name": "Mass, balance and local loads", "description": "Keep overall mass and centre-of-gravity checks connected to compartment, floor and individual cargo-position limits.", "questions": [ { "text": "What current empty-mass baseline, centre-of-gravity envelope and structural loading limits apply after modifications?", "kind": "measurement", "id": "mass-balance-and-local-loads-q01" }, { "text": "Does the proposed load and loading sequence satisfy the approved balance, restraint and local-load requirements?", "kind": "action", "id": "mass-balance-and-local-loads-q02" } ] } ] } ] }, { "id": "condition-and-airworthiness", "name": "Condition and airworthiness", "description": "Establish the technical state of the individual 767 and the evidence supporting it.", "rationale": "An airframe's service history, repairs, deferred defects and storage exposure can dominate what may presently be done with it.", "layers": [ { "id": "structural-and-system-condition", "name": "Structural and system condition", "description": "Connect utilisation and exposure to observed condition and outstanding work.", "findings": [ { "id": "ageing-and-damage-evidence", "name": "Ageing and damage evidence", "description": "Record dated inspections, fatigue or corrosion findings, damage and repairs against the applicable 767 maintenance baseline.", "questions": [ { "text": "What verified hours, cycles, storage periods and exposure history inform the airframe's inspection needs?", "kind": "measurement", "id": "ageing-and-damage-evidence-q01" }, { "text": "Which structural findings or system defects remain unresolved, and where are their inspection and repair records?", "kind": "provenance", "id": "ageing-and-damage-evidence-q02" } ] } ] }, { "id": "release-and-restrictions", "name": "Release and restrictions", "description": "Separate technical observations from documented authority to operate.", "findings": [ { "id": "supported-technical-status", "name": "Supported technical status", "description": "Establish the applicable mandatory actions, maintenance completion, deferred-defect conditions and authorised release.", "questions": [ { "text": "Which mandatory actions and maintenance tasks apply to this serial number, engine installation and modification state, and what proves compliance?", "kind": "provenance", "id": "supported-technical-status-q01" }, { "text": "Do deferred defects, expired intervals or storage conditions block the proposed operation or require authorised work first?", "kind": "action", "id": "supported-technical-status-q02" } ] } ] } ] }, { "id": "operational-and-ground-compatibility", "name": "Operational and ground compatibility", "description": "Connect aircraft-specific capabilities to a proposed flight or ground activity.", "rationale": "Family performance summaries cannot establish the suitability of an individual 767 for a route, runway, stand or servicing operation.", "layers": [ { "id": "flight-capability", "name": "Flight capability", "description": "Supply configuration-specific limits and eligibility evidence to flight-planning decisions.", "findings": [ { "id": "mission-eligibility", "name": "Mission eligibility", "description": "Bind performance evaluation and extended-diversion capability to current aircraft configuration and separately evidenced operational authority.", "questions": [ { "text": "Which approved performance data apply to this 767's engines, mass limits, modifications and current discrepancies?", "kind": "provenance", "id": "mission-eligibility-q01" }, { "text": "What aircraft status and operator-authorisation evidence are required for the proposed route, including any extended-diversion segment?", "kind": "action", "id": "mission-eligibility-q02" } ] } ] }, { "id": "ground-interfaces", "name": "Ground interfaces", "description": "Describe the aircraft's compatibility with pavement, clearances and support equipment.", "findings": [ { "id": "airport-and-servicing-fit", "name": "Airport and servicing fit", "description": "Use the actual series, wing configuration, landing gear and servicing interfaces to assess ground movements and support.", "questions": [ { "text": "What geometry, turning envelope and pavement-loading data apply to this aircraft at the proposed operating mass?", "kind": "measurement", "id": "airport-and-servicing-fit-q01" }, { "text": "Are the proposed stand, towing equipment, loaders and service connections compatible with this configuration under applicable procedures?", "kind": "action", "id": "airport-and-servicing-fit-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend Boeing 767 to include KC-767, KC-46 and E-767 derivatives, and do existing registered or world models already own those concepts?", "Which authoritative approval records establish the mapping between marketed 767 series, ER labels, factory freighters and conversion designations across jurisdictions?", "Which approved manuals and supplements are available for determining aircraft-specific engine, weight, wingtip and cargo-conversion applicability?", "Which 767-specific structural concerns, mandatory actions and inspection thresholds apply to each serial-number and modification range?", "What evidence freshness and conflict-resolution rules should govern aircraft condition, maintenance release and extended-diversion eligibility when operator and maintenance records disagree?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "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 Boeing 767, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a Boeing 767, establish its individual configuration and condition, and assess whether proposed operation, loading, maintenance or modification is supported by applicable evidence.", "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: KC-767, Boeing 767-200, Boeing 767-300, Boeing 767-400ER, Boeing 767-200SF, Boeing 767-200BDSF, Boeing 767-200PC.", "7 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 65 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 Boeing 767, 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 Boeing 767 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": [ "KC-767", "Boeing 767-200", "Boeing 767-300", "Boeing 767-400ER", "Boeing 767-200SF", "Boeing 767-200BDSF", "Boeing 767-200PC" ] } ], "standing": "Described in 65 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 7 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 Boeing 767 from another, and a Boeing 767 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 Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Boeing 767 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 Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Boeing 767 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Boeing 767 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 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 Boeing 767 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 Boeing 767 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Boeing 767, 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 Boeing 767, 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 Boeing 767 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 } } } }