CTR-WFM · version 1
Workforce Management — Schedule intervals
Interval-level adherence is individual performance data. The works-council packs commit to not using it that way, so the contract has to state the restriction and it currently does not.
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 · 2 key · 2 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 |
|---|---|---|---|---|---|---|
| Agent id | agentId | scheduleInterval.workerHash | string(64) | keypersonalconfidential | Never checked | Pseudonymized. |
| Interval start | startTime | scheduleInterval.startsAt | timestamp | keyinternal | Never checked | UTC, fifteen-minute boundary. |
| Activity code | activityCode | scheduleInterval.activity | string(30) | internal | Never checked | Mapped against a 14-value table. |
| Adherence percent | adherence | (excluded pending review) | decimal(5,2) | nullablepersonalrestricted | Never checked | Held out of the contract until the works-council restriction is written into it. |
What has passed the staging boundary against this contract
1 batch · 1,100 arrived · 0 admitted · 0 quarantined · 1,100 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0029 | Aug 17, 21:00 | 1,100 | 0 | 0 | 1,100 | Rejected outright | No record cleared the gate. All 1,100 were rejected outright and none was written to quarantine, because a rejected record is one the contract says must be fixed at the source. |
Rejects raised against these batches
1 reason covering 1,100 records. Each one names a field, what was observed and what the contract expected.
Replay windows
No replay has been requested 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.