{ "model": { "rank": 5987, "code": "thing-q34945", "model_id": "vr.tr.grumman-f-14-tomcat", "name": "Grumman F-14 Tomcat", "purpose": "Enable an AI agent to identify a Grumman F-14 Tomcat, distinguish its documented configuration from its observed condition, and determine which inspection, preservation, handling or operational actions have adequate evidence and authorization.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q34945/", "tier": 2, "score": 63, "payload": { "layer": "wikidata", "aliases": [ "Grumman NF-14 Tomcat", "Grumman F-14 Tomcat in service", "Grumman F-14A Tomcat" ], "aliasCount": 3, "merged": 3, "knownIn": 63, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q34945", "url": "https://www.wikidata.org/wiki/Q34945", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:31:51Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00536758, "turns": 1, "seconds": 16.7, "error": null }, "codex": { "seconds": 140.5, "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: 01a07b6a-7c78-7213-a1ae-af272c1d21df\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Grumman F-14 Tomcat\nRegistry id: vr.tr.grumman-f-14-tomcat\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this " } } }, "metaModel": { "id": "THING-Q34945", "registryId": "vr.tr.grumman-f-14-tomcat", "name": "Grumman F-14 Tomcat", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q34945/", "model": { "registry_id": "vr.tr.grumman-f-14-tomcat", "name": "Grumman F-14 Tomcat", "purpose": "Enable an AI agent to identify a Grumman F-14 Tomcat, distinguish its documented configuration from its observed condition, and determine which inspection, preservation, handling or operational actions have adequate evidence and authorization.", "definition": "The Grumman F-14 Tomcat is a twin-engine, two-seat, variable-sweep-wing supersonic carrier-based air superiority fighter developed for the U.S. Navy, later used for fleet air defense, reconnaissance, and precision strike, and exported only to Iran.", "scope_statement": "This model owns the recognition criteria and aircraft-level state of the F-14 Tomcat family registered as vr.tr.grumman-f-14-tomcat, including individual airframes, variant changes, installed equipment and limitations, while linking to separate models for components, operators and activities.", "in_scope": [ "F-14 family recognition and individual airframe identity, including conflicting serials, markings and provenance.", "As-built variant, documented conversions and current installed configuration.", "Variable-sweep wings, propulsion, flight controls and carrier-interface condition.", "Cockpit, sensors and aircraft-side mission-equipment configuration without assuming operational availability.", "Airframe service history, maintenance evidence, preservation state and action-specific restrictions." ], "out_of_scope": [ "Independent design and maintenance models for engines, radars, ejection seats and other replaceable components.", "Missile and ammunition internals, weapon employment procedures and targeting decisions.", "Carrier design, airfield operations and organizational readiness of squadrons.", "Pilot qualifications, training curricula and flight procedures.", "The complete history of Grumman, naval aviation or conflicts involving the F-14.", "Replicas, scale models and simulators as physical F-14 airframes; these require representation links." ], "distinguishing_features": [ "Require a combination of two engines, two crew places and variable-sweep wings; a fighter silhouette or Tomcat paint scheme alone is insufficient. [Smithsonian aircraft record](https://www.si.edu/object/nasm_A20040156000)", "Use variable-sweep wings together with the twin-tail arrangement to screen look-alikes; neither feature independently establishes F-14 identity. [NASA F-14 research history](https://www.nasa.gov/wp-content/uploads/2023/04/sp-4519.pdf)", "Cross-check a claimed F-14A, F-14B or F-14D against engine documentation: the Navy identifies TF30 propulsion for the A and F110 propulsion for the B and D; engine appearance alone cannot distinguish B from D. [Naval History and Heritage Command](https://www.history.navy.mil/research/histories/naval-aviation-history/naval-aircraft/current-aircraft-inventory/f-14-tomcat.html)", "Distinguish an original production configuration from a converted airframe through its history; an F-14A can subsequently become an F-14D, so an early identity record need not describe its later configuration. [National Naval Aviation Museum](https://www.history.navy.mil/content/history/museums/nnam/explore/collections/aircraft/f/f-14d-tomcat.html)" ], "characteristics": [ { "name": "Airframe identity", "kind": "relation", "unit_or_values": "Manufacturer identity and military serial linked to dated records; confidence and conflicts retained", "why_it_matters": "Separates the physical airframe from repainting, display labels and reassigned markings." }, { "name": "Configuration lineage", "kind": "category", "unit_or_values": "Documented F-14 designation, production configuration, conversion history or unresolved", "why_it_matters": "Determines which technical references apply without treating every Tomcat as interchangeable." }, { "name": "Installed propulsion", "kind": "relation", "unit_or_values": "Left and right engine identities, documented models, installation dates and serviceability evidence", "why_it_matters": "Separates variant expectations from engines actually installed." }, { "name": "Wing-sweep position", "kind": "measurement", "unit_or_values": "Degrees for each wing, with reference convention, observation time and uncertainty", "why_it_matters": "Affects footprint, handling clearance and assessment of configuration discrepancies." }, { "name": "Wing-sweep system condition", "kind": "state", "unit_or_values": "Documented functional, restricted, immobilized, defective, untested or unknown", "why_it_matters": "Visible wing position does not establish that the sweep mechanism can safely move." }, { "name": "Structural exposure and usage", "kind": "measurement", "unit_or_values": "Flight hours, recorded landings and carrier events where available, with record coverage", "why_it_matters": "Supports assessment of inspection applicability while preserving gaps in life-history evidence." }, { "name": "Carrier-interface condition", "kind": "state", "unit_or_values": "Component-specific condition and restrictions for landing gear, launch interfaces and arresting equipment", "why_it_matters": "Carrier-oriented design does not establish present suitability for launch or recovery." }, { "name": "Cockpit and mission-equipment fit", "kind": "relation", "unit_or_values": "Dated inventory of installed crew-station equipment, sensors, wiring and aircraft-side stores interfaces", "why_it_matters": "Prevents historical capability from being inferred from designation or external appearance." }, { "name": "Hazard isolation", "kind": "state", "unit_or_values": "Verified, partial, unverified or unknown isolation, recorded separately for each identified hazard", "why_it_matters": "Controls whether access, movement or conservation work can proceed." }, { "name": "Action authorization", "kind": "relation", "unit_or_values": "Specific action linked to responsible authority, applicable evidence, conditions and validity period", "why_it_matters": "Permission to display or tow an airframe does not imply permission to energize or fly it." } ], "affordances": [ "Identify a candidate airframe and reconcile its serials, markings and conversion history.", "Compare observed engines, cockpit equipment and external features with its documented F-14 configuration.", "Request inspections or records needed to resolve wing-sweep, structural or carrier-interface uncertainty.", "Assess whether a proposed tow, lift, cockpit visit or display arrangement has sufficient clearance, condition evidence and authorization.", "Plan preservation work around missing equipment, corrosion exposure and verified hazard isolation.", "Refer operational eligibility decisions to the applicable technical documentation and responsible authority." ] }, "sources": [], "structure": { "bundles": [ { "id": "tomcat-identity-and-lineage", "name": "Tomcat identity and lineage", "description": "Establish whether the subject is an F-14 airframe and which configuration history belongs to it.", "rationale": "Repainting, equipment removal and variant conversions can separate visible appearance from aircraft identity.", "layers": [ { "id": "family-recognition", "name": "Family recognition", "description": "Evaluate physical and documentary evidence for membership in the registered F-14 family.", "findings": [ { "id": "f-14-identification-evidence", "name": "F-14 identification evidence", "description": "Record observed recognition features, missing features and the documents connecting the subject to the F-14 family.", "questions": [ { "text": "Which observed engine, crew-station, wing-sweep and tail features support identifying this subject as an F-14?", "kind": "definition", "id": "f-14-identification-evidence-q01" }, { "text": "What evidence distinguishes an actual airframe or surviving airframe section from a replica or simulator?", "kind": "boundary", "id": "f-14-identification-evidence-q02" } ] } ] }, { "id": "airframe-continuity", "name": "Airframe continuity", "description": "Separate persistent aircraft identity from changing markings and equipment.", "findings": [ { "id": "serial-and-conversion-chain", "name": "Serial and conversion chain", "description": "Record the supported chain from original identity through redesignation, conversion and restoration.", "questions": [ { "text": "Which primary records connect the manufacturer's identity, military serial and present physical airframe?", "kind": "provenance", "id": "serial-and-conversion-chain-q01" }, { "text": "Which dated records establish the as-built designation and subsequent conversions?", "kind": "provenance", "id": "serial-and-conversion-chain-q02" }, { "text": "Do displayed markings describe this airframe's own history or represent another aircraft?", "kind": "boundary", "id": "serial-and-conversion-chain-q03" } ] } ] } ] }, { "id": "variable-sweep-airframe", "name": "Variable-sweep airframe", "description": "Represent the Tomcat's changing geometry and the structural evidence relevant to that geometry.", "rationale": "Wing position changes the aircraft's footprint, while sweep-system condition and structural condition require separate evidence.", "layers": [ { "id": "sweep-geometry", "name": "Sweep geometry", "description": "Record actual wing positions and the configuration used for clearance judgments.", "findings": [ { "id": "observed-wing-configuration", "name": "Observed wing configuration", "description": "Capture measured geometry without interpreting a parked configuration as evidence of operability.", "questions": [ { "text": "What are the measured left and right wing-sweep angles, and how was the reference convention established?", "kind": "measurement", "id": "observed-wing-configuration-q01" }, { "text": "What footprint and clearance envelope apply to the present wing configuration and proposed movement?", "kind": "measurement", "id": "observed-wing-configuration-q02" }, { "text": "Which applicable reference identifies this configuration as a flight, parking or maintenance condition?", "kind": "provenance", "id": "observed-wing-configuration-q03" } ] } ] }, { "id": "sweep-and-structure-condition", "name": "Sweep and structure condition", "description": "Connect wing movement and structural restrictions to inspections and usage records.", "findings": [ { "id": "wing-system-restrictions", "name": "Wing-system restrictions", "description": "Record condition evidence for sweep mechanisms, wing attachments and associated supporting structure.", "questions": [ { "text": "Which inspections establish the condition of the sweep mechanism, wing attachments and surrounding structure?", "kind": "provenance", "id": "wing-system-restrictions-q01" }, { "text": "What unresolved damage, corrosion, record gaps or immobilization measures restrict wing movement?", "kind": "action", "id": "wing-system-restrictions-q02" } ] } ] } ] }, { "id": "propulsion-and-flight-systems", "name": "Propulsion and flight systems", "description": "Describe installed propulsion and the aircraft-level systems needed to assess powered or flight-related actions.", "rationale": "An F-14 designation supplies an expectation about equipment, not proof of installed hardware or serviceability.", "layers": [ { "id": "engine-installation", "name": "Engine installation", "description": "Identify both engine installations and their compatibility with the documented configuration.", "findings": [ { "id": "paired-engine-evidence", "name": "Paired engine evidence", "description": "Record engine identity, installation status and supporting service records separately for each side.", "questions": [ { "text": "Which engine model and serial are installed on each side, and are either installations incomplete or display substitutes?", "kind": "provenance", "id": "paired-engine-evidence-q01" }, { "text": "Which configuration record establishes that each installed engine and its interfaces are applicable to this airframe?", "kind": "boundary", "id": "paired-engine-evidence-q02" } ] } ] }, { "id": "control-and-power-readiness", "name": "Control and power readiness", "description": "Represent the evidence for connected flight controls, hydraulic systems and electrical systems.", "findings": [ { "id": "system-level-action-limits", "name": "System-level action limits", "description": "Keep external completeness, documented functionality and authorization for energization distinct.", "questions": [ { "text": "What dated records establish the condition of flight controls, hydraulic systems and electrical systems in this configuration?", "kind": "provenance", "id": "system-level-action-limits-q01" }, { "text": "Which disconnected, preserved or defective systems prevent a proposed power application or control movement?", "kind": "action", "id": "system-level-action-limits-q02" }, { "text": "Who can authorize the proposed action, and which applicable technical reference governs it?", "kind": "action", "id": "system-level-action-limits-q03" } ] } ] } ] }, { "id": "crew-and-mission-configuration", "name": "Crew and mission configuration", "description": "Represent the actual two-place cockpit and installed mission equipment without equating equipment presence with capability.", "rationale": "Variant changes, modifications and museum removals can substantially alter what an individual Tomcat contains.", "layers": [ { "id": "crew-station-fit", "name": "Crew-station fit", "description": "Identify installed cockpit equipment and the evidence supporting crew access.", "findings": [ { "id": "cockpit-completeness-and-access", "name": "Cockpit completeness and access", "description": "Record front and rear station equipment, substitutions and access constraints.", "questions": [ { "text": "Which instruments, displays, controls and seat assemblies are present in each crew station?", "kind": "measurement", "id": "cockpit-completeness-and-access-q01" }, { "text": "Which records distinguish operational equipment from inert, disconnected or replica cockpit fittings?", "kind": "provenance", "id": "cockpit-completeness-and-access-q02" }, { "text": "What verified seat, canopy and access conditions must be satisfied before cockpit entry?", "kind": "action", "id": "cockpit-completeness-and-access-q03" } ] } ] }, { "id": "mission-equipment-fit", "name": "Mission-equipment fit", "description": "Track installed sensors and aircraft-side equipment interfaces at a descriptive level.", "findings": [ { "id": "installed-versus-attributed-capability", "name": "Installed versus attributed capability", "description": "Separate dated equipment fit from historical descriptions of F-14 capabilities.", "questions": [ { "text": "Which records identify the radar, other sensors and mission-related modifications actually installed at the date being modeled?", "kind": "provenance", "id": "installed-versus-attributed-capability-q01" }, { "text": "Which attributed capabilities lack supporting evidence for this specific airframe and configuration?", "kind": "boundary", "id": "installed-versus-attributed-capability-q02" }, { "text": "Which visible stores or pods are actual equipment, inert exhibits or replicas, and which separate component records describe them?", "kind": "definition", "id": "installed-versus-attributed-capability-q03" } ] } ] } ] }, { "id": "carrier-and-ground-interfaces", "name": "Carrier and ground interfaces", "description": "Record the condition and applicability of recovery, launch, support and movement interfaces.", "rationale": "The Tomcat's carrier-oriented configuration and variable footprint create specific handling questions that general aircraft identity cannot answer.", "layers": [ { "id": "launch-and-recovery-hardware", "name": "Launch and recovery hardware", "description": "Distinguish fitted carrier-interface hardware from documented eligibility for use.", "findings": [ { "id": "carrier-interface-evidence", "name": "Carrier-interface evidence", "description": "Record landing-gear, launch-interface and arresting-equipment condition with relevant history.", "questions": [ { "text": "Which landing-gear, launch-interface and arresting components are installed, altered or absent?", "kind": "measurement", "id": "carrier-interface-evidence-q01" }, { "text": "What inspection and usage records support the stated condition of those components?", "kind": "provenance", "id": "carrier-interface-evidence-q02" }, { "text": "What evidence and authorization would be required before treating this airframe as eligible for a proposed launch or recovery activity?", "kind": "action", "id": "carrier-interface-evidence-q03" } ] } ] }, { "id": "ground-support-and-clearance", "name": "Ground support and clearance", "description": "Assess a proposed movement or display arrangement against the airframe's actual support and geometry.", "findings": [ { "id": "movement-and-support-eligibility", "name": "Movement and support eligibility", "description": "Connect towing, lifting and static support proposals to applicable documentation and observed condition.", "questions": [ { "text": "Which approved handling reference and verified support points apply to this airframe's current completeness and configuration?", "kind": "provenance", "id": "movement-and-support-eligibility-q01" }, { "text": "What mass evidence, wing position, gear condition and route clearances constrain the proposed movement?", "kind": "measurement", "id": "movement-and-support-eligibility-q02" }, { "text": "Which unresolved support or clearance conditions require the movement to remain pending?", "kind": "action", "id": "movement-and-support-eligibility-q03" } ] } ] } ] }, { "id": "service-preservation-and-permissions", "name": "Service, preservation and permissions", "description": "Connect the airframe's history and present custody to condition judgments and permitted actions.", "rationale": "Historical service, preserved appearance and permission to display an F-14 do not establish present operational status.", "layers": [ { "id": "life-history-and-condition", "name": "Life history and condition", "description": "Preserve the evidence needed to interpret accumulated use, damage, storage and restoration.", "findings": [ { "id": "dated-condition-baseline", "name": "Dated condition baseline", "description": "Record a time-bounded assessment with explicit coverage gaps and restoration substitutions.", "questions": [ { "text": "Which records establish flight hours, landing history, major repairs and periods of storage for this airframe?", "kind": "provenance", "id": "dated-condition-baseline-q01" }, { "text": "What inspections document corrosion, weather exposure and deterioration of installed or preserved systems?", "kind": "measurement", "id": "dated-condition-baseline-q02" }, { "text": "Which missing records or substituted parts limit conclusions about authenticity or serviceability?", "kind": "boundary", "id": "dated-condition-baseline-q03" } ] } ] }, { "id": "hazards-and-action-authority", "name": "Hazards and action authority", "description": "Represent verified hazard states and action-specific authority under current custody.", "findings": [ { "id": "verified-action-boundaries", "name": "Verified action boundaries", "description": "Record the evidence and responsible authority for each proposed access, handling, conservation or operational action.", "questions": [ { "text": "What dated evidence establishes isolation or removal of seat and canopy initiation hazards, residual fluids, pressure and installed ordnance?", "kind": "provenance", "id": "verified-action-boundaries-q01" }, { "text": "Which custodian or competent authority can approve the proposed action, and what conditions or expiry apply?", "kind": "action", "id": "verified-action-boundaries-q02" }, { "text": "Which restrictions arise from the airframe's current condition, loan terms, demilitarization status or applicable jurisdiction?", "kind": "boundary", "id": "verified-action-boundaries-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": [ "F-14A", "F-14B", "F-14D", "F-14A+", "RF-14 (proposed reconnaissance)", "F-14AM (Iranian upgrade)", "NF-14D (NASA research)", "QF-14 (proposed target drone)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Grumman F-14 Tomcat this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own the F-14 concept, and should this registry entry link to it instead of receiving a separate publication?", "Which authoritative references establish the applicability boundaries among production variants, conversions, prototypes and operator-specific modifications?", "Which current, applicable technical documents can support wing-sweep, handling and inspection judgments for each configuration without importing limits from a different variant?", "What minimum identity continuity makes a heavily reconstructed or composite survivor the same F-14 airframe, and when should it instead be modeled as an assembly or representation?", "For the particular airframe and observation date, which records establish current equipment fit, serviceability, hazard isolation and custody restrictions, especially where operational records are unavailable?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 13, "questions": 34 } }, "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 Grumman F-14 Tomcat, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify a Grumman F-14 Tomcat, distinguish its documented configuration from its observed condition, and determine which inspection, preservation, handling or operational actions have adequate evidence and authorization.", "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: Grumman NF-14 Tomcat, Grumman F-14 Tomcat in service, Grumman F-14A Tomcat.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 63 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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": [ "Grumman NF-14 Tomcat", "Grumman F-14 Tomcat in service", "Grumman F-14A Tomcat" ] } ], "standing": "Described in 63 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 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 Grumman F-14 Tomcat from another, and a Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Grumman F-14 Tomcat 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Grumman F-14 Tomcat performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Grumman F-14 Tomcat at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 Grumman F-14 Tomcat is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat, 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 Grumman F-14 Tomcat 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 } } } }