# `StatifierBlocks.Core.Sequence`
[🔗](https://github.com/riddler/statifier_blocks/blob/v0.44.1/lib/statifier_blocks/core/sequence.ex#L1)

`core.sequence`: an ordered run of steps, and the conventional document
root (ADR-0002 decision 10).

One `body` slot, no config at all. Adjacency inside `body` *is*
sequencing (ADR-0001 decision 5), so a sequence adds no meaning of its
own beyond "these, in this order" - which is exactly why it is the one
core type that is transparent to type flow: it declares
`produces: {:passthrough, "body"}`, so whatever the last step in its body
produces is what the sequence produces, computed by ADR-0003 decision 4
rather than by anything here.

A sequence has no `interrupts` slot. A container that can be interrupted
is `StatifierBlocks.Core.Group` or
`StatifierBlocks.Core.ResumableGroup`; keeping the plain ordered case free
of that machinery is what makes the two readable side by side in a
palette.

# `emit`

A compound state running `body` in order and finishing at its own
`<final>` - `StatifierBlocks.Core.Emit`'s plain ordered shape, with
nothing added. A sequence with an empty `body` enters its `<final>`
directly and is done, which is the honest compilation of "these, in this
order" over no steps.

# `sentence`

This block as one line of prose (ADR-0002's 2026-09-07 amendment).

A sequence has no config, so the line is the same for every block of
this type: what it does with its steps, in the words
`StatifierBlocks.Core.Parallel` uses for its lanes, so the two read as
the pair they are in a list.

    iex> StatifierBlocks.Core.Sequence.sentence(%{})
    "Run its steps in order"

# `validate_config`

Always `:ok`. A sequence declares no config fields, so there is nothing
for an author to get wrong; a config carrying keys this type does not
know is left alone rather than rejected, the same way ADR-0001 decision 9
leaves an unresolvable type alone at decode time.

---

*Consult [api-reference.md](api-reference.md) for complete listing*