Problem Statement
Studio includes useful scientific circuit presets, but they are hard-coded in Swift. As SchroSIM becomes a design tool, presets should be public artifacts that can be reviewed, cited, versioned, validated in CI, and reused by docs, CLI examples, and the Gottesman software site.
Proposed Solution
Create a public preset catalog under docs/config or docs/examples/design-presets:
- JSON schema for scientific presets,
- citation and DOI/source metadata,
- recommended backend, seed, mode count, slot count,
- nodes and edges,
- mapping notes and approximation boundaries,
- script to validate every preset compiles and runs.
Update Studio to load presets from the catalog with a fallback only for development.
Acceptance Criteria
- Presets are data files, not hard-coded arrays.
- CI validates every preset for schema, compile, and at least one runtime backend.
- Studio shows citation, mapping note, and compatibility status from catalog data.
- Docs render a preset gallery from the same source files.
- Adding a new preset requires no Swift source edit.
Validation
bash scripts/swift-test.sh
bash scripts/cv-validation-suite.sh --runtime both
Evidence
core-swift/Sources/schrosim-studio/StudioStore.swift
docs/examples/
docs/config/
Problem Statement
Studio includes useful scientific circuit presets, but they are hard-coded in Swift. As SchroSIM becomes a design tool, presets should be public artifacts that can be reviewed, cited, versioned, validated in CI, and reused by docs, CLI examples, and the Gottesman software site.
Proposed Solution
Create a public preset catalog under
docs/configordocs/examples/design-presets:Update Studio to load presets from the catalog with a fallback only for development.
Acceptance Criteria
Validation
Evidence
core-swift/Sources/schrosim-studio/StudioStore.swiftdocs/examples/docs/config/