1/ 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.
@sduxvault
- 0 Followers
- 0 Following
- 7 Posts
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
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.
Behaviors transform state. Controllers enforce policy. In SDuX Vault, they can never cross — a controller can't touch the payload, a behavior can't block a request. Separation by architecture, not convention.
go.sdux-vault.com/x-005-mastodon
3/ Reentrancy is structurally impossible. Dispatching during reducers can't happen. Promise interleaving is eliminated. Observer-triggered loops are prevented by construction.
Same guarantees for sync values, promises, observables, and streams.
Docs → go.sdux-vault.com/x002-mastodon
2/ Every state update runs in two strict phases:
Pipeline computation — all interceptors, resolvers, filters, and reducers execute without mutating state. No side effects. No observer notifications.
State commitment — deferred to a microtask boundary. Observers see only finalized snapshots.