panahister 

Application contracts, results, and time abstractions.

DDD domain primitives without infrastructure dependencies.

Transport-neutral current-actor abstractions for MP Core products. BCL only.

Tenant context port and ambient tenant scope for MP Core: who the current operation is for, resolved by the host, consumed by audit, messaging and business code. BCL-only.

Persistence ports for DDD aggregates and units of work.

Messaging ports and delivery metadata independent of Wolverine and brokers.

Cache port owned by applications, independent of a cache provider.

Durable Wolverine messaging foundation with PostgreSQL persistence.

Redis implementation of the MP Core cache port over IDistributedCache: shared across instances, JSON-serialized values, key prefix and default expiration.

OpenTelemetry and structured logging foundation for MP Core consumers.

Business audit contracts: entity-change and business-action records, capture policy with allowlisting and masking, sink and query ports. BCL-only.

RFC 9457 problem-details rendering of MP Core transport-neutral failures over HTTP.

Message catalog for MP Core failures: renders message keys in the caller's culture from resource files and optional override stores, with a fallback chain and a metric for missing translations.

EF Core and PostgreSQL implementation of MP Core business audit: same-transaction entity-change capture through a SaveChanges interceptor, detached recording of rejected attempts, and paged querying.

Bearer-only OIDC resource-server wiring, current-actor mapping and default-deny authorization for MP Core hosts.

EF Core and PostgreSQL implementation of MP Core persistence ports.

Outbound HTTP clients for MP Core hosts: the standard resilience pipeline (retry, circuit breaker, timeouts, rate limiter), the service's own identity on a call to another service (OAuth 2.0 client... More information

Native gRPC failure mapping and interception for MP Core logical failures.

Composition helpers for MP Core hosting, time, and observability.

FluentValidation for MP Core commands: validators run as Wolverine middleware before the handler, and their failures become MP Core validation failures with field paths, rule codes and localizable message... More information