Skip to content

docs: restore CHANGELOG 0.2.0 section and fix release hygiene #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joshua-temple merged 1 commit into from
Jun 5, 2026
Merged

docs: restore CHANGELOG 0.2.0 section and fix release hygiene #142

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/src/content/docs/authoring/services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
title: Services
description: Invoke async work on a state and route its completion back as an onDone event.
description: Invoke async work on a state and route its completion back through the WithInvokeOnDone option.
sidebar:
order: 6
---

<!-- IMAGE-SLOT: invoked-service (sky-squid dispatching a glowing courier-orb to an external system, a return thread carrying the onDone signal home) 16:9 -->
<!-- IMAGE-SLOT: invoked-service (sky-squid dispatching a glowing courier-orb to an external system, a return thread carrying the completion signal home) 16:9 -->
![Services](../../../assets/invoked-service.png)

A **service** is asynchronous work scoped to a state: authorize a payment, run a cancellation saga, call an external API. Unlike an effect (fire-and-forget data the host dispatches), a service has a lifecycle: it starts when the state is entered, and its completion feeds back into the machine as an event.
Expand Down
Loading