Prototype: Services as composable state machines - #190
Draft
kyleve wants to merge 1 commit into
Draft
Conversation
Add an exploratory ServicesStateMachine layer under WhereCore/Prototype that models five TLA-aligned protocol slices (tracking, post-write, ingestor quiesce, launch, reset) as pure reducers over a composite ServicesSnapshot. Includes scenario replay tests and a README — not wired into production WhereServices. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Look-only prototype — not wired into production.
What this is
An exploratory sketch of redefining WhereServices coordination as composable state machines:
Sub-machines (TLA-aligned)
TrackingMachineTrackingReconciliationPostWriteMachinePostWriteReconcileIngestorMachineIngestorQuiesceLaunchMachineLaunchLifecycleResetMachineWhereServices.reset()orderingPlain actors (
ReportReader, backup export, recent activity, …) stay out of scope.How to read it
Where/WhereCore/Sources/Prototype/ServicesStateMachine/ServicesSnapshot.swiftServicesMachine.reduce— one event in, snapshot + effects outMachines/*.swift— maps 1:1 to an existing TLA READMEServicesStateMachineTests— replays Coalesced.cfg / Current.cfg scenariosDocs:
Where/WhereCore/Prototype/ServicesStateMachine/README.mdStacked on
If this were real
A production runner would replace ad-hoc
Taskloops inWhereSession/DayJournalincrementally — one protocol at a time — not a big-bang rewrite.