CTR-ITSM · version 2
IT Service Management — Service requests
Drives the service-level surface for information technology and the shared administration queues.
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
6 fields · 1 key · 1 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 |
|---|---|---|---|---|---|---|
| System id | sys_id | request.ref | string(32) | keyinternal | In contract | Thirty-two character hex. Idempotence key. |
| Number | number | request.displayRef | string(12) | internal | In contract | Human-facing reference. Not unique across instances, so never used as a key. |
| Assignment group | assignment_group | request.queue | string(60) | internal | In contract | Must resolve to a queue in the capacity plan. |
| Priority | priority | request.priority | integer | internal | In contract | One to five. Drives the service-level clock. |
| Opened at | opened_at | request.openedAt | timestamp | internal | In contract | UTC. A local-time value would silently shift every clock and the contract rejects any payload without a zone. |
| Caller | caller_id | request.callerHash | string(64) | personalconfidential | In contract | Pseudonymized at the boundary. |
What has passed the staging boundary against this contract
2 batches · 22,230 arrived · 21,440 admitted · 790 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0015 | Aug 18, 08:00 | 11,250 | 10,848 | 402 | 0 | Partly admitted | 10,848 admitted · 402 quarantined · 0 rejected outright. |
| STG-0016 | Aug 18, 07:00 | 10,980 | 10,592 | 388 | 0 | Partly admitted | 10,592 admitted · 388 quarantined · 0 rejected outright. |
Rejects raised against these batches
2 reasons covering 790 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
2 routes designed against IT Service Management.
What goes stale when this feed does
3 asserted figures depend on IT Service Management. The rule on each row is what the surface does when the feed misses its commitment.
| Figure | Where it is shown | Role | On stale | Note |
|---|---|---|---|---|
| Touchless processing rate | AI GBS towers | contributing | Show it unchanged | Service tickets are a small share and move the rate by under half a point. |
| Reconciliation breaks with no owner | Reconciliation ledger | contributing | Show it unchanged | Assignment groups are resolved from the service directory and change slowly. |
| Work units under management | Subway map, function cockpit | primary | Mark it stale | Service records are the largest single intake stream into the work tracker. |
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 20,000 records 4 days ago, which is 32% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.