{ "model": { "rank": 5976, "code": "thing-q249091", "model_id": "vr.tr.falcon-9", "name": "Falcon 9", "purpose": "Enable an AI agent to identify a Falcon 9 configuration or flight article, assess its mission suitability and observed condition, and determine which actions its evidence and authorization support.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q249091/", "tier": 2, "score": 63, "payload": { "layer": "wikidata", "aliases": [ "Falcon Heavy", "Falcon 9 v1.1", "Falcon 9 v1.0", "Falcon 9 Full Thrust", "Falcon 9 Block 5", "Falcon 9 Block 4" ], "aliasCount": 6, "merged": 6, "knownIn": 63, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q249091", "url": "https://www.wikidata.org/wiki/Q249091", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:27:57Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.01096942, "turns": 1, "seconds": 126.9, "error": null }, "codex": { "seconds": 100.8, "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: 01a07b64-f835-7583-ab67-c44fbd910a2d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Falcon 9\nRegistry id: vr.tr.falcon-9\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy" } } }, "metaModel": { "id": "THING-Q249091", "registryId": "vr.tr.falcon-9", "name": "Falcon 9", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q249091/", "model": { "registry_id": "vr.tr.falcon-9", "name": "Falcon 9", "purpose": "Enable an AI agent to identify a Falcon 9 configuration or flight article, assess its mission suitability and observed condition, and determine which actions its evidence and authorization support.", "definition": "Falcon 9 is SpaceX's two-stage, RP-1/liquid-oxygen orbital launch vehicle whose first stage uses nine Merlin engines and is designed for propulsive recovery and reuse, with a single Merlin Vacuum engine on the second stage.", "scope_statement": "Owns the recognition and assessment model for Falcon 9 under vr.tr.falcon-9, distinguishing the vehicle family, configuration, assembled launch vehicle and individually tracked stages without creating separate registry entries.", "in_scope": [ "Falcon 9 configuration identity, historical applicability and stage composition", "Association of an assembled vehicle with its booster, upper stage and payload accommodation", "Mission-specific payload compatibility and delivery capability", "Vehicle readiness, flight-phase state and anomaly disposition", "Booster recovery, inspection and eligibility for another flight", "Evidence supporting vehicle assessments and permitted state transitions" ], "out_of_scope": [ "Falcon Heavy as a complete launch vehicle", "Dragon or satellite internal systems and independent mission operations", "Merlin engine design and component-level maintenance procedures", "Launch-site, range and recovery-vessel infrastructure management", "SpaceX corporate operations, launch-service pricing and contracts", "Detailed trajectory optimization and executable launch-control procedures" ], "distinguishing_features": [ "Check for a two-stage Falcon 9 architecture with one first-stage core; Falcon Heavy uses three cores. [SpaceX Falcon User's Guide](https://www.spacex.com/assets/media/falcon-users-guide-2025-05-09.pdf)", "Check for nine first-stage Merlin engines and a Merlin Vacuum upper-stage engine, with engine revision matched to vehicle version. [SpaceX Falcon User's Guide](https://www.spacex.com/assets/media/falcon-users-guide-2025-05-09.pdf)", "Check for liquid-oxygen and RP-1 propulsion rather than assigning identity from rocket silhouette alone. [SpaceX Falcon User's Guide](https://www.spacex.com/assets/media/falcon-users-guide-2025-05-09.pdf)", "Determine whether a reference identifies the Falcon 9 family, an assembled vehicle, a booster alone or its carried spacecraft; a booster identifier does not identify the complete launch stack." ], "characteristics": [ { "name": "Configuration applicability", "kind": "category", "unit_or_values": "Documented vehicle version, block, modification baseline and effective date; unknown permitted", "why_it_matters": "Prevents specifications and permissions from migrating between incompatible Falcon 9 configurations." }, { "name": "Flight-article composition", "kind": "relation", "unit_or_values": "Launch vehicle linked to booster identifier, upper-stage identifier, payload accommodation and mission", "why_it_matters": "Keeps reused hardware identity distinct from a particular assembled vehicle." }, { "name": "Booster flight history", "kind": "measurement", "unit_or_values": "Completed flights and recovery attempts, counted separately and dated", "why_it_matters": "Supports inspection assessment without treating flight count as proof of remaining life." }, { "name": "Payload configuration", "kind": "category", "unit_or_values": "Fairing-enclosed payload, Dragon configuration or other documented arrangement", "why_it_matters": "Selects the applicable accommodation and integration evidence." }, { "name": "Payload mass and fit", "kind": "measurement", "unit_or_values": "kg; envelope and center-of-gravity coordinates in m with reference frame", "why_it_matters": "Supports assessment against the selected vehicle and adapter configuration." }, { "name": "Required delivery condition", "kind": "measurement", "unit_or_values": "Position in km and velocity in km/s with epoch and reference frame, plus acceptance tolerances", "why_it_matters": "Makes payload-delivery success assessable beyond a generic destination label." }, { "name": "Booster recovery disposition", "kind": "category", "unit_or_values": "Land recovery planned, droneship recovery planned, intentional expenditure or unresolved", "why_it_matters": "Conditions mission capability and the expected post-separation outcome." }, { "name": "Vehicle lifecycle state", "kind": "state", "unit_or_values": "Integration, checkout, hold, ready, flight, postflight, retired or unknown; timestamp required", "why_it_matters": "Determines which assessments and authorized transitions are relevant." }, { "name": "Propellant and stored-energy condition", "kind": "state", "unit_or_values": "Documented loading, pressurization and safing status by stage; unknown permitted", "why_it_matters": "Constrains handling and access decisions." }, { "name": "Readiness disposition", "kind": "state", "unit_or_values": "Pending, accepted, conditional, held or unknown, with issuing authority and validity", "why_it_matters": "Separates observed condition from permission to proceed." }, { "name": "Postflight hardware disposition", "kind": "state", "unit_or_values": "Unrecovered, recovered awaiting inspection, refurbishment required, accepted for reuse or retired", "why_it_matters": "Prevents successful landing from being interpreted as automatic flight eligibility." } ], "affordances": [ "Resolve a Falcon 9 reference to its configuration, mission and constituent flight articles.", "Screen a proposed payload and delivery requirement against documented configuration-specific capability.", "Identify missing integration evidence and unresolved readiness constraints.", "Reconcile reported flight events with separate payload-delivery and booster-recovery outcomes.", "Recommend hold, inspection, refurbishment or retirement review from documented condition and authority.", "Determine whether an authorized next step has current supporting evidence." ] }, "sources": [ { "id": "spacex-f9-vehicle", "title": "Falcon 9", "url": "https://www.spacex.com/vehicles/falcon-9/", "what_it_supports": "Manufacturer description of the current Block 5 vehicle, engines, reuse, and published performance figures.", "url_status": "blocked" }, { "id": "spacex-f9-users-guide", "title": "Falcon User's Guide", "url": "https://www.spacex.com/media/falcon-users-guide-2021-09.pdf", "what_it_supports": "Stage layout, fairing, environments, interfaces, and the LEO/GTO/TLI performance numbers used in practice by payload customers.", "url_status": "blocked" }, { "id": "faa-14cfr-450", "title": "14 CFR Part 450 - Launch and Reentry License Requirements", "url": "https://www.ecfr.gov/current/title-14/chapter-III/subchapter-C/part-450", "what_it_supports": "U.S. licensing of Falcon 9 launch and first-stage reentry/landing as a commercial space transportation system.", "url_status": "live" }, { "id": "nasa-ccp-f9", "title": "NASA Commercial Crew Program - SpaceX Falcon 9 / Crew Dragon", "url": "", "what_it_supports": "Human-rated use of Falcon 9 Block 5 for crew transport to the International Space Station.", "url_status": "dead" } ], "structure": { "bundles": [ { "id": "falcon-9-identity-and-configuration", "name": "Falcon 9 Identity and Configuration", "description": "Establishes what a Falcon 9 reference denotes and which configuration-specific statements apply.", "rationale": "The family name alone cannot identify a launch stack or establish that a specification applies to its hardware.", "layers": [ { "id": "family-and-version", "name": "Family and Version", "description": "Locates the subject within Falcon 9 configuration history.", "findings": [ { "id": "configuration-applicability", "name": "Configuration Applicability", "description": "Record the documented version and the limits of evidence applied to it.", "questions": [ { "text": "Which Falcon 9 version and modification baseline does this reference describe?", "kind": "definition", "id": "configuration-applicability-q01" }, { "text": "Which dated manufacturer or operator evidence establishes that identification?", "kind": "provenance", "id": "configuration-applicability-q02" }, { "text": "Which characteristics remain unverified for this version rather than inheritable from another Falcon 9?", "kind": "boundary", "id": "configuration-applicability-q03" } ] } ] }, { "id": "stack-and-stage-identity", "name": "Stack and Stage Identity", "description": "Separates vehicle assembly identity from the histories of its constituent articles.", "findings": [ { "id": "flight-article-association", "name": "Flight-Article Association", "description": "Record which booster, upper stage and payload accommodation constitute the vehicle for a particular mission.", "questions": [ { "text": "Does the identifier denote a complete Falcon 9, a booster, an upper stage or a mission?", "kind": "definition", "id": "flight-article-association-q01" }, { "text": "What evidence associates these articles with this launch assembly?", "kind": "provenance", "id": "flight-article-association-q02" }, { "text": "Which histories belong to the reused booster rather than to the newly assembled launch vehicle?", "kind": "boundary", "id": "flight-article-association-q03" } ] } ] } ] }, { "id": "payload-accommodation-and-delivery", "name": "Payload Accommodation and Delivery", "description": "Assesses whether a specified Falcon 9 configuration can accommodate and deliver a particular payload.", "rationale": "A family-level payload figure cannot settle compatibility or capability for a specific mission.", "layers": [ { "id": "payload-integration", "name": "Payload Integration", "description": "Connects the payload arrangement to applicable interface and qualification evidence.", "findings": [ { "id": "accommodation-compatibility", "name": "Accommodation Compatibility", "description": "Record fit, attachment and environmental acceptance for the chosen payload configuration.", "questions": [ { "text": "Which fairing or Dragon configuration and attachment interfaces apply to this Falcon 9?", "kind": "definition", "id": "accommodation-compatibility-q01" }, { "text": "Do payload mass, envelope and center of gravity satisfy the documented accommodation limits?", "kind": "measurement", "id": "accommodation-compatibility-q02" }, { "text": "Which interface and environmental verification results remain necessary before integration can be accepted?", "kind": "action", "id": "accommodation-compatibility-q03" } ] } ] }, { "id": "mission-conditioned-performance", "name": "Mission-Conditioned Performance", "description": "Qualifies delivery capability by mission and vehicle assumptions.", "findings": [ { "id": "delivery-feasibility", "name": "Delivery Feasibility", "description": "Record the evidence that the requested delivery condition is achievable with the selected payload and recovery disposition.", "questions": [ { "text": "What payload separation state and tolerances define the requested delivery?", "kind": "measurement", "id": "delivery-feasibility-q01" }, { "text": "Which performance assessment supports this payload mass, launch site and booster recovery disposition?", "kind": "provenance", "id": "delivery-feasibility-q02" }, { "text": "Which changed assumptions would invalidate that feasibility assessment?", "kind": "boundary", "id": "delivery-feasibility-q03" } ] } ] } ] }, { "id": "stage-condition-and-launch-readiness", "name": "Stage Condition and Launch Readiness", "description": "Relates the condition of the Falcon 9 stages and integrated stack to a time-specific readiness assessment.", "rationale": "Hardware configuration, checkout results and operating state must agree before readiness can be inferred.", "layers": [ { "id": "propulsion-and-stack-condition", "name": "Propulsion and Stack Condition", "description": "Records stage-level condition without substituting for subsystem maintenance models.", "findings": [ { "id": "stage-checkout-disposition", "name": "Stage Checkout Disposition", "description": "Associate propulsion, tank, avionics and separation-system assessment results with the installed hardware.", "questions": [ { "text": "Which acceptance and checkout records apply to the installed first and second stages?", "kind": "provenance", "id": "stage-checkout-disposition-q01" }, { "text": "What unresolved anomalies or configuration mismatches affect propulsion, guidance or separation readiness?", "kind": "measurement", "id": "stage-checkout-disposition-q02" }, { "text": "Which hardware or software changes require the readiness assessment to be repeated?", "kind": "action", "id": "stage-checkout-disposition-q03" } ] } ] }, { "id": "countdown-and-hold-state", "name": "Countdown and Hold State", "description": "Separates a reported countdown phase from verified permission to proceed.", "findings": [ { "id": "time-bounded-launch-readiness", "name": "Time-Bounded Launch Readiness", "description": "Record vehicle loading state, active constraints and the scope of the latest readiness disposition.", "questions": [ { "text": "What are the latest verified loading, pressurization and countdown states, and when were they observed?", "kind": "measurement", "id": "time-bounded-launch-readiness-q01" }, { "text": "Which vehicle holds or linked site, weather and range constraints remain active?", "kind": "boundary", "id": "time-bounded-launch-readiness-q02" }, { "text": "Who may accept the next transition, and what evidence must remain valid at that time?", "kind": "action", "id": "time-bounded-launch-readiness-q03" } ] } ] } ] }, { "id": "flight-progression-and-outcomes", "name": "Flight Progression and Outcomes", "description": "Tracks what the Falcon 9 accomplished during flight and distinguishes the outcomes of its separated elements.", "rationale": "Payload delivery, booster landing and upper-stage disposition are separate judgments.", "layers": [ { "id": "ascent-and-payload-release", "name": "Ascent and Payload Release", "description": "Evaluates mission progress through corroborated stage and payload events.", "findings": [ { "id": "delivery-event-evidence", "name": "Delivery Event Evidence", "description": "Record observed milestones and compare the achieved payload release condition with the mission requirement.", "questions": [ { "text": "Which ascent, stage-separation, upper-stage burn and payload-release events are confirmed rather than scheduled?", "kind": "provenance", "id": "delivery-event-evidence-q01" }, { "text": "How does the achieved separation state compare with the required state and tolerances?", "kind": "measurement", "id": "delivery-event-evidence-q02" }, { "text": "Where does Falcon 9 delivery responsibility end and independent spacecraft operation begin?", "kind": "boundary", "id": "delivery-event-evidence-q03" } ] } ] }, { "id": "separated-element-outcomes", "name": "Separated-Element Outcomes", "description": "Maintains independent outcomes after vehicle elements separate.", "findings": [ { "id": "outcome-separation", "name": "Outcome Separation", "description": "Record payload delivery, booster recovery, fairing recovery where applicable and upper-stage disposition without collapsing them into one success flag.", "questions": [ { "text": "What was the planned disposition of each separated Falcon 9 element?", "kind": "definition", "id": "outcome-separation-q01" }, { "text": "Which observations establish each actual outcome, including any unknown upper-stage disposition?", "kind": "provenance", "id": "outcome-separation-q02" }, { "text": "Which mission objective failed or remained unverified despite success elsewhere?", "kind": "boundary", "id": "outcome-separation-q03" } ] } ] } ] }, { "id": "booster-recovery-and-reflight", "name": "Booster Recovery and Reflight", "description": "Connects recovery observations to the identity, condition and subsequent eligibility of a Falcon 9 booster.", "rationale": "Recovery preserves hardware for assessment; it does not by itself establish readiness for another mission.", "layers": [ { "id": "recovery-and-retrieval", "name": "Recovery and Retrieval", "description": "Records the recovered article and evidence relevant to its handling and inspection.", "findings": [ { "id": "recovered-booster-condition", "name": "Recovered Booster Condition", "description": "Distinguish touchdown reports from verified retrieval, safing and condition assessment.", "questions": [ { "text": "Which booster was recovered, where, and with what confirmation of identity?", "kind": "provenance", "id": "recovered-booster-condition-q01" }, { "text": "What landing, transport or exposure damage and unresolved stored-energy conditions were recorded?", "kind": "measurement", "id": "recovered-booster-condition-q02" }, { "text": "Which handling or inspection actions are supported by the documented safing disposition?", "kind": "action", "id": "recovered-booster-condition-q03" } ] } ] }, { "id": "reuse-eligibility", "name": "Reuse Eligibility", "description": "Relates accumulated service and refurbishment evidence to the next proposed flight.", "findings": [ { "id": "reflight-acceptance", "name": "Reflight Acceptance", "description": "Record inspection closure, replaced hardware and the authorized disposition for reuse.", "questions": [ { "text": "Which flight and maintenance history belongs to this booster and its currently installed components?", "kind": "provenance", "id": "reflight-acceptance-q01" }, { "text": "Which inspections, repairs or unresolved anomalies constrain its next assignment?", "kind": "measurement", "id": "reflight-acceptance-q02" }, { "text": "What documented acceptance permits reflight, or requires further refurbishment or retirement?", "kind": "action", "id": "reflight-acceptance-q03" } ] } ] } ] }, { "id": "evidence-and-decision-authority", "name": "Evidence and Decision Authority", "description": "Makes Falcon 9 assessments traceable and limits decisions to the authority and evidence actually available.", "rationale": "Public specifications and launch coverage cannot establish internal flight acceptance or authorize physical operations.", "layers": [ { "id": "claim-applicability-and-confidence", "name": "Claim Applicability and Confidence", "description": "Qualifies statements by vehicle version, mission, date and evidence quality.", "findings": [ { "id": "traceable-vehicle-assessment", "name": "Traceable Vehicle Assessment", "description": "Keep published capability, mission-specific acceptance and observed state distinguishable.", "questions": [ { "text": "Does the supporting source address the Falcon 9 family, this configuration or this individual flight article?", "kind": "provenance", "id": "traceable-vehicle-assessment-q01" }, { "text": "Is the statement a published capability, an estimate, an observation or an authorized acceptance?", "kind": "definition", "id": "traceable-vehicle-assessment-q02" }, { "text": "What contradictory or stale evidence prevents a firm assessment?", "kind": "boundary", "id": "traceable-vehicle-assessment-q03" } ] } ] }, { "id": "authorized-next-actions", "name": "Authorized Next Actions", "description": "Connects proposed actions to specific dispositions and accountable decision makers.", "findings": [ { "id": "action-eligibility", "name": "Action Eligibility", "description": "Determine whether an agent can record, recommend or initiate a next step for the identified vehicle.", "questions": [ { "text": "Is the proposed action an analytical recommendation or an operational transition affecting Falcon 9 hardware?", "kind": "boundary", "id": "action-eligibility-q01" }, { "text": "Which current authorization and accepted evidence support that action for this vehicle and mission?", "kind": "provenance", "id": "action-eligibility-q02" }, { "text": "What missing evidence or unresolved hold requires referral to the responsible operator?", "kind": "action", "id": "action-eligibility-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": [ "Falcon 9 v1.0 (2010-2013, Merlin 1C, 3.6 m interstage, no landing legs)", "Falcon 9 v1.1 (stretched tanks, Merlin 1D, octaweb, first ASDS/RTLS attempts)", "Falcon 9 Full Thrust / v1.2 including Block 3 (subcooled propellant, higher thrust, first successful landings)", "Falcon 9 Block 4 (transitional Block 5 hardware, limited reuse)", "Falcon 9 Block 5 (current production: higher-thrust Merlin 1D+, titanium grid fins, designed for rapid reuse)", "Crew-capable Block 5 (NASA Commercial Crew configuration with Dragon 2, abort, and human-rating overlays)", "Recovery profile: RTLS (return to launch site), ASDS (droneship), or expendable first stage", "Fairing vs Dragon missions (5.2 m payload fairing versus Cargo/Crew Dragon as the second-stage payload)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q186509", "note": "Item for the Falcon 9 launch vehicle family, not individual boosters or missions." }, { "scheme": "SpaceX booster serial", "value_or_pattern": "B#### (Block 5 cores typically B1046-B10xx)", "note": "First-stage core identity used in flight manifests, landing records, and reuse counts; the stack as a whole is still called Falcon 9." }, { "scheme": "Common vehicle name / catalogue field", "value_or_pattern": "Falcon 9 or F9 (Space-Track / SATCAT launch-vehicle field often FALCON 9)", "note": "Mission-level catalogues name the launcher, not the booster serial." }, { "scheme": "COSPAR / international launch designator", "value_or_pattern": "YYYY-NNN (e.g. 2020-055) assigned to the launch, not to the vehicle type", "note": "Identifies the flight's objects, not the Falcon 9 design itself." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "FAA / AST: 14 CFR Parts 400-460, especially Part 450 launch and reentry licensing, plus vehicle operator licenses for SpaceX (United States).", "U.S. Commercial Space Launch Act: 51 U.S.C. Chapter 509 (licensing, third-party liability, indemnification).", "U.S. Space Force Eastern and Western Range safety requirements (descended from AFSPCMAN 91-710 / RCC 319 flight-termination and public-risk criteria).", "ITAR: U.S. Munitions List Category IV (launch vehicles and related technical data), 22 CFR Parts 120-130.", "NASA Commercial Crew: CCT-REQ-1130 and related human-rating / ISS visiting-vehicle requirements for crewed Falcon 9/Dragon flights.", "NASA Launch Services Program requirements for science/cargo missions flown under NLS-class contracts.", "FCC licenses for launch telemetry, tracking, and (separately) many Falcon 9 payloads; NOAA licenses when the payload is U.S. remote sensing.", "UN treaties implemented via national licensing: Outer Space Treaty (1967) and Liability Convention (1972), with U.S. registry of space objects." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Commercial satellite deployment from Cape Canaveral Space Force Station SLC-40, Kennedy Space Center LC-39A, and Vandenberg Space Force Base SLC-4E.", "High-cadence Starlink constellation launches, now the majority of Falcon 9 flights.", "NASA cargo (CRS Dragon) and crew (Crew Dragon) transport to the International Space Station.", "U.S. national-security launches (NSSL and related missions) once Falcon 9 was certified for that class of payloads.", "Geostationary-transfer, medium-Earth, and Earth-escape missions (science probes, lunar logistics) using the expendable or partially expended performance margin.", "First-stage recovery as a routine operations step: landing at LZ-1/LZ-2 (Florida), LZ-4 (Vandenberg), or Atlantic/Pacific droneships, then refurbishment and reflights of the same booster." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Vehicle height (Block 5, with fairing)", "typical_range": "70", "unit": "m" }, { "quantity": "First- and second-stage diameter", "typical_range": "3.66", "unit": "m" }, { "quantity": "Payload-fairing outer diameter", "typical_range": "5.2", "unit": "m" }, { "quantity": "Liftoff mass", "typical_range": "549000", "unit": "kg" }, { "quantity": "Sea-level thrust (nine Merlin 1D+, Block 5)", "typical_range": "7607", "unit": "kN" }, { "quantity": "Published payload to LEO, expendable", "typical_range": "22800", "unit": "kg" }, { "quantity": "Published payload to GTO, expendable", "typical_range": "8300", "unit": "kg" }, { "quantity": "First-stage flight count (Block 5 operational reuse)", "typical_range": "1-20+", "unit": "flights" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Ascent vehicle breakup or engine-out beyond the design-allowable remaining engines; public-risk managed by flight termination and range safety.", "Second-stage helium COPV / tank structural failure (CRS-7, 2015) and on-pad second-stage explosion during fueling (AMOS-6, 2016).", "Upper-stage underperformance or attitude/propellant issues that leave payloads in unusable orbits (e.g. Starlink Group 7-3 / Flight 44, January 2024, cold-soak filter blockage).", "First-stage landing failure (ocean impact, hard landing, grid-fin or engine-relight faults), which is usually a loss of the booster rather than the payload.", "Fairing recovery failure or debris from expended stages; second stages left in orbit become tracked space objects and eventual debris.", "Ground hazards: RP-1/LOX fire or explosion on the pad, landing-zone overflight and sonic boom, and toxic/fire risk at the landing site.", "Crewed-flight unique hazards: launch-abort failure, Dragon separation or reentry faults (the crew system is a neighbour stack, but Falcon 9 is the energy source).", "Payload collision or contamination risk if the second stage or debris remains near the deployed objects." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Launches are U.S.-only (Florida east-coast azimuths versus Vandenberg polar/sun-synchronous); there is no operational Falcon 9 pad outside the United States.", "Landing practice differs by coast and energy: Florida RTLS to LZ-1/LZ-2 versus west-coast LZ-4 versus droneship landings in the Atlantic or Pacific.", "In U.S. government usage the vehicle is often specified as \"Falcon 9 Block 5\" plus a NASA/DoD mission designator; commercial manifests usually say \"Falcon 9\" plus booster serial (B10xx).", "Chinese-language reporting commonly uses 猎鹰9号; European coverage typically keeps \"Falcon 9\" untranslated.", "Human-spaceflight flights are described as Crew Dragon missions in NASA communications even though the launcher is still Falcon 9." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Falcon Heavy", "difference": "Three Falcon 9-class first-stage cores side by side (two strap-on boosters plus a center core) versus a single first-stage core; Heavy is a distinct vehicle with higher payload and different load paths." }, { "name": "Falcon 1", "difference": "Retired small launcher with one Merlin first-stage engine and a Kestrel second stage; not 3.66 m class and not orbital-crew capable." }, { "name": "Starship / Super Heavy", "difference": "Stainless-steel, methane/oxygen, fully reusable two-stage system with many Raptor engines; not RP-1 Merlin, not 3.66 m, and not the operational ISS crew/cargo vehicle as of 2026." }, { "name": "Merlin engine (as a standalone article)", "difference": "Merlin is the engine family; Falcon 9 is the launch vehicle that mounts nine sea-level Merlins plus one vacuum Merlin." }, { "name": "Dragon 2 (Crew/Cargo)", "difference": "The spacecraft on top of Falcon 9 for ISS missions; identified by Dragon capsule serial and NASA crew/cargo flight name, not by booster serial alone." }, { "name": "New Glenn (Blue Origin)", "difference": "7 m-class, BE-4 methane first stage, different operator and pads; not a nine-engine RP-1 core and not landed with Merlin relights." }, { "name": "Atlas V / Vulcan (ULA)", "difference": "Expendable (Atlas) or differently recovered (Vulcan) U.S. medium-heavy launchers with different engines (RD-180 or BE-4) and no Falcon-style nine-Merlin octaweb." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Falcon 9 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world-model publication already own Falcon 9 or its authoritative concept boundary, requiring a link rather than a separate publication?", "Which historical Falcon 9 versions and modification baselines need explicit coverage, and which characteristics are valid across them?", "Which mission-specific interface and performance documents are available, particularly for Dragon configurations and recovery-dependent capability?", "What authoritative booster inspection, life-limit and reflight-acceptance evidence is accessible beyond public flight counts?", "Which trusted sources can establish current article identity, readiness and upper-stage disposition when public reporting is incomplete or conflicting?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 20, "questions": 44 } }, "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 Falcon 9, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify a Falcon 9 configuration or flight article, assess its mission suitability and observed condition, and determine which actions its evidence and authorization support.", "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: Falcon Heavy, Falcon 9 v1.1, Falcon 9 v1.0, Falcon 9 Full Thrust, Falcon 9 Block 5, Falcon 9 Block 4.", "6 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 Falcon 9, 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 Falcon 9 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": [ "Falcon Heavy", "Falcon 9 v1.1", "Falcon 9 v1.0", "Falcon 9 Full Thrust", "Falcon 9 Block 5", "Falcon 9 Block 4" ] } ], "standing": "Described in 63 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 6 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 Falcon 9 from another, and a Falcon 9 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 Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Falcon 9 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 Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Falcon 9 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Falcon 9 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 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 Falcon 9 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 Falcon 9 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Falcon 9, 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 Falcon 9, 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 Falcon 9 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 } } } }