RevenueFlow.Catalog.Abstractions 0.1.0-alpha.7.2

This is a prerelease version of RevenueFlow.Catalog.Abstractions.
dotnet add package RevenueFlow.Catalog.Abstractions --version 0.1.0-alpha.7.2
                    
NuGet\Install-Package RevenueFlow.Catalog.Abstractions -Version 0.1.0-alpha.7.2
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="RevenueFlow.Catalog.Abstractions" Version="0.1.0-alpha.7.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="RevenueFlow.Catalog.Abstractions" Version="0.1.0-alpha.7.2" />
                    
Directory.Packages.props
<PackageReference Include="RevenueFlow.Catalog.Abstractions" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add RevenueFlow.Catalog.Abstractions --version 0.1.0-alpha.7.2
                    
#r "nuget: RevenueFlow.Catalog.Abstractions, 0.1.0-alpha.7.2"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package RevenueFlow.Catalog.Abstractions@0.1.0-alpha.7.2
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=RevenueFlow.Catalog.Abstractions&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=RevenueFlow.Catalog.Abstractions&version=0.1.0-alpha.7.2&prerelease
                    
Install as a Cake Tool

RevenueFlow.Catalog.Abstractions

ICatalogReader and ICatalogService expose replaceable durable catalog behavior. CatalogOfferRevision, OfferingRevision, ordered OfferingPackage alternatives and CatalogProviderMappingRevision reference immutable exact terms. Mapping bindings preserve provider/account/test-live mode independently for each purchase source. Provider import facts live in Core and do not grant benefits. Existing CatalogOffer and PurchaseSnapshot remain immutable captured local terms rather than payment proof.

Validated immutable catalog contracts in the RevenueFlow.Catalog namespace. All identifiers preserve ordinal, case-sensitive values and every definition belongs to a complete RevenueScope. Versions are positive immutable revisions. CatalogOffer requires matching scope and exact product revision across its product, price and fulfillment definitions.

Prices use nonnegative Int64 amounts in the currency's minor unit, with a three-uppercase-letter currency code. The code syntax is validated; currency availability and minor-unit exponent are application/provider responsibilities. A subscription price requires a positive billing period; a one-time price forbids one. Calendar billing periods describe terms, not a rule for calculating provider renewal timestamps.

Fulfillment definitions copy their allocation lists into read-only collections, reject null entries and ordinal duplicate keys within a benefit kind, and allow at most 256 allocations of each kind. Resource allocations require positive integer units. Entitlements explicitly distinguish permanent access, a positive fixed duration and the provider's subscription period. One-time offers reject subscription-period allocations. Applications and lifecycle implementations determine the actual grant start and end instants; definitions do not grant access themselves.

ProviderCatalogMapping binds a provider/account/product/optional-price reference to exact scoped local revisions. Provider names are ordinal identifiers. It contains no SDK, credentials or remote validation. PurchaseSnapshot retains the immutable offer and optional matching provider mapping at a UTC-normalized capture instant. A snapshot is neither payment evidence nor a completed order; callers must verify provider amounts, currency and payment state separately before fulfilling it. Fulfillment revisions and allocations remain frozen when new catalog revisions are registered.

The abstractions package does not implement persistence or provider adapters. The companion Catalog package implements document-store-backed publication. Neither package performs taxation, currency conversion, renewal reconciliation or checkout authorization.

Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (4)

Showing the top 4 NuGet packages that depend on RevenueFlow.Catalog.Abstractions:

Package Downloads
RevenueFlow.Commerce.Abstractions

Provider-neutral scoped commerce building blocks for .NET.

RevenueFlow.Teams.Abstractions

Provider-neutral scoped commerce building blocks for .NET.

RevenueFlow.Catalog

Catalog snapshot behavior and a development-only immutable catalog registry for RevenueFlow.

RevenueFlow.Growth.Abstractions

Scoped audience, paywall, placement and experiment contracts for RevenueFlow.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.1.0-alpha.7.2 136 11/10/2026