Author RAES SDL

Create a scenario that passes local semantic validation. Use RAES 11.0.2 and Python 3.14. You need write access to a local SDL file. This task changes only that file; it needs no runtime identity or backend permission.

Author and check the scenario

Start with four parts:

  1. Give the scenario a stable name.

  2. Declare resources under nodes.

  3. Set requested counts and links under infrastructure.

  4. Run raes semantic validate scenario.sdl.yaml on your file.

  5. Correct each reported error before adding more sections.

Replace scenario.sdl.yaml with your file path. Exit 0 and validate: success mean that structural and semantic checks passed. Exit 1 means refusal. Read diagnostics and recovery. For imported modules, use file parsing from Python.

The quickstart shows all four parts. Larger scenarios can add services, identities, participants, behaviors, objectives, workflows, variation, and evidence requirements. Follow validate, compile, and inspect a scenario plan to add a condition, evidence, attacker behavior, participants, and objectives one at a time. Then compile the scenario and read its plan.

Read the exact reference

The published schemas and normative specifications remain the authority for accepted fields and meaning:

The development specification defines safe-state declarations. It describes desired states, observed proof, and the backend execution boundary.

Finish

Keep the validated source. No native resources were created, so no backend cleanup is needed. Continue with compile and inspect. Read scenario concepts to understand the authored/runtime boundary.

Read current limits before assuming that a backend can realize every valid authored section.