Graph · dataset · registered
Shipping log observations
Immutable synthetic JSONL observations with baseline, carrier-gateway simulation and future recovery-example classifications kept separate. Semantic identifiers link to the Shipping companion without creating cross-database foreign keys.
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
9322a1b42726166e136dc9d5181393a1ec70cc76The registry pins this commit; every concept below is read from it.meaning://github.com/demo-db/shipping-logsshipping_logsmodel/shipping-logs.modelspec.hcl at commit 9322a1b · View in CodeGrapher Concepts
What Shipping log observations defines
An original baseline simulated booking request or response for healthy order 11038 only. It is not a real carrier API call or evidence that blocked orders 11045 or 11062 were…
An original baseline shipping-process observation, including the Northwind example orders and synthetic control scenarios. These records do not import future recovery examples.
The clock whose timestamps the record uses. Clock domains must be considered before comparing event times across streams.
The scenario identifier relating a gateway exchange to its Shipping request. It correlates records without proving successful processing.
The kind of synthetic observation, such as request-created, replay-started or booking-confirmed. A kind found in a recovery-example collection remains illustrative.
The recorded event order within a stream and attempt. Sequence numbers are not a global order across collections or a substitute for clock-domain-aware time comparisons.
The timestamp recorded for the synthetic observation, qualified by clock_domain and precision_ms. A future example timestamp does not establish that an action occurred.
A simulated carrier-gateway entry illustrating a possible future order 11045 replay. It is not an original baseline observation, a real carrier call or proof of physical shipping.
A separately stored shipping-process entry illustrating a possible future replay for order 11045. It is not baseline observation or executed recovery evidence.
A simulated carrier-gateway entry illustrating a possible future order 11062 replay. It does not establish an executed replay, real booking or physical shipping.
A separately stored shipping-process entry illustrating a possible future replay for order 11062, whose replay is pending. It does not establish that the replay happened.
The scenario order identifier associated with the log entry. Orders 11038, 11045 and 11062 reuse Northwind order identifiers; 90001–90005 are synthetic controls that need not…
An attempt identifier referring to the Shipping attempt concept. Baseline IDs can correspond to recorded attempts; future example IDs need not exist in the Shipping baseline. This…
The shipping request identifier carried by the simulated carrier-gateway message. This declares the identifier meaning without asserting a SQL join or a completed carrier…
An optional reference returned by the synthetic booking simulation. Example references are not evidence of a real booking, carrier call or shipment.
An optional status on a simulated carrier response. A booked status in a recovery example is illustrative and does not establish an executed replay or a real shipment.