CTR-CMDB · version 1
Configuration Management Database — Configuration items
The staleness on this feed is the reason four figures on the continuity surface carry a stale marker.
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 · 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 |
|---|---|---|---|---|---|---|
| System id | sys_id | configItem.ref | string(32) | keyinternal | Never checked | Thirty-two character hex. |
| Class | sys_class_name | configItem.class | string(60) | internal | Never checked | One of 34 declared classes. |
| Operational status | operational_status | configItem.state | integer | internal | Never checked | One to six. Anything else quarantines. |
| Owned by group | owned_by | configItem.ownerGroup | string(60) | nullableinternal | Never checked | Null is common in the source and admitted, but it is counted as an ownership gap rather than treated as fine. |
| Last discovered | last_discovered | configItem.discoveredAt | timestamp | nullableinternal | Never checked | Drives the staleness marker on everything derived from this feed. |
What has passed the staging boundary against this contract
1 batch · 2,410 arrived · 0 admitted · 2,410 quarantined · 0 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0017 | Aug 15, 21:00 | 2,410 | 0 | 2,410 | 0 | Held whole | The whole batch was held at the gate before any record was admitted. 2,410 records are waiting on the owner. |
Rejects raised against these batches
1 reason covering 2,410 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
No write-back route is designed into this system.
What goes stale when this feed does
1 asserted figure depends on Configuration Management Database. 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 |
|---|---|---|---|---|
| Systems of record in the registry | Connector registry | contributing | Show it unchanged | The registry is maintained in the platform. The configuration database is read only to check that nothing has been decommissioned underneath it, and it is badly stale. |
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.