Flight Route DSL — Examples

# Flight Route DSL — Examples

Worked `dwsd-flightroute` examples, from the smallest complete route to a bound
route with a `bound-to:` layer. Each is a corpus fixture (`examples-src/route/`),
inlined **byte-faithful** so every fence parses **0-diagnostic**. See the
[reference index](./index.md) for the per-construct field documentation, and the
topic pages ([Path & bands](./path-and-bands.md), [Edges](./edges.md),
[Binding](./binding.md), [Anchors](./anchors.md)) for the constructs each example
exercises.

> **Rendered versions.** These are the **source** examples. For the same routes
> with their **rendered SVG diagrams** side by side (for GitHub / handover
> reading), see the generated [Examples gallery](./route-examples.md).

### 1. Minimal

The smallest complete route: one band, one `generate` edge between two stages.

```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
```

One `Delivery` band; `epic` and `story` are the two inferred stages; the `->`
glyph is a same-band `generate` (solid). See [Path & bands](./path-and-bands.md)
for stage identity and [Edges](./edges.md) for the glyph vocabulary.

### 2. Edge vocabulary

All three canonical edges in one route: `generate` (solid), `copy` (dashed),
`feedback` (dotted).

```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
```

`epic @ Strategy -> story @ Strategy` is a same-band `generate`;
`story @ Strategy --> task @ Delivery` is a cross-band `copy`;
`task @ Delivery ..> epic @ Strategy` is a `feedback` (dotted, bidirectional).
See [Edges](./edges.md) for the full vocabulary and the `()`/⊙ delivery sink.

### 3. A referenced route (an anchor target)

A plain valid route with an external `trigger`; a companion entity anchors to one
of its stages host-side (see [Anchors](./anchors.md)).

```dwsd.flightroute
# refs — a plain valid route; a companion entity anchors to one of its stages 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
```

The `new feature idea` note sits outside the bands and generates
`epic @ Coordination`; a `copy` carries it into `Delivery`. An interaction note
can anchor to `stage:epic @ Coordination::before` — see [Anchors](./anchors.md).

### 4. A bound route

An abstract two-band route whose `Delivery` band is bound to a concrete board via
a `bound-to:` layer, pinning the `story` stage to a lane's column.

```dwsd.flightroute
# binding — a `bound-to:` layer maps a route band to a concrete board via the shared locator.
title: Bound Route
for: feature
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"
```

`bound-to:` realizes the `Delivery` band on `[[team-alpha]]`, pinning `story` to
that board's `Frontend` lane, `Doing` column. Flow ⊆ Path holds — `Delivery` is a
declared band and `story` lives in it per the path. See [Binding](./binding.md)
for the derivation and the Flow ⊆ Path invariant.

---

Back to the [reference index](./index.md).