{ "model": { "rank": 5581, "code": "thing-q81231", "model_id": "vr.tr.iron-dome", "name": "Iron Dome", "purpose": "Enable an AI agent to recognise Iron Dome, distinguish its system configurations, assess documented condition and evidence, and identify authorised support actions.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q81231/", "tier": 2, "score": 66, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 66, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q81231", "url": "https://www.wikidata.org/wiki/Q81231", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:41:56Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.1, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08854-ea6b-7b53-898b-105e918ff0ba\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Iron Dome\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 188 things:\n# Batch 006: 1001 regist", "usd": 0, "recall": true }, "codex": { "seconds": 55.6, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08854-ea60-7cf1-b896-1a56dda80fc4\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Iron Dome\nRegistry id: vr.tr.iron-dome\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCont" } } }, "metaModel": { "id": "THING-Q81231", "registryId": "vr.tr.iron-dome", "name": "Iron Dome", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q81231/", "model": { "registry_id": "vr.tr.iron-dome", "name": "Iron Dome", "purpose": "Enable an AI agent to recognise Iron Dome, distinguish its system configurations, assess documented condition and evidence, and identify authorised support actions.", "definition": "Iron Dome is an Israeli short-range air-defence system developed by Rafael with Israeli partners that combines radar, battle-management software and Tamir interceptor missiles to engage incoming rockets and other aerial threats assessed as endangering defended areas.", "scope_statement": "This model owns the identifying properties, functional architecture, configuration distinctions and lifecycle requirements of Iron Dome as the named air-defence system family registered as vr.tr.iron-dome in PHY / PHY.OBJ; individual batteries, launchers and interceptors are related instances or components.", "in_scope": [ "Identity and boundaries of the Iron Dome system family", "Relationships among detection, battle-management, launch and interception functions", "Documented configurations and interfaces that establish system membership", "Evidence-qualified capability claims and readiness descriptions", "Maintenance, controlled handling and authorised lifecycle support" ], "out_of_scope": [ "Detailed construction or internal design of interceptor missiles and radar equipment", "Tactical deployment, engagement settings and targeting decisions", "Other air-defence systems and the architecture of a national defence network", "Military organisations, procurement programmes and manufacturing companies as independent entities", "Conflict histories and political assessments of system use" ], "distinguishing_features": [ "Identification requires documented membership in the Iron Dome family; a generic short-range air-defence system does not qualify by function alone.", "A complete system configuration connects detection and tracking, battle management, and interceptor launch functions; a launcher or interceptor alone is a component.", "Its characteristic functional description includes assessing predicted impact and selectively engaging threats judged relevant to protected areas.", "The model distinguishes Iron Dome from adjacent defence systems through documented system identity, component compatibility and integration boundaries, rather than through overlapping threat labels." ], "characteristics": [ { "name": "System identity and designation", "kind": "category", "unit_or_values": "Documented official designation, aliases and configuration identifier", "why_it_matters": "Prevents confusion between the named family, related products and individual equipment." }, { "name": "Configuration membership", "kind": "relation", "unit_or_values": "Configuration linked to documented radar, battle-management, launcher and interceptor types", "why_it_matters": "Establishes which components form a supported system combination." }, { "name": "Functional role", "kind": "category", "unit_or_values": "Detection and tracking; threat assessment; engagement coordination; launch; interception; support", "why_it_matters": "Separates component functions from claims about the complete system." }, { "name": "Documented threat coverage", "kind": "category", "unit_or_values": "Source-stated threat classes, qualified by configuration, date and evidence type", "why_it_matters": "Avoids attributing one configuration's claimed capabilities to every Iron Dome installation." }, { "name": "Claimed engagement envelope", "kind": "measurement", "unit_or_values": "km for explicitly defined distance or altitude measures, with conditions and source", "why_it_matters": "Keeps target travel range, interceptor reach and defended footprint from becoming interchangeable figures." }, { "name": "Readiness evidence", "kind": "state", "unit_or_values": "Unknown; under maintenance; under test; restricted; declared ready, with authority and timestamp", "why_it_matters": "A component's apparent availability cannot establish complete-system readiness." }, { "name": "External support dependencies", "kind": "relation", "unit_or_values": "Documented power, communications, resupply and authorised support dependencies", "why_it_matters": "Exposes dependencies that affect whether a configuration can be supported." }, { "name": "Performance claim basis", "kind": "category", "unit_or_values": "Manufacturer claim; operator report; controlled test; independent analysis; unresolved", "why_it_matters": "Makes the provenance and limits of effectiveness statements explicit." } ], "affordances": [ "Classify a documented asset as a complete Iron Dome configuration, constituent component or related external system.", "Compare configuration records and flag unsupported component combinations for qualified review.", "Trace a capability or effectiveness statement to its source, configuration, date and measurement definition.", "Summarise readiness evidence and identify missing inspections or support records without declaring combat readiness.", "Route maintenance, handling and configuration-change requests to the documented responsible authority." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-system-boundary", "name": "Identity and System Boundary", "description": "Establishes what the registered Iron Dome concept includes and how named variants and physical instances relate to it.", "rationale": "Iron Dome can denote a system family, a particular configuration or deployed equipment; these meanings must remain distinguishable.", "layers": [ { "id": "family-identity", "name": "Family Identity", "description": "Records the evidence that a designation belongs to the registered system family.", "findings": [ { "id": "documented-family-membership", "name": "Documented Family Membership", "description": "Recognition requires attributable identity evidence rather than resemblance or a shared defensive role.", "questions": [ { "text": "Which authoritative record identifies this designation as Iron Dome or a member of its system family?", "kind": "provenance", "id": "documented-family-membership-q01" }, { "text": "Does the designation identify the family, a configuration, a battery or a component?", "kind": "definition", "id": "documented-family-membership-q02" } ] } ] }, { "id": "adjacent-system-boundaries", "name": "Adjacent System Boundaries", "description": "Separates the registered concept from related naval products, component offerings and wider defence networks.", "findings": [ { "id": "variant-versus-neighbour", "name": "Variant Versus Neighbour", "description": "Related branding or shared components alone do not settle whether another product belongs within this entry.", "questions": [ { "text": "How do authoritative product records describe the relationship between Iron Dome and C-Dome?", "kind": "boundary", "id": "variant-versus-neighbour-q01" }, { "text": "Which functions belong to Iron Dome itself and which belong to an external integrated defence network?", "kind": "boundary", "id": "variant-versus-neighbour-q02" } ] } ] } ] }, { "id": "functional-chain-and-configuration", "name": "Functional Chain and Configuration", "description": "Describes the system-level relationship between tracking, assessment, coordination and interception.", "rationale": "Iron Dome is recognised and assessed through connected functions, not merely the presence of missile launchers.", "layers": [ { "id": "detection-to-assessment", "name": "Detection to Assessment", "description": "Captures the distinction between observing a trajectory and assessing its relevance to a protected area.", "findings": [ { "id": "selective-threat-assessment", "name": "Selective Threat Assessment", "description": "The model records the documented role of predicted-impact assessment without encoding operational thresholds or engagement settings.", "questions": [ { "text": "How does the configuration's documentation distinguish tracking a threat from judging that it warrants interception?", "kind": "definition", "id": "selective-threat-assessment-q01" }, { "text": "Which source establishes the respective roles of the radar and battle-management functions in that assessment?", "kind": "provenance", "id": "selective-threat-assessment-q02" } ] } ] }, { "id": "interception-chain", "name": "Interception Chain", "description": "Relates battle management, launch equipment and interceptors within a documented configuration.", "findings": [ { "id": "supported-component-combination", "name": "Supported Component Combination", "description": "A valid configuration needs evidence of supported relationships among its constituent equipment and software baselines.", "questions": [ { "text": "Which documented launcher, interceptor and battle-management versions belong to this configuration?", "kind": "provenance", "id": "supported-component-combination-q01" }, { "text": "What approval evidence is required before a substituted component or software revision is accepted into the configuration?", "kind": "action", "id": "supported-component-combination-q02" } ] } ] } ] }, { "id": "capability-and-effectiveness-evidence", "name": "Capability and Effectiveness Evidence", "description": "Qualifies statements about threat coverage, engagement envelopes and interception outcomes.", "rationale": "Iron Dome performance figures are interpretable only when their denominators, conditions and configuration applicability are explicit.", "layers": [ { "id": "coverage-claims", "name": "Coverage Claims", "description": "Separates threat categories and different meanings of range or coverage.", "findings": [ { "id": "qualified-capability-envelope", "name": "Qualified Capability Envelope", "description": "Each capability statement must identify its configuration and distinguish the quantity actually being described.", "questions": [ { "text": "Which threat classes are documented for this configuration, and is the evidence a claim, test result or operational report?", "kind": "provenance", "id": "qualified-capability-envelope-q01" }, { "text": "Does a quoted distance describe the incoming threat's range, interception distance, altitude or defended footprint?", "kind": "measurement", "id": "qualified-capability-envelope-q02" } ] } ] }, { "id": "outcome-interpretation", "name": "Outcome Interpretation", "description": "Makes interception statistics and their evidential limitations comparable.", "findings": [ { "id": "defined-success-denominator", "name": "Defined Success Denominator", "description": "A success percentage is incomplete without a defined outcome, counted population and treatment of non-engaged threats.", "questions": [ { "text": "Does the reported percentage use all detected threats, threats assessed as dangerous, attempted engagements or another denominator?", "kind": "measurement", "id": "defined-success-denominator-q01" }, { "text": "How was successful interception established, and what uncertainty or independent verification accompanies the result?", "kind": "provenance", "id": "defined-success-denominator-q02" } ] } ] } ] }, { "id": "readiness-and-controlled-support", "name": "Readiness and Controlled Support", "description": "Connects system condition, support dependencies and lifecycle work to documented authority.", "rationale": "The condition of Iron Dome depends on the integrated system and its controlled explosive components, not a single equipment status.", "layers": [ { "id": "integrated-readiness", "name": "Integrated Readiness", "description": "Distinguishes component condition from a supported declaration about the complete configuration.", "findings": [ { "id": "readiness-with-evidence", "name": "Readiness With Evidence", "description": "Readiness records retain the assessed configuration, responsible authority, assessment date and unresolved restrictions.", "questions": [ { "text": "Which authorised record establishes the readiness state of the complete configuration rather than one radar or launcher?", "kind": "provenance", "id": "readiness-with-evidence-q01" }, { "text": "Which missing or expired power, communications, inspection or support evidence prevents a current readiness assessment?", "kind": "boundary", "id": "readiness-with-evidence-q02" } ] } ] }, { "id": "maintenance-and-handling-authority", "name": "Maintenance and Handling Authority", "description": "Records the applicable controls for support work, interceptor handling and return to service.", "findings": [ { "id": "authorised-lifecycle-actions", "name": "Authorised Lifecycle Actions", "description": "Support actions depend on the exact equipment identity, applicable instructions and the authority of qualified personnel.", "questions": [ { "text": "Which current manufacturer and operator instructions govern maintenance, storage, transport and disposal for the identified equipment?", "kind": "provenance", "id": "authorised-lifecycle-actions-q01" }, { "text": "Who may authorise the requested support action and certify the affected equipment's return to service?", "kind": "action", "id": "authorised-lifecycle-actions-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This description is recalled knowledge, not source-verified research; deployment counts, configurations and supported target classes require checking.", "Reported interception percentages depend on how threatening trajectories and successful engagements are counted; no universal effectiveness figure is asserted.", "Published range figures can describe incoming rockets rather than interceptor reach or defended area; measurements are omitted to avoid conflating these quantities." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Iron Dome this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Land-based Iron Dome", "Naval C-Dome variant" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Iron Dome this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Defence of populated areas and critical infrastructure against short-range rocket attacks.", "Protection of military forces and installations against selected aerial threats.", "Naval air defence through the C-Dome variant.", "Operation as the short-range component of Israel's layered missile-defence architecture." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Iron Dome this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Interceptions can fail, allowing an incoming threat to reach the defended area.", "Simultaneous attacks can exceed available engagement capacity or interceptor stocks.", "Radar, communications, power or battle-management failures can impair protection.", "Falling interceptor and target debris can cause injury and damage.", "Interceptor storage, handling and launch involve explosive and propulsion hazards." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Iron Dome this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Israeli deployment forms part of a layered defence that also includes David's Sling and Arrow.", "Export configurations and integration with national command systems can differ from Israeli configurations." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Iron Dome this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Tamir", "difference": "Tamir is an interceptor missile used by Iron Dome; Iron Dome is the complete defensive system." }, { "name": "Iron Dome battery", "difference": "A battery is an operational grouping of system equipment; Iron Dome names the system family rather than an individual deployed unit." }, { "name": "David's Sling", "difference": "David's Sling is a separate system addressing a different, generally longer-range threat tier." }, { "name": "Arrow", "difference": "Arrow is a separate family focused on ballistic-missile defence at higher defensive tiers." }, { "name": "Iron Beam", "difference": "Iron Beam uses laser energy for interception, whereas Iron Dome uses interceptor missiles." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Iron Dome this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already cover Iron Dome, requiring this registry entry to link to that publication?", "Should C-Dome and other related named configurations be represented as variants or neighbouring models under the registry's authoritative granularity?", "Which authoritative public sources establish configuration-specific component identities, threat coverage and capability limits?", "Which effectiveness reports provide sufficiently clear denominators, outcome definitions and verification to support comparison?", "Which maintenance, certification, handling and readiness requirements can be established from accessible authoritative documentation?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 22 } }, "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 Iron Dome, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise Iron Dome, distinguish its system configurations, assess documented condition and evidence, and identify authorised support actions.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 66 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 Iron Dome, 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 Iron Dome looks like has to come from research." ], "relatedModels": [], "standing": "Described in 66 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 Iron Dome from another, and a Iron Dome 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 Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Iron Dome 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 Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Iron Dome performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Iron Dome at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome 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 Iron Dome and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 Iron Dome is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Iron Dome, 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 Iron Dome, 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 Iron Dome 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 } } } }