Document the application lifecycle as a finite state machine. - #266
Merged
Conversation
mrogaski
force-pushed
the
feature/233-document-fsm
branch
from
May 24, 2026 00:08
ee0e914 to
adac786
Compare
davidmreed
approved these changes
May 24, 2026
davidmreed
force-pushed
the
feature/233-document-fsm
branch
from
May 27, 2026 03:37
adac786 to
fda6558
Compare
davidmreed
enabled auto-merge (squash)
May 27, 2026 03:37
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
2 participants
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.
This change represents the application lifecycle as a finite state machine. The transitions conditioned by the application_kind are represented as a choice node and the CONFIRM state is represented as a pseudonode because of the automatic secondary transition that occurs on invite confirmation.
This will be used as a basis for the unit tests for the unit tests for logic encapsulation in #233.