Design generation and validation

For a standard experiment, declare layers and their order in setup.yaml, run the small setup.py entry point, then inspect the generated design.yaml.

artefacts:
  design_file_name: design.yaml
design:
  name: Policy experiment
  layer_ids: [announcement, response]

Setup preserves the layer_ids order exactly. It never infers design membership.

G-Cubed rejects a design with:

duplicate or unknown keys;
anchors, aliases, merge keys or custom tags;
a missing or unsupported schema version;
blank or duplicate layer names;
unsafe data_file values;
non-integer event years;
decreasing event years; or
a missing or invalid layer CSV when the runtime loads the design.

Errors identify the file and path, such as layers[2].event_year.

Generate one or more designs from setup