Skip to content

docs: consolidate roadmap and drop the bellows seam #137

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 4, 2026
Merged

docs: consolidate roadmap and drop the bellows seam #137

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
20 changes: 9 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,11 @@ Streams adapters, CloudEvents and CDC codecs, reliability middleware, and
state-machine bridge, are now available and documented; the `broker` module is
planned.

## Roadmap: event-driven seams
## Roadmap

Two kinds of seam frame the work ahead, and both build on the engine without
reaching into the kernel: the IO edges where effects leave and events arrive, and
the serializable IR as a first-class artifact anything can read or write.

The kernel emits effects as pure data; a small family of bring-your-own-adapter
IO seams moves events to and from the outside world, each defaulting to a no-op
Expand All @@ -105,17 +109,8 @@ and forcing nothing third-party on the consumer:
`source/cdc` codec decodes Debezium/OpenCDC change-event topics into typed
change events; a native database write-ahead-log connector (logical replication
slot, binlog) remains future work.
- [ ] **`bellows`** _(exploring)_: resilience seam. Circuit-breaking and
backpressure around the IO edges.

Durable state and event persistence is tracked separately with the `durable`
runtime, not here.

## Roadmap: authoring & visualization

The serializable IR is a first-class artifact, not just an internal format: anything
that reads or writes it can build on the engine without reaching into the kernel. A
small set of tools works the IR directly.
A small set of tools works the IR directly:

- [ ] **Visual editor** _(planned)_: a browser workbench over the IR. Author, simulate,
and inspect machines, with reachability and version-diff overlays from the existing
Expand All @@ -124,6 +119,9 @@ small set of tools works the IR directly.
nondeterminism, render diagrams, and classify version diffs straight from a machine's
IR.

Durable state and event persistence is tracked separately with the `durable`
runtime, not here.

## Design & docs

Design rationale, concepts, and guides live on the
Expand Down