CTR-CCAAS · version 2
Contact Center Platform — Contact interactions
Privacy condition: transcript text is excluded from the contract. Only structured interaction metadata is ingested.
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 · 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 |
|---|---|---|---|---|---|---|
| Conversation id | conversationId | interaction.ref | guid | keyinternal | In contract | Source-generated guid. |
| Queue | queue.name | interaction.queue | string(60) | internal | In contract | Must resolve to a queue in the capacity plan. |
| Handle time | metrics.tHandle | interaction.handleSecs | integer | internal | In contract | Seconds. Drives the service-level clock and the cost-per-contact figure. |
| Disposition | wrapUpCode | interaction.disposition | string(40) | nullableinternal | In contract | Null on abandoned interactions, which is legitimate. |
| Transcript | transcript.body | (excluded) | text | nullablepersonalrestricted | In contract | Excluded from the contract. This exclusion is the privacy condition. |
What has passed the staging boundary against this contract
1 batch · 7,420 arrived · 7,129 admitted · 291 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0028 | Aug 18, 08:00 | 7,420 | 7,129 | 291 | 0 | Partly admitted | 7,129 admitted · 291 quarantined · 0 rejected outright. |
Rejects raised against these batches
1 reason covering 291 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 Contact Center Platform.
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 40,000 records 16 days ago, which is 10% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.