Graph · dataset · registered
Shipping requests and routing
The synthetic Northwind shipping companion: requests, processing attempts, routing configurations, carrier assignments, message handoffs and indexed event evidence. No real carrier call or physical delivery is represented.
Where it is, what shape it has, what it means. OVDB Directory: where the data is. ModelSpec: its shape. MeaningGraph: what it means.
Provenance
Where it lives
03a158c07bb726ac2c4ad7f524bddf696ac2e6bbThe registry pins this commit; every concept below is read from it.meaning://github.com/demo-db/shippingConcepts
What Shipping requests and routing defines
The recorded processing state of an attempt. A blocked attempt is not an accepted carrier assignment; the state describes only this synthetic processing attempt.
A synthetic acceptance of an attempt by a carrier partner, protected by a deduplication key. Assignment acceptance does not establish physical dispatch or delivery.
A synthetic routing destination identified by partner_id, with an enabled flag. It represents the training fixture's partner configuration, not evidence of a real carrier call.
The clock domain in which an event timestamp was recorded; precision_ms declares its resolution.
A scenario correlation identifier used to relate shipping requests to synthetic carrier-gateway log entries.
The recorded event timestamp, interpreted with clock_domain and precision_ms. Time values from different clock domains must not be assumed directly comparable.
The same request message identifier carried through request creation, publication and receipt. Sharing it correlates observations; it does not establish completion.
Acknowledgement that a request message was published. Publication acknowledgement alone does not prove receipt, carrier acceptance, or delivery.
Observation that a request message was received by the synthetic shipping process. Receipt alone does not prove successful routing or a carrier assignment.
An immutable numbered configuration revision used when an attempt starts and by the routes published for that revision.
The scenario order identifier to which the request belongs. Orders 11038, 11045 and 11062 reuse Northwind order identifiers; 90001–90005 are synthetic controls that need not…
One numbered processing attempt for a shipping request using a pinned routing configuration. The baseline contains accepted and blocked attempts; future replay examples are stored…
An indexed observation within a shipping attempt, with a sequence, clock domain, timestamp precision and a byte-range pointer to its immutable source log artifact.
A synthetic instruction to arrange shipping for a scenario order. Main examples reuse Northwind identifiers; additional synthetic control orders need not exist in Northwind.…
A time-bounded mapping from a shipper identifier to a partner within one routing configuration. Overlapping or expired routes are retained for diagnostic examples.
The synthetic fixture generation, active configuration and business clock used to evaluate current routes. The business clock is scenario state, not the current wall clock.