Stratara.Contracts
4.0.2
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Contracts --version 4.0.2
NuGet\Install-Package Stratara.Contracts -Version 4.0.2
<PackageReference Include="Stratara.Contracts" Version="4.0.2" />
<PackageVersion Include="Stratara.Contracts" Version="4.0.2" />
<PackageReference Include="Stratara.Contracts" />
paket add Stratara.Contracts --version 4.0.2
#r "nuget: Stratara.Contracts, 4.0.2"
#:package Stratara.Contracts@4.0.2
#addin nuget:?package=Stratara.Contracts&version=4.0.2
#tool nuget:?package=Stratara.Contracts&version=4.0.2
Stratara.Contracts
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Wire-level POCO contracts shared by every Stratara package. Pure data records — no runtime, no DI, no infrastructure deps. Safe to reference from any layer.
Contents
Messages/EventMessage,EventBundle,CommandEnvelope— the cross-process envelope shapes that messaging adapters (Stratara.Outbox.RabbitMQetc.) serialise on and off the bus.Requests/PagedRequest— shared pagination + sort record used by query handlers across the family.Session/SessionContext— public data shape for actor/subject identity, correlation, causation, and connection routing. TheISessionContextProviderservice abstraction lives inStratara.Abstractions; the ASP.NET Core middleware that populates it lives inStratara.Sessions.
Quick reference
// Build a CommandEnvelope outside the framework (rare, but supported)
var envelope = new CommandEnvelope(
Id: Guid.CreateVersion7(),
CommandJson: commandJson,
CommandTypeName: typeof(MyCommand).AssemblyQualifiedName!,
SessionContextJson: sessionContextJson);
Dependencies
None. Contracts is the lowest tier in the Stratara dependency graph.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- No dependencies.
NuGet packages (9)
Showing the top 5 NuGet packages that depend on Stratara.Contracts:
| Package | Downloads |
|---|---|
|
Stratara.Abstractions
Contract interfaces and POCO records for the Stratara CQRS / Event Sourcing framework — Mediator, EventSourcing, Persistence, Outbox, Messaging, Session, Security, Authorization. Library-safe, no EF Core or message-bus runtime. |
|
|
Stratara.Sessions
ASP.NET Core middleware and provider for Stratara's Actor/Subject session model. Reads tenant and user from JWT claims (or X-Tenant-Id / X-Client-Id headers) and populates the ambient ISessionContextProvider for every request. |
|
|
Stratara.Shared
Umbrella package for the Stratara framework — source-generated logger extensions for command flows, domain-event helpers, merge primitives, and the Tier-A/B abstractions surface re-exported as one transitive bundle. |
|
|
Stratara.Projections
Projection runtime for the Stratara event-sourced stack — projection-handler discovery, change-set creation, update application, and projection manager. Sits between read-model repositories and the event-bundle dispatcher. |
|
|
Stratara.Outbox.RabbitMQ
Outbox-pattern command and event dispatch for the Stratara event-sourced stack — RabbitMQ IMessageBus implementation, retry worker, mediator command worker, and Redis-coordinated projection-replay state. Azure Service Bus support ships as the sibling Stratara.Outbox.AzureServiceBus package. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.2.0 | 120 | 9/18/2026 |
| 4.1.1 | 308 | 9/16/2026 |
| 4.1.0 | 248 | 9/16/2026 |
| 4.0.4 | 919 | 9/14/2026 |
| 4.0.3 | 409 | 9/3/2026 |
| 4.0.2 | 814 | 9/3/2026 |
| 4.0.1 | 413 | 9/2/2026 |
| 4.0.0 | 845 | 8/31/2026 |
| 4.0.0-preview.1 | 162 | 8/31/2026 |
| 3.4.0 | 388 | 8/28/2026 |
| 3.3.0 | 547 | 8/25/2026 |
| 3.2.3 | 376 | 8/22/2026 |
| 3.2.2 | 927 | 8/14/2026 |
| 3.2.1 | 928 | 8/2/2026 |
| 3.2.0 | 356 | 7/18/2026 |
| 3.1.7 | 622 | 7/1/2026 |
| 3.1.6 | 760 | 6/22/2026 |
| 3.1.5 | 335 | 6/22/2026 |
| 3.1.4 | 2,208 | 6/15/2026 |
| 3.1.3 | 341 | 6/10/2026 |
Two operational fixes, both found while a consumer rolled out bus-envelope signing and reasoned
about rebuilding its read models: a projection replay now survives a passing failure, and an
integrity failure says whether the signature was absent or wrong. Additive on every published
surface.
### Added
- **A projection replay retries a failing batch before it gives up.** Each batch — the read from
the event store and the application of its entries — now runs under a new named policy,
`ResilienceNames.ProjectionReplayBatch`: five attempts in all, exponential backoff from one second
with jitter between them, any exception except cancellation. A read-store timeout or a
dropped connection mid-rebuild no longer ends the replay; a failure that persists through every
attempt ends it exactly as before, with the same failure record. A retried batch is applied
again from its first entry in a fresh scope, which relies on the guarantee projections already
give under at-least-once delivery: a second application converges (see *Write handlers that
converge rather than accumulate* in the projection guide). Each failed attempt logs a new
warning, `104_011`. `AddResiliencePipelines` registers six policies rather than five. Nothing
about truncation, ordering, progress, the failure record or the lease changes.
### Changed
- **An integrity failure now says whether the signature was absent or wrong, and the existing
warning and error ids fire only for a signature that is present and does not verify.** An
unsigned envelope — what every not-yet-restarted publisher emits during a `Permissive` roll —
was logged as *"signature mismatch"* under the same id as a key mismatch or tampering, so an
operator could not tell a rolling restart from an attack without correlating host start times.
Four new event ids carry the unsigned case: `105_004` (command, permissive), `111_004` (event
bundle, permissive), `105_105` (command, strict) and `111_105` (event bundle, strict). The
existing `105_003`, `111_003`, `105_104` and `111_104` keep their numbers and their level but
now mean a present signature that did not verify; an alert keyed on one of them goes quiet
during a roll instead of firing for every unsigned message. Strict-mode rejections name the
case in their exception message. `BusEnvelopeIntegrityVerifier.Verify` gains an overload with
`out BusEnvelopeIntegrityFailure` (`None`, `Absent`, `Invalid`); the existing overload and the
`BusEnvelopeIntegrityResult` values are unchanged. An absent signature no longer reaches the
signer, which already answered `false` for it.