Flight Route DSL — Examples Gallery
Six canonical examples, each shown as its DSL source and the rendered diagram — one source of truth (the routeExamples export of @worksystems-design/dwsd-dsl), two representations.
- On a host that understands the
dwsd.flightroutefence (the DWSD.md website, the VS Code preview) the Source block renders live, so the Source/Rendered pair can be surfaced as a Text | Diagram toggle. - On GitHub and other plain-Markdown viewers the Source shows as code and the Rendered static SVG is shown beneath it.
For the field-by-field syntax reference, see index.md.
1. Minimal
The smallest complete route: one band and a single generate edge between two stages.
Source (dwsd.flightroute):
# minimal — the smallest complete route: one band, one generate edge between two stages. title: Minimal Route for: feature bands: - name: Delivery fl: 1 path: - epic @ Delivery -> story @ Delivery
2. Bands
Multiple band records, one named band per flight level (3/2/1); stages live across the named bands.
Source (dwsd.flightroute):
# bands — one named band per flight level; stages live across named bands. title: Multi-Band Route for: feature bands: - name: Strategy fl: 3 - name: Coordination fl: 2 - name: Delivery fl: 1 path: - vision @ Strategy --> epic @ Coordination - epic @ Coordination --> story @ Delivery
3. Edges
All three canonical edges in one route: generate (solid, same band), copy (dashed, between bands), feedback (dotted, backward between bands).
Source (dwsd.flightroute):
# edges — all three canonical edges in one route: generate (solid), copy (dashed), feedback (dotted). title: Edge Vocabulary for: feature bands: - name: Strategy fl: 3 - name: Delivery fl: 1 path: - epic @ Strategy -> story @ Strategy - story @ Strategy --> task @ Delivery - task @ Delivery ..> epic @ Strategy
4. Delivery
A copy into the delivery band, then a dotted delivery edge to the reserved outside-band ()/⊙ sink.
Source (dwsd.flightroute):
# delivery — a copy into the delivery band, then a dotted `..> ()` to the reserved outside-band sink. title: Delivery Route for: feature bands: - name: Build fl: 2 - name: Ship fl: 1 path: - account @ Build --> account @ Ship - account @ Ship ..> ()
5. Binding
A bound-to: layer maps a route band to a concrete board via the shared locator, with a per-stage refinement; for-domain: names the domain responsible for the route.
Source (dwsd.flightroute):
# binding — a `bound-to:` layer maps a route band to a concrete board via the shared locator; `for-domain:` names the domain responsible for the route. title: Bound Route for: feature for-domain: "[[Delivery Ops]]" bands: - name: Coordination fl: 2 - name: Delivery fl: 1 path: - epic @ Coordination --> story @ Delivery bound-to: - band: Delivery boards: - board: "[[team-alpha]]" stages: - story: "lane:Frontend/col:Doing"
6. Refs
Item types as text or wikilink: a quoted wikilink stage ([[Epic]]) is a real connection, plain text (story) a local description, and the two mix freely; a companion entity anchors to a stage host-side (the entity-frontmatter side is explained in anchors.md).
Source (dwsd.flightroute):
# refs — a stage's item type is plain text OR a quoted wikilink: `[[Epic]]` is a real connection, `story` a local description; the two mix freely, also on one line. A companion entity anchors to a stage host-side (see anchors.md). title: Referenced Route for: "[[Feature]]" bands: - name: Coordination fl: 2 - name: Delivery fl: 1 triggers: - name: new feature idea generates: - "[[Epic]] @ Coordination" path: - "[[Epic]] @ Coordination --> story @ Delivery"
Like what you see? → Start — build your own org folder in ~2 min