Reference · SemText · Sequences & progress

`<sem-step>`

SemText element

You write the instruction as the text and set status to done, current, todo, or blocked. Its place in the page is its order in the procedure.

Shares its schema with <sem-procedure> — the option bullets below belong to that element's contract.

One step in a procedure. You write the instruction as the text and set status to done, current, todo, or blocked. Its place in the page is its order in the procedure.

No options beyond the global attribute catalog are stated for this tag.

Children

<sem-step>status: `done` | `current` | `todo` (default) | `blocked`.

Example

sem-step.html

source

              
              <sem-procedure kind="runbook" role="list">
            
                <sem-step role="listitem" status="done">provision Infisical path</sem-step>
            
                <sem-step role="listitem" status="current">port-forward MinIO</sem-step>
            
                <sem-step role="listitem">run migrations</sem-step>
            
                <sem-step role="listitem" status="blocked">cut release — waiting on CI</sem-step>
            
              </sem-procedure>

render

Live render boots with JavaScript — the authored source is alongside.

variant: every status, one runbook

One step per `status` — `done` ✓, `current` →, `blocked` ⛔, `todo` ○ (dashed rail) — plus the fourth step carrying no attribute at all: the schema default IS `todo`, and it renders exactly like the explicit spelling. A blocked step mutes its text; every step stays fully readable — the glyphs annotate, never redact. Status sugar inside step text (conventions §3) is display-only: `status` is canonical and is what extraction reads.

variant: every status, one runbook

sem-step-status-vocabulary.html

source

              
              <sem-procedure kind="runbook" role="list">
            
                <sem-step role="listitem" status="done">snapshot the secret store</sem-step>
            
                <sem-step role="listitem" status="current">drain the old replicas</sem-step>
            
                <sem-step role="listitem" status="todo">rotate the signing key</sem-step>
            
                <sem-step role="listitem">flip traffic to the new pool</sem-step>
            
                <sem-step role="listitem" status="blocked">retire the legacy endpoint — waiting on the client release</sem-step>
            
              </sem-procedure>

render

Live render boots with JavaScript — the authored source is alongside.

Source: spec/schema/sem-procedure.md