{ "model": { "rank": 1917, "code": "thing-q5503", "model_id": "vr.tr.rapid-transit", "name": "rapid transit", "purpose": "Enable an AI agent to recognise a rapid-transit system, assess its ability to move passengers reliably and safely, and identify feasible interventions within recorded operating constraints.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q5503/", "tier": 2, "score": 122, "payload": { "layer": "wikidata", "aliases": [ "medium-capacity rail transport system", "semi-metro", "premetro", "rapid transit in India", "Rapid transit in Taiwan", "automated rapid transit", "Berlin U-Bahn infrastructure", "rapid transit in the United States", "subway", "Fukuoka City Subway", "Subway in Japan" ], "aliasCount": 11, "merged": 11, "knownIn": 122, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q5503", "url": "https://www.wikidata.org/wiki/Q5503", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-06T22:06:16Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 2.2, "error": null, "retried": true }, "codex_seconds": 63.1 } }, "metaModel": { "id": "THING-Q5503", "registryId": "vr.tr.rapid-transit", "name": "rapid transit", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5503/", "model": { "registry_id": "vr.tr.rapid-transit", "name": "rapid transit", "purpose": "Enable an AI agent to recognise a rapid-transit system, assess its ability to move passengers reliably and safely, and identify feasible interventions within recorded operating constraints.", "definition": "", "scope_statement": "This model owns the identity, physical configuration, passenger-service capability and current operating state of an integrated rapid-transit system, including how its routes, stations, infrastructure and operating rules work together; the unresolved rail-only versus mode-inclusive registry boundary must remain explicit.", "in_scope": [ "System boundary, constituent lines and relationship between advertised routes and physical infrastructure", "Right-of-way separation, junction conflicts and station configuration", "Service patterns, operating periods, headways and passenger-carrying capability", "Passenger access, interchange and continuity of accessible journeys", "Infrastructure and fleet availability, degraded operation and recovery constraints" ], "out_of_scope": [ "Detailed engineering and maintenance records for individual vehicles, tracks, signals, lifts and other component assets", "The operator's corporate governance, staffing establishment and financial accounts", "Regional travel demand and the complete multimodal transport network", "Individual passenger journeys, tickets, payments and personal records", "Neighbourhood land use, property development and wider urban economic effects" ], "distinguishing_features": [ "Test the extent to which passenger movement has an exclusive right of way and whether road crossings or mixed traffic constrain operation; speed or branding alone does not establish the boundary.", "Test whether service supports repeated station-to-station travel across an urban area, rather than primarily long-distance or peak-direction regional journeys.", "Test actual service intervals and operating periods before treating the system as usable without planning around a particular departure; retain the observed values rather than assuming a universal frequency threshold.", "Test whether routes, stations and movement control form an integrated operating system, rather than a single vehicle, an isolated guideway or an advertised service name.", "For light rail, bus rapid transit and automated people movers, record the operating characteristics that support or challenge inclusion instead of deciding from the mode label." ], "characteristics": [ { "name": "Mode and classification basis", "kind": "category", "unit_or_values": "Recorded technology and local classification, with evidence and unresolved boundary flags", "why_it_matters": "Prevents an ambiguous registry label from silently determining which systems qualify." }, { "name": "Right-of-way separation", "kind": "category", "unit_or_values": "By segment: grade-separated exclusive, exclusive with level crossings, mixed traffic, or unknown", "why_it_matters": "Exposes external conflicts that affect service regularity and permissible operation." }, { "name": "Route-to-infrastructure mapping", "kind": "relation", "unit_or_values": "Passenger routes linked to station sequences, physical segments, junctions and turnbacks", "why_it_matters": "Shows which services share a constraint and which diversions or short workings are physically possible." }, { "name": "Service headway", "kind": "measurement", "unit_or_values": "Minutes between departures, by direction, segment and time period; distinguish planned and observed", "why_it_matters": "Supports assessment of waiting time, service gaps and uneven spacing." }, { "name": "Operating window", "kind": "measurement", "unit_or_values": "First and last usable departures by station, direction, calendar and time zone", "why_it_matters": "Determines when a passenger movement or interchange can actually be completed." }, { "name": "Passenger-carrying capability", "kind": "measurement", "unit_or_values": "Passengers per hour per direction at a named segment, with vehicle loading and service-frequency assumptions", "why_it_matters": "Allows demand and proposed service changes to be judged against a stated capacity basis." }, { "name": "Passenger loading", "kind": "measurement", "unit_or_values": "Passengers per vehicle or platform and percentage of a stated capacity, with location and observation time", "why_it_matters": "Identifies crowding and distinguishes observed loading from theoretical capacity." }, { "name": "Accessible journey continuity", "kind": "state", "unit_or_values": "Available, restricted, unavailable or unknown for a specified entrance-to-platform-to-vehicle-to-exit path and access requirement", "why_it_matters": "A station-level accessibility label cannot establish whether a complete journey is currently possible." }, { "name": "Operational availability", "kind": "state", "unit_or_values": "Normal, restricted, suspended, under recovery or unknown, by affected service and infrastructure segment", "why_it_matters": "Connects a disruption to the passenger services and movements it prevents." }, { "name": "Service delivery", "kind": "measurement", "unit_or_values": "Delivered versus planned departures and observed headway variation over a specified interval", "why_it_matters": "Distinguishes a published timetable from service passengers can rely on." }, { "name": "Operating authority", "kind": "relation", "unit_or_values": "Responsible bodies and roles linked to movement control, closures, maintenance access and restoration decisions", "why_it_matters": "Separates technically possible interventions from actions an agent or operator is authorised to take." } ], "affordances": [ "Determine whether a proposed passenger movement is supported at a specified time, including transfers and access requirements.", "Locate shared segments, junctions, platforms or turnbacks that constrain a proposed service pattern.", "Compare planned service, delivered service and passenger loading to identify a service shortfall.", "Trace an infrastructure or fleet restriction to affected routes, stations and accessible paths.", "Evaluate candidate frequency changes, short workings, closures or replacement connections against recorded capacity and operating rules.", "Prepare a disruption or restoration recommendation for the responsible authority, stating evidence gaps and required checks." ] }, "sources": [], "structure": { "bundles": [ { "id": "system-identity-and-boundary", "name": "System identity and boundary", "description": "Establishes what the registered rapid-transit thing includes and how it differs from neighbouring transport systems.", "rationale": "An agent must identify the operational thing before combining observations or proposing changes across its parts.", "layers": [ { "id": "classification-evidence", "name": "Classification evidence", "description": "Records the operating characteristics and source definitions behind inclusion as rapid transit.", "findings": [ { "id": "rapid-transit-inclusion", "name": "Rapid-transit inclusion", "description": "A supported classification decision with disputed or unresolved criteria retained explicitly.", "questions": [ { "text": "Which combination of right-of-way separation, service pattern and urban passenger function supports treating this system as rapid transit?", "kind": "definition", "id": "rapid-transit-inclusion-q01" }, { "text": "Which registry or authoritative transport definition establishes whether this entry includes bus rapid transit, light rail or people movers?", "kind": "provenance", "id": "rapid-transit-inclusion-q02" } ] } ] }, { "id": "operational-extent", "name": "Operational extent", "description": "Separates the integrated system from its branded services, individual lines and connecting networks.", "findings": [ { "id": "system-membership", "name": "System membership", "description": "The lines, stations and shared facilities included in the system, with interfaces to separately managed systems.", "questions": [ { "text": "Which lines, stations, depots and control facilities are constituents, and which are external connections or shared dependencies?", "kind": "boundary", "id": "system-membership-q01" }, { "text": "Where do branding, ownership, fare integration and operational control imply different system boundaries?", "kind": "boundary", "id": "system-membership-q02" } ] } ] } ] }, { "id": "guideway-and-route-configuration", "name": "Guideway and route configuration", "description": "Describes where vehicles can move and how passenger routes use the physical network.", "rationale": "Route maps alone cannot establish conflict exposure, shared bottlenecks or feasible changes to service.", "layers": [ { "id": "right-of-way-and-conflicts", "name": "Right of way and conflicts", "description": "Locates exclusive running sections and interfaces with other movements.", "findings": [ { "id": "movement-conflict-exposure", "name": "Movement conflict exposure", "description": "Segment-level separation and crossing conditions relevant to safe and regular operation.", "questions": [ { "text": "Which segments are grade-separated, cross other movements at level or share running space with other traffic?", "kind": "measurement", "id": "movement-conflict-exposure-q01" }, { "text": "What documented priority, protection or operating restrictions apply at each conflict point?", "kind": "provenance", "id": "movement-conflict-exposure-q02" } ] } ] }, { "id": "route-topology-and-turnbacks", "name": "Route topology and turnbacks", "description": "Links advertised services to actual paths, junctions, platforms and reversal facilities.", "findings": [ { "id": "feasible-service-paths", "name": "Feasible service paths", "description": "The physical paths and reversal options available for normal and altered service.", "questions": [ { "text": "Which routes share tracks or lanes, junctions, station berths and terminal reversal facilities?", "kind": "boundary", "id": "feasible-service-paths-q01" }, { "text": "Where can services terminate early, reverse, bypass a station or divert, and what restrictions govern each option?", "kind": "action", "id": "feasible-service-paths-q02" } ] } ] } ] }, { "id": "service-and-passenger-throughput", "name": "Service and passenger throughput", "description": "Connects scheduled and delivered service to passenger-carrying capability and loading.", "rationale": "An agent must distinguish nominal service from the frequency and capacity available at the location and time of a decision.", "layers": [ { "id": "service-pattern-and-delivery", "name": "Service pattern and delivery", "description": "Records where and when services run and how observed departures compare with the plan.", "findings": [ { "id": "usable-service-offer", "name": "Usable service offer", "description": "Direction-specific operating windows, stopping patterns and departure intervals with observed delivery.", "questions": [ { "text": "What stopping patterns, first and last departures, and planned headways apply by branch, direction and service calendar?", "kind": "measurement", "id": "usable-service-offer-q01" }, { "text": "What observed departure gaps, cancellations and headway variation occurred over the assessment period?", "kind": "measurement", "id": "usable-service-offer-q02" } ] } ] }, { "id": "capacity-and-loading", "name": "Capacity and loading", "description": "Relates vehicle capacity and achievable service frequency to demand at specific locations.", "findings": [ { "id": "binding-throughput-constraint", "name": "Binding throughput constraint", "description": "The evidenced limit on passenger throughput, including its assumptions and current loading.", "questions": [ { "text": "What passenger throughput is supported at the critical segment, using which vehicle capacity, loading standard and achievable departure rate?", "kind": "measurement", "id": "binding-throughput-constraint-q01" }, { "text": "Would the proposed service increase be limited by fleet availability, movement separation, junction conflicts, dwell time, platform clearance or terminal reversal?", "kind": "action", "id": "binding-throughput-constraint-q02" } ] } ] } ] }, { "id": "station-access-and-interchange", "name": "Station access and interchange", "description": "Represents the passenger paths that make the rapid-transit service reachable and usable.", "rationale": "A running service provides little usable capability when passengers cannot reach its platform, board or complete a transfer.", "layers": [ { "id": "accessible-boarding-paths", "name": "Accessible boarding paths", "description": "Connects entrances, circulation facilities, platforms and vehicle boarding interfaces.", "findings": [ { "id": "continuous-access-path", "name": "Continuous access path", "description": "The availability of a complete station and boarding path for a stated passenger access requirement.", "questions": [ { "text": "Which entrance-to-vehicle paths meet the specified access requirement, including level changes, platform gaps and any required assistance?", "kind": "boundary", "id": "continuous-access-path-q01" }, { "text": "Which lift failures, entrance closures or boarding restrictions currently break those paths, and when was their state verified?", "kind": "measurement", "id": "continuous-access-path-q02" } ] } ] }, { "id": "transfers-and-platform-circulation", "name": "Transfers and platform circulation", "description": "Records transfer paths and station circulation constraints that affect practical connectivity.", "findings": [ { "id": "usable-interchange", "name": "Usable interchange", "description": "Whether a mapped connection can be completed under current timing, access and crowding conditions.", "questions": [ { "text": "What walking time, level changes, fare-boundary crossings and operating-hour restrictions apply to each interchange path?", "kind": "measurement", "id": "usable-interchange-q01" }, { "text": "Under what recorded crowding or closure conditions must entry, transfer movements or platform access be restricted or redirected?", "kind": "action", "id": "usable-interchange-q02" } ] } ] } ] }, { "id": "operating-readiness-and-recovery", "name": "Operating readiness and recovery", "description": "Connects critical dependencies and operating restrictions to permitted service and restoration decisions.", "rationale": "Physical connectivity does not establish that a movement is currently safe, supported or authorised.", "layers": [ { "id": "critical-operating-dependencies", "name": "Critical operating dependencies", "description": "Identifies the fleet, power, control and infrastructure capabilities required by each service section.", "findings": [ { "id": "service-readiness", "name": "Service readiness", "description": "An evidence-backed assessment of whether the required operating capabilities are available.", "questions": [ { "text": "Which fleet, power supply, movement-control, communications and station capabilities are required to operate each section?", "kind": "boundary", "id": "service-readiness-q01" }, { "text": "Which dependencies are unavailable or restricted, what services are affected, and how current is the supporting status evidence?", "kind": "measurement", "id": "service-readiness-q02" } ] } ] }, { "id": "degraded-operation-and-restoration", "name": "Degraded operation and restoration", "description": "Records permitted responses to disruption and the conditions for returning to service.", "findings": [ { "id": "permitted-response-and-release", "name": "Permitted response and release", "description": "Applicable degraded-service options, decision authorities and restoration checks.", "questions": [ { "text": "Which documented degraded modes, section closures, short workings or passenger evacuation arrangements apply to the observed failure?", "kind": "action", "id": "permitted-response-and-release-q01" }, { "text": "Who may authorise the response and subsequent reopening, and what inspections, tests or operating confirmations must precede restoration?", "kind": "action", "id": "permitted-response-and-release-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.rapid-transit denote a rail metro system specifically, or a functional class that also includes qualifying bus rapid transit, light rail and people movers?", "Does an existing Vercy world model already own this concept or a substantial part of its system-level scope?", "What evidence should resolve system boundaries when branding, fare integration, physical connections and operating control disagree?", "Which capacity, accessibility and service-regularity definitions should be adopted, and which must remain jurisdiction-specific?", "Which authoritative operating sources and live status feeds are available, and how should evidence age limit an agent's recommendations?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "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 rapid transit, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a rapid-transit system, assess its ability to move passengers reliably and safely, and identify feasible interventions within recorded operating constraints.", "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: medium-capacity rail transport system, semi-metro, premetro, rapid transit in India, Rapid transit in Taiwan, automated rapid transit, Berlin U-Bahn infrastructure, rapid transit in the United States, subway, Fukuoka City Subway, Subway in Japan.", "11 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 122 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 rapid transit, 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, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "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": [ "medium-capacity rail transport system", "semi-metro", "premetro", "rapid transit in India", "Rapid transit in Taiwan", "automated rapid transit", "Berlin U-Bahn infrastructure", "rapid transit in the United States", "subway", "Fukuoka City Subway", "Subway in Japan" ] } ], "standing": "Described in 122 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 11 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 rapid transit from another, and a rapid transit 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 rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit 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 rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit 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 rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit 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 rapid transit is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit 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 rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit 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 rapid transit between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a rapid transit 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 rapid transit, 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 rapid transit, 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 rapid transit is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What rapid transit is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does rapid transit perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise rapid transit, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How rapid transit is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does rapid transit have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does rapid transit need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about rapid transit is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about rapid transit hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern rapid transit, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a rapid transit 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 rapid transit and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a rapid transit, 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 rapid transit, 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 rapid transit 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 rapid transit is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a rapid transit, 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 rapid transit, 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 rapid transit is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }