Skip to main content
Publish exact invoice totals, investigate exceptions, and retain decisions as source corrections arrive.

​
Business capabilities

etl, publication, lineage, exact-money, external-compute, authorization, operational-decisions

​
Dataset

Eighteen rows comprising the first complete sale, cancellation and missing-customer invoice in the first worksheet of UCI Online Retail II. One separately labeled synthetic customer correction. License: CC BY 4.0; synthetic corrections supplied with this example. Bound: 256 rows, 262144 bytes.
  • Daqing Chen, Online Retail II, UCI Machine Learning Repository, DOI 10.24432/C5CG6D. (source); SHA-256 572e36277c2390fbfde10664750731e0a86f55e33470d91919085f0408e67bfb
  • Synthetic scenario: associate invoice 489464 with SYNTHETIC-ACCOUNT; this is not a source correction from the publisher.

​
Journeys

​
Publish, review and correct invoices

Actor: Publisher and sales analyst, using separate signed identities. Complete source invoices and independently calculated expected totals; no existing release.
  1. Complete initial invoices match the independent exact-money oracle. Expected: Complete initial invoices match the independent exact-money oracle.
  2. Replay preserves release identity and rejects conflicting content. Expected: Replay preserves release identity and rejects conflicting content.
  3. An analyst records a decision against the selected release. Expected: An analyst records a decision against the selected release.
  4. Invalid external output is invisible and leaves the selected release unchanged. Expected: Invalid external output is invisible and leaves the selected release unchanged.
  5. A synthetic correction publishes atomically without erasing reviews or history. Expected: A synthetic correction publishes atomically without erasing reviews or history.
  6. Current authority refuses outsiders and analyst publication. Expected: Current authority refuses outsiders and analyst publication.

​
Recipes

​
Source and evidence

Application: examples/sales-exceptions/bijection. The example’s overview, walkthrough and adaptation guide live beside usecase.json. Catalog source digest: 86395572aa798559aca1282148643f1651c0d55ff497f3429e8a8eca7a2c0f0d. This identifies example inputs; it is not a successful execution or a runtime build claim.