Skip to content

Create validated scenario templates for current SDL authoring #378

Closed

Description

@Brad-Edwards

Related to #227 and PR #376.

This tracks reusable scenario template artifacts that are useful only after the template boundary is explicit enough to validate.

Current constraint:

  • The repository has example scenarios, but no validated template contract that distinguishes safe placeholders from executable SDL.
  • Adding placeholder templates now would invite users to copy incomplete SDL as if it were supported.

Useful artifact:

  • A small set of scenario templates that parse or are clearly marked as non-executable.
  • Validation commands next to each template.
  • Clear notes about what each template does and does not claim.

Acceptance notes:

  • Do not add templates that look executable unless normal SDL validation accepts them.
  • Do not describe templates as normative.
  • Keep language factual and short.

Activity

  1. added this to the Docs & Governance milestone on Jul 3, 2026
  2. Brad-Edwards commented on Oct 27, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Delivered by #1458 (squash merge ecd7b20). The change came from the stacked PR #1445.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions