{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-vrt-012","code":"wm-vrt-012-simulation-scenario","url":"https://ver.cy/models/wm-vrt-012-simulation-scenario/","name":"Simulation Scenario","alternateNames":[],"kind":"world-model","status":"todo","version":"unversioned","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"standalone-mm","plane":"","domain":["INF.VRT.SCN"],"industry":["Cross-industry"],"navPath":"NAV.INF.VRT.SCN","tags":["simulation","scenario","inf.vrt.scn"],"facets":{}},"whatItIs":"A simulation scenario is the specification of one situation to be simulated: its inputs, actors, environment, initial conditions, events, objectives and expected outcomes. It is reusable across runs and simulators; the simulation model that computes behaviour and the results of a particular run are separate records.","purpose":"Inputs, actors, environment, objectives and expected outcomes","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["It specifies a situation to simulate, while the simulation model computes behaviour and a run produces results.","It can be reused across simulators and runs when written in a neutral format.","Expected outcomes are part of the scenario, which makes it usable as a test case.","A game world is meant for open-ended participation; a scenario has defined objectives and bounds."],"structure":{"bundles":[{"id":"VRT012-B1","name":"Scenario definition","description":"What situation is set up and why.","layers":[{"id":"VRT012-B1-L1","name":"Purpose and setting","description":"The objective, environment and initial conditions.","findings":[{"id":"VRT012-F01","name":"Objective","description":"The question the scenario is meant to answer or the skill it is meant to train.","questions":[{"text":"What question or training goal does the scenario serve?","id":"VRT012-Q01"},{"text":"Which outcomes count as success or failure?","id":"VRT012-Q02"}]},{"id":"VRT012-F02","name":"Environment and initial state","description":"The environment, map, weather and starting state of all elements.","questions":[{"text":"Which environment and initial conditions does the scenario set?","id":"VRT012-Q03"},{"text":"Which parameters are fixed and which are varied?","id":"VRT012-Q04"}]}]}]},{"id":"VRT012-B2","name":"Actors and events","description":"Who takes part and what happens.","layers":[{"id":"VRT012-B2-L1","name":"Actors and storyline","description":"Actors with their behaviour and the scripted or random events.","findings":[{"id":"VRT012-F03","name":"Actors","description":"The actors, agents or vehicles with their roles and behaviour models.","questions":[{"text":"Which actors take part, and how is each one's behaviour defined?","id":"VRT012-Q05"},{"text":"Are any actors controlled by humans in the loop?","id":"VRT012-Q06"}]},{"id":"VRT012-F04","name":"Events and triggers","description":"Scripted events and the conditions that trigger them.","questions":[{"text":"Which events occur, and what triggers each?","id":"VRT012-Q07"},{"text":"Which events are stochastic, and with which seeds or distributions?","id":"VRT012-Q08"}]}]}]},{"id":"VRT012-B3","name":"Validity and reuse","description":"How far the scenario can be trusted and reused.","layers":[{"id":"VRT012-B3-L1","name":"Provenance and coverage","description":"Sources, version and the range of conditions covered.","findings":[{"id":"VRT012-F05","name":"Scenario provenance","description":"Where the scenario comes from, such as real data, expert design or generation.","questions":[{"text":"Was the scenario derived from real recorded events, designed by experts or generated?","id":"VRT012-Q09"},{"text":"Which version is it, and who approved it?","id":"VRT012-Q10"}]},{"id":"VRT012-F06","name":"Coverage","description":"Which part of the operating domain the scenario represents.","questions":[{"text":"Which conditions of the operating domain does the scenario cover?","id":"VRT012-Q11"},{"text":"Which important conditions are not covered by any scenario in the set?","id":"VRT012-Q12"}]}]}]}]},"agentConduct":{"may":["Author scenarios with stated objectives, actors, events and expected outcomes.","Run scenarios in a simulator and compare results with expected outcomes.","Vary parameters systematically and record seeds for reproducibility.","Report gaps in scenario coverage."],"mustNot":["Present simulation results as real-world evidence without stating validity limits.","Change a scenario after a run without versioning it.","Hide failed scenarios from a test or certification report.","Use personal data from recorded events in scenarios without a lawful basis.","Design scenarios that rehearse attacks on real people or infrastructure."],"requiresHuman":["Accepting a scenario set as sufficient for safety or certification claims.","Approving scenarios used to train people for safety-critical tasks.","Releasing scenarios derived from real incidents."]},"ethics":{"considerations":["Safety claims for autonomous systems rest on how well scenarios cover real conditions.","Scenarios derived from real incidents can expose the people involved.","Biased scenario sets can hide failures that affect specific groups or places."],"affectedParties":["People affected by systems validated in simulation","Trainees and operators","Regulators and certifiers","People whose recorded data underlies scenarios"]},"owners":{"steward":"The engineering, testing or training team that authors and maintains the scenario set.","roles":[],"masterSystems":["Scenario libraries and databases","Simulation and test management tools"]},"relations":[{"target":"WM-VRT-003","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["A scenario is identified by its library identifier and version.","Scenario files are referenced by path or content hash in the scenario library.","Runs reference the scenario identifier, version and random seed."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A scenario names an environment, actors, events, initial conditions and expected outcomes.","Often confused with the simulation model, a simulation run or its results."]},"capabilities":{"applicability":"required","items":["Scenarios can be parameterised, versioned and run repeatedly.","Scenario sets can be analysed for coverage of an operating domain.","Results can be compared with expected outcomes automatically."]},"hazards":{"applicability":"required","items":["False confidence from scenarios that miss real-world conditions.","Irreproducible results when versions or seeds are not recorded.","Privacy breaches from scenarios built on recorded personal data."]},"interfaces":{"applicability":"required","items":["ASAM OpenSCENARIO for driving scenarios.","ASAM OpenDRIVE for road networks used in scenarios.","IEEE 1516 High Level Architecture for distributed simulation."]},"context":{"applicability":"required","items":["Used in testing autonomous systems, training, emergency planning and research.","Scenario-based testing supports safety cases in automotive, aviation and robotics."]}},"sources":[{"title":"ASAM OpenSCENARIO, Association for Standardization of Automation and Measuring Systems"},{"title":"IEEE 1516 Standard for Modeling and Simulation High Level Architecture, IEEE"}],"openQuestions":["Planned model: boundary questions, research and every section remain to be written."],"resources":{"spec":"https://ver.cy/models/wm-vrt-012-simulation-scenario/spec.yaml","agents":"https://ver.cy/models/wm-vrt-012-simulation-scenario/AGENTS.md"},"provenance":{"origin":"planned (registry candidate)","builtFrom":["models/runtime-index.json","ver-cy/world-models/card-supplements/wm-vrt-012-simulation-scenario.json"],"providers":[],"researchStatus":"todo","generatedAt":"","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_":"Planned entry, hidden from the catalogue until researched.","interaction.properties":"The subject is an institutional or informational record, not a physical object with measurable properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-06, unreviewed). Written from the card's existing content and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}