CTR-PLANNING · version 2
Supply and Demand Planning — Supply plan lines
Feeds the supply chain cockpit and the cross-flow between planning and procurement.
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
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. A monthly bucket in a weekly scenario quarantines. |
| 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
| 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.
Replay windows
1 window recorded against this contract.
Write-back routes into this system
1 route designed against Supply and Demand Planning.
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.
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.