STORE DOCS / DIAGRAMS

When a canonical alias becomes active

When a canonical alias becomes activeMutationStore persists an ACKED receipt and PENDING alias before adopting the echo, finishes declared invalidation effects, then retires the intent and activates the alias before the existing stream changes delegate.mutate(provisionalKey,createRef, args)push(provisionalidentity)PresentAck(canonicalKey)transaction:ACKED receipt +PENDING aliasadopt authoritativeechofinish declaredinvalidation effectstransaction:retire intent +alias ACTIVEexisting streamcollection swaps tocanonical delegateAppMutationStoreMutationServerDurable journalCall / local workAcknowledgement / return
The alias becomes ACTIVE during retirement finalization, after declared invalidation effects finish. The app keeps the same stream collection.