Repository navigation
Construct Chronicle reactors and reducers through Arc dependency injection #93
Description
Activity
28 remaining items
Increment A2 (shutdown participants, registry-owned coordinated shutdown; no-participant path unchanged) shipped in #127 / v0.45.0. Next: A3 Chronicle fallback registration, A4 activator, A5 store pinning and returned-command signal, A6 runtime shutdown, live kernel and docs. Also #121 (pre-existing synchronous closeWebSockets leak) can now be fixed on top.
Increment A3 (discovered reactors and reducers registered as deferred scoped fallbacks) shipped in #131 / v0.46.0. Next: A4 activator.
Increment A4 (preview opt-in scoped activation, activateArtifactsInScopes) shipped in #135 / v0.48.0. Remaining: A5 (pin Arc Chronicle services to the delivery store, pass the delivery signal to returned commands) and A6 (enable by default, caller-owned clients, raise the Chronicle peer floor to 6.17, live-kernel tests).
- added 10 commits that reference this issue
on Sep 29, 2026 All increments (A1–A6) are released; A6 shipped in #137 / v0.50.0. Scoped activation remains an opt-in option (activateArtifactsInScopes).
Chronicle.TypeScript now lets a host activate reactors and reducers (
ChronicleOptions.artifactActivator, Cratis/Chronicle.TypeScript#121) and gives reactor handlers the event store and read models of their observation. Plug Arc's DI into it fromwithChronicle, like Arc for .NET composes Chronicle with the host container:currentServices()/currentContext()work in handlers;ChronicleReadModelsetc.) to the delivery's store;options.servicesand decorated lifetimes;Requires the
@cratis/chroniclerelease that contains #121.