CTR-PLANNING · version 2

Supply and Demand Planning — Supply plan lines

Feeds the supply chain cockpit and the cross-flow between planning and procurement.

RatifiedIn contract

What the contract says

These are the terms the connector is generated against. more

Entity

Supply plan line · bidirectional

Primary key

scenarioId + partNumber + bucket

Declared volume

168,000 records a day

Freshness commitment

4 h

Owner

R. Nakamura · Supply Chain Systems

Vendor

Kinaxis RapidResponse · high criticality · modeled

Cardinality

One scenario to many lines. A line is unique on part and time bucket within a scenario.

Write-back rule

Scenario note and exception acknowledgement are in scope. Plan commit is excluded and requires a planner.

Review state

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

Security reviewApproved

D. Contreras · Jul 2, 2026

Privacy reviewApproved

Maitre Olivier Lascaux · Aug 3, 2026

Validation and drift

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

Last validatedAug 6, 2026 · 12 d ago

30,000 records read in the sample.

Validated against a 30,000-line scenario extract.

The field list

5 fields · 3 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
Scenario id	scenario.id	planLine.scenarioRef	string(24)	keyinternal	In contract	Must resolve to a published scenario. Working scenarios are not admitted.
Part number	part.id	planLine.partRef	string(30)	keyinternal	In contract	Must resolve against the part master.
Time bucket	bucket	planLine.bucket	string(10)	keyinternal	In contract	Weekly buckets in ISO week form. more
Planned quantity	plannedQty	planLine.quantity	decimal(13,3)	internal	In contract	Non-negative.
Constraint flag	constrained	planLine.constrained	boolean	internal	In contract	Drives the constraint view on the supply cockpit.

What has passed the staging boundary against this contract

1 batch · 3,980 arrived · 3,804 admitted · 176 quarantined · 0 rejected

Staging boundary

Batch	Arrived	In	Admitted	Quarantined	Rejected	Result	Gate
STG-0030	Aug 18, 05:00	3,980	3,804	176	0	Partly admitted	3,804 admitted · 176 quarantined · 0 rejected outright.

Rejects raised against these batches

1 reason covering 176 records. Each one names a field, what was observed and what the contract expected.

Working scenario submitted where only published scenarios are admitted176 records · 4 h oldOwner assigned

Observed: 3 working scenarios

Expected: A published scenario

STG-0030 · field scenarioId · queue quarantine · R. Nakamura

Replay windows

1 window recorded against this contract.

Replay register

RPL-012Completed

Source correction · Aug 14, 2026 to Aug 15, 2026

A published scenario was superseded within the day and the earlier version had already been read.

6,120 replayed · 5,901 held at the idempotence key · 0 duplicates created

Write-back routes into this system

1 route designed against Supply and Demand Planning.

Write-back register

commit-recommendation · Supply plan lineDesigned, never live

WB-PLANNING-01 · agent · authority SC2-AUTH-A1 · policy SC2-POL-200

2 attempted · 0 written to a production system

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

The last validation read 30,000 records 12 days ago, which is 18% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.