Register an aggregate. The shard is constructed via DI (ctor args resolved from the container) and Init'd at startup; its Handler and AggregateRefs are registered so endpoints/sagas can resolve them.

DI variant of the filtered single-event handler overload.

DI variant of the single-event handler overload.

Register the read-model projection, building the handler (and resuming offset) from DI. Use this overload when the projection needs services — e.g. an ILoggerFactory — so it resolves them the same way the actor system does.

Register the read-model projection with a filtered single-event handler: the handler updates the read model and returns Publish/Suppress per event to control whether it wakes subscribers. The middle ground between the void overload (publish all) and the list-returning one (full control) — e.g. suppress an intermediate event so read-your-writes wakes only on the final.

Register the read-model projection with a single-event handler: the handler just updates the read model (returns void); each aggregate event is then published to subscribers as-is. Use the list-returning overload when notifications must be filtered — e.g. suppressing intermediate events so read-your-writes only wakes on the final one.

Register the read-model projection, resuming from the given offset (default 0).

Register a saga and the event that starts it. `create` builds the saga (use sp.AggregateFactory<T>() to reference the aggregates it coordinates); `startOn` decides which originator events spawn an instance.

The underlying service collection (so you can keep chaining .Add… on it).

Enable Akka's internal logging (FCQRS ships it OFF). `level` maps to akka.loglevel; by default akka.stdout-loglevel is set to the same value. FCQRS's own logs are unaffected — they follow the host's ILoggerFactory.

Set the builder-wide default snapshot cadence: every aggregate/saga whose own SnapshotPolicy is Default uses this instead. Per-entity overrides (Every n / NoSnapshots) always win; leaving this unset keeps the config key (config:akka:persistence:snapshot-version-count) / 30 fallback.

Register stable journal names for payload types: manifests become "fcqrs:ev(doc.event)" instead of CLR AssemblyQualifiedNames, so types can be renamed/moved freely (update the mapping; old rows keep reading).

The message-flow narrative — which command reached which aggregate and what it yielded, saga state transitions, the commands sagas issue — is written at Information level to the "FCQRS.MessageFlow" category and is ON by default: these lines describe your application's messages, not FCQRS internals. Turn it off here (a process-wide switch), or filter the category in your logging configuration.

Whether message *payloads* appear in diagnostics detail — the span tags (command.type / event.type) and the message-flow log lines. ON by default. Span *names* are always low-cardinality case names regardless, so this never affects tracing rules or grouping. Turn it off for sensitive domains: tags and log lines then carry the case name only.