state-machine

Explore a bounded state machine

Install

docsloth component add @docsloth/state-machine@1.0.0

Live package: sha256:91bd9464a06f102f68ad96545904912e91352b4972210f60025c8635e3f1b613 with 2 file digest(s); the catalog entry is generated from the built package, not a placeholder.

Props

The prop schema is normative in packages/contracts/component-props/state-machine.schema.json.

Example props generated from this schema:

{
  "title": "example-title",
  "workflow_id": "example-workflow_id",
  "initial_state": "example-initial_state",
  "states": [
    "example-states"
  ],
  "transitions": [
    {
      "from": "example-from",
      "to": "example-to",
      "event": "example-event",
      "guard_description": "example-guard_description"
    }
  ]
}

Required props: workflow_id, initial_state, states, transitions.

Example

Example document IR (the block the renderer consumes):

{
  "type": "state-machine",
  "props": {
    "title": "example-title",
    "workflow_id": "example-workflow_id",
    "initial_state": "example-initial_state",
    "states": [
      "example-states"
    ],
    "transitions": [
      {
        "from": "example-from",
        "to": "example-to",
        "event": "example-event",
        "guard_description": "example-guard_description"
      }
    ]
  }
}

Renderer HTML (entities decoded and wrapped for display):

<section class="ds-block ds-state-machine" data-component="state-machine" aria-labelledby="b-title">
<h3 class="ds-block-title" id="b-title">example-title</h3>
<dl class="ds-facts">
<div>
<dt>Workflow</dt>
<dd>
<code>example-workflow_id</code>
</dd>
</div>
<div>
<dt>Initial state</dt>
<dd>
<code>example-initial_state</code>
</dd>
</div>
<div>
<dt>States</dt>
<dd>
<code>example-states</code>
</dd>
</div>
</dl>
<table class="ds-table">
<caption>Transitions</caption>
<thead>
<tr>
<th scope="col">From</th>
<th scope="col">Event</th>
<th scope="col">To</th>
<th scope="col">Guard</th>
</tr>
</thead>
<tbody>
<tr>
<td>example-from</td>
<td>example-event</td>
<td>example-to</td>
<td>example-guard_description</td>
</tr>
</tbody>
</table>
</section>

Preview (interface-only; the markup above is the same output):

The renderer resolves this component as a native block; the preview above is its real HTML output, and Markdown parity for native blocks is covered by the renderer test suite.

Specification

Generated from packages/contracts/component-specs/state-machine.md.

Contract

Production props are normative in ../contracts/component-props/state-machine.schema.json. The corresponding component-fixtures manifest is only a minimal protocol fixture; use the production props schema when building the published package. The packaged artifact ships exactly its generated component-package.json manifest plus props.schema.json (the production props schema, copied byte-for-byte) and spec.md (this spec, copied byte-for-byte); it contains no executable payload, fallback implementation, Storybook, test suite, SSR harness or README. Rendering behavior and the acceptance cases below belong to the renderer and the repository tests, not to the package. Installation pins the package version and the digest of every shipped byte.

Intended behavior

Simulate documented local states, label simulation versus live system status.

Failure and fallback

Guard not satisfied explains blocker and no state mutation.

Required acceptance cases

No illegal transition accepted by UI or AI tool. Also test empty data, loading, denied access, browser without JS, mobile 360px, keyboard navigation, dark mode and an explicit constrained agent tool call. The server independently authorizes capability requests; a package manifest cannot grant authority.

Data and maintenance

Data bindings resolve from a specific publication/release vector and permitted fact/evidence graph. Configuration edits create versioned component patches. Update invalidation uses dependency IDs, never indiscriminate whole-page regeneration. Human-owned props survive automatic updates unless invalidated with an explicit conflict. Missing optional resources leave an honest inert/readable fallback, not a broken page or fake success.

Cost and tools

Pure/local interaction must never invoke a model by accident. Any model, remote query or executor call must reserve approved budget before dispatch. Public visitors do not inherit owner resources. The component may call only named tools in its signed manifest with valid typed inputs. A cancelled job stops polling and closes resources. No component gets platform administration, raw credentials or an unlimited execution loop.

Package manifest

Protocol fixture: packages/contracts/component-fixtures/state-machine.json.

Sources