CTR-TMS · version 1
Transportation Management — Shipments
Carrier data crosses a jurisdiction boundary and the security review is open on that.
What the contract says
These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.
Review state
Neither review is performed by the team that wrote the contract.
Validation and drift
Drift is only detectable on a contract that has been read against a sample.
The field list
4 fields · 1 key · 0 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.
| Field | Source | Target | Type | Flags | Drift | Validation |
|---|---|---|---|---|---|---|
| Shipment id | shipment_id | shipment.ref | string(20) | keyinternal | Never checked | Unique. |
| Carrier | carrier_scac | shipment.carrier | string(4) | internal | Never checked | Standard carrier code. Must resolve to a contracted carrier. |
| Origin country | origin.country | shipment.originJurisdiction | string(2) | internal | Never checked | Drives the transfer route check. |
| Delivery date | planned_delivery | shipment.plannedFor | date | internal | Never checked | Required on every open shipment. |
What has passed the staging boundary against this contract
1 batch · 720 arrived · 0 admitted · 720 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0031 | Aug 16, 23:00 | 720 | 0 | 720 | 0 | Held whole | The whole batch was held at the gate before any record was admitted. 720 records are waiting on the owner. |
Rejects raised against these batches
1 reason covering 720 records. Each one names a field, what was observed and what the contract expected.
Replay windows
1 window recorded against this contract.
Write-back routes into this system
No write-back route is designed into this system.
A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.
This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.