BD.PricingContext.Core

The Pricing Block's domain contract. POCO-only apart from the formula engine — no B3.CRUD and no B3.Messaging dependency — so a Blick, a consumer's adapter, or a notification subscriber can consume it without pulling in the store implementation. See ../_docs/ARCHITECTURE.md.

What's here

• Model/ — PriceSheet (the sheet header) and PriceSheetDetail (one product's price on one sheet), both PersistableEntity (_id + computed FriendlyID), their validation and their ToDictionary/FromDictionary mapping to the B3.CRUD row shape; IPriceAuditable (the shared audit stamps); PriceResolutionOutcome — the closed set Priced / SheetInactive / NotOnSheet / NoSheetAssigned that replaces a silent $0. Also PriceChangeSweepWatermark, the single bookkeeping row recording how far the Block Host's price-change sweep has swept (DECISIONS §7) — not a domain aggregate, and deliberately carrying no audit attribution.
• Contracts/ — the read/write entry points (IPriceSheetQueries/IPriceSheetCommands, IPriceSheetDetailQueries/IPriceSheetDetailCommands, IPriceSheetAssignmentQueries/…Commands, IPriceSheetResolutionQueries). Declared here rather than in DataAccess so the Blick can depend on the contracts and have implementations injected. There is no customer seam: the assignment is a column on PriceSheet and a customer id is passed in (DECISIONS §10).
• Formulas/ — PriceSheetFormulaEvaluator (W/H/x binding, RoundUpToNextEven/MRound), FormulaEvaluationOutcome, and MathFormulaFunctions.SimplifyMathFormulaText for display text.
• Notifications/ — the published notification shapes and IPricingNotificationPublication. The type names are the wire contract; the schema is additive-only.
• Configuration/PricingConfiguration — the host-supplied ViewRole / EditRole names, fail-closed by default.
• Exceptions/ — the domain exception vocabulary the Block Host maps to HTTP status codes, rooted at PricingException.
• ApplicationConstants — the three DataList names the Block owns.

What it deliberately excludes

No store access, no HTTP, no message transport, and no customer or product master — this package describes the price sheet and nothing about where it lives or who reads it. The B3.CRUD-backed implementations of the contracts above live in BD.PricingContext.DataAccess, which a host wires up via DI.

Publishing

Published to nuget.bdcsoft.com by ../azure-pipelines-Core.yml (trigger: master), which mints the date-based version from the pipeline's build number. Never hand-packed — the csproj <Version> is a local-build marker only (BD-BLOCK-SOP §8.3).