Skip to content

docs(st3): design for compiling data-DSL missions into programs (program engine M3) #6308

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
schickling-assistant wants to merge 3 commits into
base: main
Choose a base branch
from
+487 −16
Draft

docs(st3): design for compiling data-DSL missions into programs (program engine M3) #6308

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
48ad380
docs(st3): design for compiling data-DSL missions into programs (prog…
schickling Nov 10, 2026
ea58e93
docs(st3): resolve review of the data-DSL compilation design
schickling Nov 10, 2026
a448bb7
docs(st3): restrict in-body constructs to released nodes; revision re…
schickling Nov 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/st3/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ Use these documents for implementation details:
- [Mission graph runtime](mission-graph-runtime.md) defines the KDL language and execution model.
- [Program engine](program-engine.md) is the accepted design for missions whose body is a program: where
it runs, its journal, versioning by bundle hash, authority, child runs and visibility.
- [Data-DSL missions as programs](program-engine-data-dsl.md) is the proposed design for compiling
data-DSL missions into programs: orchestrated missions, released steps, parity tests and slices.
- [Configuration and KDL](../site/reference/configuration.md) defines day-to-day publication and revision workflows.
- [Native driver contracts](native-driver-contracts.md) retains launch, scope, helper, harness-state and context obligations after catalog-runner retirement.
- [Owned sets](owned-sets.md) defines complete membership publication, source ordering and retirement.
Expand Down
Loading
Loading