{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:25:49Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0955c-9d85-72f0-b3f2-0bca71a1409a\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: MP 05\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 registere", "usd": 0.0, "recall": true }, "codex": { "seconds": 79.7, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0955c-9d8c-7b42-8e33-dd343ecf1f80\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: MP 05\nRegistry id: vr.tr.mp-05\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for " } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:55:53+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:28+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q2318135", "registryId": "vr.tr.mp-05", "name": "MP 05", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2318135/", "model": { "registry_id": "vr.tr.mp-05", "name": "MP 05", "purpose": "Enable an agent to recognise the MP 05 Paris Métro rolling-stock type, assess evidence about its configuration and condition, and determine the prerequisites for operation, maintenance or reassignment.", "definition": "MP 05 is a class of rubber-tyred, electrically powered metro trainsets built by Alstom for fully automatic operation on the Paris Métro.", "scope_statement": "This model owns the type-level identity, configuration constraints and assessment questions for MP 05 under vr.tr.mp-05; individual trainsets supply observations and maintenance records without becoming separate definitions of the type.", "in_scope": [ "MP 05 identification and distinctions from MP 89, MP 14 and steel-wheel metro stock", "Train formation, passenger layout and platform interfaces", "Rubber-tyred running gear, electrical traction and braking requirements", "Onboard automation, operating modes and compatibility with a particular line", "MP 05 maintenance dependencies, configuration changes and return-to-service evidence" ], "out_of_scope": [ "General principles shared by all metro trains", "Individual trainset asset histories as standalone models", "Track, power supply, platform doors and signalling infrastructure themselves", "RATP organisational responsibilities and network timetable planning", "MP 89 and MP 14 specifications except where needed for identification or compatibility boundaries" ], "distinguishing_features": [ "Require an MP 05 designation in a manufacturer or operator record; appearance, livery and service line alone do not establish the type.", "Check for rubber-tyred running gear and driverless design, distinguishing MP 05 from steel-wheel metro stock and manually driven stock. These attributes are documented by [Alstom's Line 1 introduction](https://www.alstom.com/press-releases-news/2011/11/automating-line-1-paris-metro).", "Check the documented six-car, approximately 90 m formation and three passenger doorways per car side as supporting identification evidence. [Alstom's MP05 completion announcement](https://www.alstom.com/press-releases-news/2015/10/alstom-and-ratp-celebrate-the-67th-and-final-mp05-metro-train-).", "Do not identify a six-car automated train as MP 05 solely from formation and automation: MP 14 also includes a six-car automated version. Require the recorded type and equipment baseline. [Alstom's MP14 introduction](https://www.alstom.com/press-releases-news/2020/10/alstoms-mp14-metro-enters-commercial-service-paris)." ], "characteristics": [ { "name": "Recorded rolling-stock type", "kind": "category", "unit_or_values": "MP 05; conflicting identification; unverified", "why_it_matters": "Prevents inheritance of specifications from visually similar MP 89 or MP 14 stock." }, { "name": "Train formation", "kind": "measurement", "unit_or_values": "Cars per trainset; six in the manufacturer-described configuration", "why_it_matters": "Constrains train length, passenger accommodation and configuration conformity." }, { "name": "Train length", "kind": "measurement", "unit_or_values": "m; manufacturer describes 90 m, with exact measurement convention to verify", "why_it_matters": "Supports checks against platform length, stopping allowance and depot accommodation." }, { "name": "Passenger doorway arrangement", "kind": "measurement", "unit_or_values": "Doorways per car side; three in the manufacturer-described configuration", "why_it_matters": "Supports platform-door alignment and boarding assessments." }, { "name": "Speed envelope", "kind": "measurement", "unit_or_values": "km/h; manufacturer reports a maximum of 80; record authorised operating limits separately", "why_it_matters": "Separates type capability from route and condition restrictions." }, { "name": "Passenger capacity basis", "kind": "measurement", "unit_or_values": "Persons per trainset, seats and standing persons/m²; values require an explicit loading convention", "why_it_matters": "Prevents incompatible capacity figures from being treated as equivalent." }, { "name": "Automation configuration", "kind": "relation", "unit_or_values": "Onboard hardware and software baseline linked to a documented compatible line configuration", "why_it_matters": "Driverless capability alone does not establish permission to operate on another line." }, { "name": "Electrical supply compatibility", "kind": "measurement", "unit_or_values": "V DC, permitted variation and current-collection arrangement; authoritative values unresolved", "why_it_matters": "Supports traction-power and depot-interface assessment." }, { "name": "Operational disposition", "kind": "state", "unit_or_values": "Released; restricted; isolated; under maintenance; awaiting verification", "why_it_matters": "Links an observed trainset condition to the applicable MP 05 operating and maintenance rules." } ], "affordances": [ "Classify a candidate trainset as MP 05 using recorded identity and supporting physical evidence.", "Compare its installed configuration with the MP 05 baseline applicable to a proposed line assignment.", "Assess platform fit, doorway alignment and passenger accommodation using documented dimensions.", "Identify missing evidence before a trainset enters automatic passenger service or a degraded operating mode.", "Map observed running-gear, door, traction or automation defects to the applicable maintenance decision.", "Trace modifications and inspection evidence needed for return to service." ], "agent_conduct": { "may": [ "Describe the trainsets, their rubber-tyred running gear and their fully automatic operation.", "Report faults and passenger alarms to the operator's control centre." ], "must_not": [ "Override automatic train protection or platform door interlocks.", "Move or stop trains without the operator's control centre authorising it.", "Share passenger video or travel data without legal basis.", "Interfere with signalling or communications systems." ], "requires_human": [ "Evacuating passengers from a stalled train.", "Returning a train to service after an incident." ] }, "ethics": { "considerations": [ "Driverless trains place full trust in automated safety systems; passengers cannot intervene." ], "affected_parties": [ "Passengers", "Maintenance staff", "People on platforms" ] }, "owners": { "steward": "The metro operator; the transport safety authority approves the rolling stock.", "master_systems": [] }, "visual_identification": [ "A modern rubber-tyred metro train without a driving cab.", "Runs on lines with platform screen doors, with a wide front window open to passengers." ], "failure_modes_and_hazards": [ "Software or signalling faults can stop trains in tunnels.", "Overcrowding in a stalled train causes heat stress.", "Tyre faults can cause smoke in tunnels." ], "standards_and_regulation": [ "IEC 62267, Railway applications, Automated urban guided transport (AUGT), Safety requirements, International Electrotechnical Commission." ], "what_it_is_for": [ "This rolling-stock class is used for urban passenger transport on compatible rubber-tyred routes of the Paris metro system.", "It is designed for fully automatic service within an integrated system of train control, stations and supporting infrastructure.", "Maintenance and fleet planning require evidence about each trainset's configuration, condition and compatibility with its assigned route." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q2318135: MP 05", "url": "https://www.wikidata.org/wiki/Q2318135", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: MP 05", "url": "https://en.wikipedia.org/wiki/MP_05", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "mp05-identity-and-configuration", "name": "MP 05 identity and configuration", "description": "Establish what belongs to the registered MP 05 type and how installed configurations remain traceable.", "rationale": "Similar metro stock and changing line assignments make visual identification and route-based classification unreliable.", "layers": [ { "id": "type-identification", "name": "Type identification", "description": "Connect the registry entry to authoritative rolling-stock designations.", "findings": [ { "id": "documented-mp05-membership", "name": "Documented MP 05 membership", "description": "Record evidence identifying the type before assigning MP 05 characteristics to a candidate trainset.", "questions": [ { "text": "Which manufacturer or operator record explicitly identifies the candidate as MP 05?", "kind": "provenance", "id": "documented-mp05-membership-q01" }, { "text": "Which identifiers or equipment distinctions exclude MP 89 CA, MP 89 CC and MP 14?", "kind": "boundary", "id": "documented-mp05-membership-q02" } ] } ] }, { "id": "configuration-lineage", "name": "Configuration lineage", "description": "Separate the MP 05 design identity from delivery batches, modifications and route assignments.", "findings": [ { "id": "applicable-equipment-baseline", "name": "Applicable equipment baseline", "description": "Treat a delivery configuration and subsequent modifications as dated evidence, without assuming every MP 05 has identical equipment.", "questions": [ { "text": "Which delivery baseline and approved modifications define this MP 05 configuration?", "kind": "provenance", "id": "applicable-equipment-baseline-q01" }, { "text": "Which changes require renewed compatibility assessment while leaving the train classified as MP 05?", "kind": "boundary", "id": "applicable-equipment-baseline-q02" } ] } ] } ] }, { "id": "formation-and-passenger-interface", "name": "Formation and passenger interface", "description": "Describe the MP 05 train envelope, passenger circulation and interfaces with station platforms.", "rationale": "Formation and doorway geometry constrain deployment independently of automation compatibility.", "layers": [ { "id": "train-envelope", "name": "Train envelope", "description": "Capture formation, dimensions and permissible geometric clearances.", "findings": [ { "id": "formation-and-platform-fit", "name": "Formation and platform fit", "description": "Use the documented six-car formation and nominal length as starting evidence, then obtain engineering dimensions for clearance decisions.", "questions": [ { "text": "What are the approved MP 05 overall length, width, height and swept envelope, including measurement conventions?", "kind": "measurement", "id": "formation-and-platform-fit-q01" }, { "text": "What stopping allowance and platform clearance must a proposed station provide for this configuration?", "kind": "boundary", "id": "formation-and-platform-fit-q02" } ] } ] }, { "id": "boarding-and-accommodation", "name": "Boarding and accommodation", "description": "Assess doorway placement, passenger movement and accommodation conditions.", "findings": [ { "id": "usable-passenger-accommodation", "name": "Usable passenger accommodation", "description": "Record capacity assumptions, doorway geometry and accessibility evidence alongside the actual interior configuration.", "questions": [ { "text": "What seating count, usable standing area and standing-density convention support the stated MP 05 capacity?", "kind": "measurement", "id": "usable-passenger-accommodation-q01" }, { "text": "What doorway positions, clear openings and platform gaps govern accessible boarding and platform-door alignment?", "kind": "measurement", "id": "usable-passenger-accommodation-q02" }, { "text": "Which passenger-service restrictions apply if a doorway, inter-car passage or ventilation function is unavailable?", "kind": "action", "id": "usable-passenger-accommodation-q03" } ] } ] } ] }, { "id": "rubber-tyred-running-and-power", "name": "Rubber-tyred running and power", "description": "Capture the mechanical and electrical requirements behind MP 05 movement.", "rationale": "Rubber-tyred operation introduces running-surface and tyre-condition dependencies that a generic rail-vehicle description would miss.", "layers": [ { "id": "running-gear-interface", "name": "Running-gear interface", "description": "Describe MP 05 support, guidance and compatibility with track and depot infrastructure.", "findings": [ { "id": "tyre-and-guidance-condition", "name": "Tyre and guidance condition", "description": "Identify the actual wheel and guidance arrangement and the approved condition limits for its components.", "questions": [ { "text": "How do the MP 05 load-bearing tyres, guidance components and any auxiliary steel wheels interact with running surfaces and points?", "kind": "definition", "id": "tyre-and-guidance-condition-q01" }, { "text": "Which tyre pressure, wear, temperature or damage limits require restriction or withdrawal under MP 05 maintenance instructions?", "kind": "measurement", "id": "tyre-and-guidance-condition-q02" } ] } ] }, { "id": "traction-and-braking", "name": "Traction and braking", "description": "Connect electrical supply, propulsion and stopping performance to documented operating limits.", "findings": [ { "id": "power-and-stopping-envelope", "name": "Power and stopping envelope", "description": "Keep supply requirements, design performance and authorised service limits distinct; resolve braking architecture from MP 05 documentation.", "questions": [ { "text": "What supply voltage range, collection arrangement and traction configuration apply to this MP 05 baseline?", "kind": "measurement", "id": "power-and-stopping-envelope-q01" }, { "text": "How are service, emergency and parking braking provided, and how does braking change when electrical braking is unavailable?", "kind": "definition", "id": "power-and-stopping-envelope-q02" }, { "text": "Which load, gradient, adhesion and equipment conditions determine the permitted speed and stopping envelope?", "kind": "measurement", "id": "power-and-stopping-envelope-q03" } ] } ] } ] }, { "id": "driverless-operation-and-line-integration", "name": "Driverless operation and line integration", "description": "Model the prerequisites for MP 05 automatic operation and its interfaces with line control and platform protection.", "rationale": "A driverless train remains dependent on compatible infrastructure, validated onboard equipment and explicit degraded-operation rules.", "layers": [ { "id": "automation-compatibility", "name": "Automation compatibility", "description": "Identify the onboard and wayside configurations needed for a particular deployment.", "findings": [ { "id": "validated-line-pairing", "name": "Validated line pairing", "description": "Represent line compatibility as a dated, evidenced relationship rather than an inherent consequence of the MP 05 designation.", "questions": [ { "text": "Which onboard control and communications versions are validated against the intended line's automation system?", "kind": "provenance", "id": "validated-line-pairing-q01" }, { "text": "What modifications and acceptance tests are required before this MP 05 configuration can move to another line?", "kind": "action", "id": "validated-line-pairing-q02" } ] } ] }, { "id": "movement-and-door-interlocks", "name": "Movement and door interlocks", "description": "Connect movement authority, stopping position, door status and abnormal operating modes.", "findings": [ { "id": "permitted-operating-state", "name": "Permitted operating state", "description": "Record the evidence and authority required for each operating mode without inventing an MP 05 control sequence.", "questions": [ { "text": "Which verified train-door, platform-door, stopping-position and movement-authority conditions permit departure?", "kind": "definition", "id": "permitted-operating-state-q01" }, { "text": "What MP 05 procedures govern communications loss, failed door confirmation or inability to complete an automatic stop?", "kind": "action", "id": "permitted-operating-state-q02" }, { "text": "Who may authorise and perform degraded movement, rescue or depot operation, using which controls and restrictions?", "kind": "action", "id": "permitted-operating-state-q03" } ] } ] } ] }, { "id": "maintenance-and-service-acceptance", "name": "Maintenance and service acceptance", "description": "Connect MP 05 equipment condition and modifications to applicable maintenance and acceptance evidence.", "rationale": "Type identification cannot establish that an individual MP 05 trainset is fit for passenger service.", "layers": [ { "id": "maintenance-dependencies", "name": "Maintenance dependencies", "description": "Identify MP 05 inspection requirements, consumables and configuration-specific replacement constraints.", "findings": [ { "id": "condition-to-maintenance-decision", "name": "Condition-to-maintenance decision", "description": "Map observations to documented MP 05 limits and interventions; distinguish plausible hazards from evidenced recurring failures.", "questions": [ { "text": "Which MP 05 maintenance instructions specify inspection intervals and replacement limits for tyres, brakes, door equipment and current collectors?", "kind": "provenance", "id": "condition-to-maintenance-decision-q01" }, { "text": "Which recorded MP 05 failure modes require withdrawal, restricted operation or scheduled repair?", "kind": "action", "id": "condition-to-maintenance-decision-q02" }, { "text": "Which replacement parts, consumables and software versions are approved for the installed configuration?", "kind": "boundary", "id": "condition-to-maintenance-decision-q03" } ] } ] }, { "id": "acceptance-evidence", "name": "Acceptance evidence", "description": "Trace applicable requirements and evidence supporting release after maintenance or modification.", "findings": [ { "id": "documented-release-basis", "name": "Documented release basis", "description": "Require the actual MP 05 approval basis, including requirement editions and configuration applicability, before inferring compliance.", "questions": [ { "text": "Which standards, issuing bodies, operator requirements and approval decisions govern this MP 05 configuration and intended deployment?", "kind": "provenance", "id": "documented-release-basis-q01" }, { "text": "Which inspections, functional tests and authorised sign-offs are required after work on braking, doors, running gear or automation?", "kind": "action", "id": "documented-release-basis-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The name is interpreted as the Paris Métro rolling-stock class because no sense is recorded.", "Current fleet allocation, dimensions, speed ratings and applicable certification requirements should be checked against RATP or manufacturer records.", "The listed failure modes are general engineering concerns for this train type, not claims of documented MP 05 defects." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "RATP rolling-stock designation", "value_or_pattern": "MP 05", "note": "Identifies a rolling-stock class, not an individual trainset; MP denotes matériel sur pneumatiques, or rubber-tyred rolling stock." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Driverless passenger service on Paris Métro Line 1.", "Passenger service on Paris Métro Line 14 before its conversion to MP 14 rolling stock." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Cars per trainset", "typical_range": "6", "unit": "cars" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Tyre damage or deterioration requiring inspection and replacement.", "Door faults that can prevent departure or create passenger entrapment hazards.", "Traction or electrical supply faults causing loss of propulsion.", "Automatic train-control or communication faults requiring protective stops or restricted operation." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Designed for the Paris Métro's rubber-tyred infrastructure; compatibility cannot be assumed with other rubber-tyred metro systems." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "MP 89", "difference": "An earlier Paris Métro rubber-tyred rolling-stock class, produced in both driver-operated and automatic versions; MP 05 was built for automatic operation." }, { "name": "MP 14", "difference": "A later rolling-stock class with multiple train lengths and operating configurations, including the longer trains introduced on Line 14." }, { "name": "Rubber-tyred metro train", "difference": "The broader vehicle category; MP 05 is one specific rolling-stock class within it." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of MP 05 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative identification guide distinguishes MP 05 from MP 89 CA and six-car MP 14 when labels or asset records are unavailable?", "What are the approved MP 05 electrical supply limits, traction and braking architecture, exact engineering dimensions and passenger-capacity conventions?", "Which MP 05 configurations and line assignments are current, and what modifications and validation records support reassignment?", "What manufacturer or operator documents establish tyre limits, maintenance intervals, recurring failure modes and degraded-operation procedures?", "Which standards, editions, issuing bodies and acceptance decisions actually apply to MP 05, including modifications made after initial delivery?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 31 } }