PLAT-204: Scenario Catalog and Editor¶
Statement¶
The platform shall provide a scenario catalog and staff-only scenario editor for creating, validating, listing, disabling, and deleting scenario definitions used by range and experiment workflows. Scenario definitions shall be schema-validated and shall enforce visibility and access metadata before provisioning.
Rationale¶
Scenario catalog/editor code exists and is used by range, CTF, and experiment workflows, but GC only had a future scenario expressiveness constraint rather than the implemented product capability.
Traceability¶
- DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#402(Smoke test: Scenario Editor end-to-end) - DOCUMENTS → GITHUB_ISSUE
Brad-Edwards/bigrae#403(Create Scenario Editor documentation) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/cms/scenarios/pack_validation.py(Scenario pack validation: identity, containment, provenance, and schema checks) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/cms/scenarios/registry.py(Scenario registry and access filtering) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/cms/models/scenarios.py(Scenario and scenario metadata models) - TESTS → TEST
shifter/shifter_platform/tests/cms/test_pack_validation.py(Scenario pack validation tests) - IMPLEMENTS → PULL_REQUEST
733(Add CyberScript docs and additional scenario editor script validation) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/cms/scenario_editor/_common.py(Scenario editor service shared helpers) - IMPLEMENTS → CODE_FILE
shifter/shifter_platform/cms/scenario_editor/_metadata.py(Scenario editor metadata services)