CTR-TMS · version 1

Transportation Management — Shipments

Carrier data crosses a jurisdiction boundary and the security review is open on that.

DraftNever checked

What the contract says

These are the terms the connector is generated against. more

Entity

Shipment · inbound

Primary key

shipmentId

Declared volume

12,000 records a day

Freshness commitment

12 h

Owner

G. Mwangi · Logistics Systems

Vendor

Blue Yonder TMS · medium criticality · modeled

Cardinality

One shipment to many stops and many order lines. A stop belongs to exactly one shipment.

Write-back rule

None proposed.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewIn review

R. Osei · Jun 25, 2026

Privacy reviewApproved

Helena Marsh · Jul 28, 2026

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedNever

No sample has been read against this contract.

Draft. The registry reports this feed stale at 1,980 minutes against a 720-minute commitment, which is the second-worst freshness gap on the estate.

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

Staging boundary

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.

Batch arrived beyond the declared freshness commitment720 records · 34 h oldOpen, no owner

Observed: Thirty-three hours against a twelve-hour commitment

Expected: Inside the commitment

STG-0031 · field extractedAt · queue quarantine · no owner assigned

Replay windows

1 window recorded against this contract.

Replay register

RPL-016Awaiting approval

Late arriving · Jul 19, 2026 to Aug 17, 2026

The transportation feed is more than a day beyond its commitment and a month of shipment events has not been read.

0 replayed · 0 held at the idempotence key · 0 duplicates created

Write-back routes into this system

No write-back route is designed into this system.

Write-back register

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. more

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.