SyncQuestProgressReq compares GameplayStateStore facts against the fold and appends QuestReconciled
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Semantic radar needs more MAP space.
Reconcile
• If GameplayStateStore facts increased but a GameplayMsg was lost, the Client or an operational trigger sends SyncQuestProgressReq.
• The Spot reads the authoritative facts, compares them against the current fold, and appends the needed QuestReconciled event.
Failure boundary
• If the Ready owner process terminates, the current Spot operation ends as Unavailable — the Framework doesn't automatically resubmit the failed operation by selecting a new QuestMission node.
• A new Instance intent, after an explicit Close completes authority release, can replay the event stream in a new generation. These two cases are not used in the same flow as crash failover.