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.

In reviewNever checked

What the contract says

These are the terms the connector is generated against. more

Entity

Configuration item · inbound

Primary key

sysId

Declared volume

8,000 records a day

Freshness commitment

1 d

Owner

J. Petrakis · IT Operations

Vendor

ServiceNow CMDB · high criticality · modeled

Cardinality

One item to many relationships. Relationships are directional and the contract declares both directions explicitly.

Write-back rule

None. The contract declares the configuration database authoritative and the platform subordinate to it.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewApproved with conditions

R. Osei · Aug 6, 2026

Privacy reviewApproved

Helena Marsh · Jun 16, 2026

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedNever

No sample has been read against this contract.

No sample. This is the feed the registry already reports as stale at 3,610 minutes against a 1,440-minute commitment, so a sample taken today would not describe a healthy feed anyway.

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

Staging boundary

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.

Batch arrived beyond the declared freshness commitment2,410 records · 60 h oldOwner assigned

Observed: Two and a half days against a one-day commitment

Expected: Inside the commitment

STG-0017 · field extractedAt · queue quarantine · J. Petrakis

Replay windows

1 window recorded against this contract.

Replay register

RPL-017Refused

Connector defect · Jul 29, 2026 to Aug 17, 2026

The configuration feed has not moved in two and a half days against a one-day commitment.

0 replayed · 0 held at the idempotence key · 0 duplicates created

Write-back routes into this system

No write-back route is designed into this system.

Write-back register

What goes stale when this feed does

1 asserted figure depends on Configuration Management Database. more

Freshness

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. more

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. more

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.