sduxvault1/ Your state update travels through a pipeline. Here's every stop.
Most state libraries give you a reducer and say "good luck." SDuX Vault™ runs every update through a structured, multi-stage pipeline — and every stage is composable.
2/ The pipeline stages, in execution order:
→ Resolve — normalizes input (sync, promise, observable, stream)
→ Merge — combines the resolved value with current state
→ Operators — refines or suppresses the merged candidate
→ Filters — examines and gates values before reduction
→ Reducers — computes the finalized state from the processed value
→ State — commits the result as the new immutable snapshot
Each stage is isolated. Each Behavior is scoped to one stage.
3/ Core Behaviors are always present. Everything else is opt-in. No implicit behavior. No hidden middleware. You declare what runs. Composable state management — small, focused Behaviors in a FeatureCell™ pipeline, not a monolithic store.
Docs → go.sdux-vault.com/x004-mastodon