Connect · item 15

Data quality gates at intake

Bad data does not become less expensive further down the line. Sixteen checks sit at the first station of every line, covering completeness, validity, duplication, referential integrity, timeliness and consistency. A unit that fails is blocked outright or held in a quarantine queue with a named owner — never quietly waved through with a flag nobody reads.

Connector registry

Health

What the rules are catching

Active and monitoring rules, and everything they have held, released or rejected.

Gates at intake

14 enforcing · 2 monitoring only

Checks run

203,658

Across the whole estate at first station

Pass rate

99.6%

767 checks failed

Held right now

of 171 items ever quarantined

Held over 72 hours

Oldest is 9.1 days old

Rejected at intake

47 released after review

What the gates test for

Six dimensions. A check that has never fired is shown as never having fired, not as evidence of a clean estate.

Completeness4 gates · 53,176 checks · 175 failed · 99.7% pass

Validity3 gates · 42,810 checks · 108 failed · 99.7% pass

Duplication2 gates · 17,406 checks · 87 failed · 99.5% pass

Referential5 gates · 74,103 checks · 320 failed · 99.6% pass

Timeliness1 gate · 945 checks · 15 failed · 98.4% pass

Consistency1 gate · 15,218 checks · 62 failed · 99.6% pass

What happens on failure

The action is stated on the gate, not decided later.

Block4 gates

The unit never enters the line.

Quarantine8 gates

Held at intake for a named owner to clear.

Warn4 gates

Enters the line carrying a flag that travels with it.

Gates that have never fired

Reported as a zero, not as a pass.

1 of 16 gates have run without a single failure. That is either a genuinely clean condition or a check that is not reaching the data it was written for. It is listed here so somebody has to decide which.

DQ-16Research payload provenance recorded9,928 run

The gates

Each names the dimension it tests, the expression it evaluates, what happens when it fails, and who owns the failures.

All 16 Completeness Validity Duplication Referential Timeliness Consistency

Gate	Dimension	Applies to	Expression	On failure	Run	Failed	Pass	Held	Owner
DQ-10 Source extract inside its freshness commitment High	Timeliness	Any unit relying on an inbound feed all-lines	every source system the unit reads has synchronized within its committed freshness window	Warn threshold 97%	945	15	98.4%	8	N. Ferreira

Quarantine queue

15 items match the current filter. Every held item has an owner and an age.

All 171 Held · 67 In review · 28 Released · 47 Rejected at intake · 29 Gate DQ-10 — clear

Item	Function · line	Gate	Field	Observed	Expected	Source	Age	Status	Owner	Outcome
IT2B-1009 Access request at confirm DQ-10-Q-005	Information Technology IT2B	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	8.5 days	Released	N. Ferreira	Corrected at source and released back onto the line with the correction recorded.
FI11B-1011 Change at escalate DQ-10-Q-014	Finance FI11B	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	7.2 days	Released	N. Ferreira	Corrected at source and released back onto the line with the correction recorded.
IT11A-1015 Cost line at publish DQ-10-Q-002	Information Technology IT11A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	5.8 days	Rejected at intake	N. Ferreira	Rejected at intake. The unit never entered the line and the requester was told why.
AD1B-1001 Work order at dispatch DQ-10-Q-007	Administration AD1B	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	5.1 days	In review	N. Ferreira	—
LG3B-1041 Corporate action at officer sign DQ-10-Q-008	Legal LG3B	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	4.9 days	Rejected at intake	N. Ferreira	Rejected at intake. The unit never entered the line and the requester was told why.
PR10A-1002 Payment run at remittance advice DQ-10-Q-013	Procurement & Source-to-Pay PR10A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	4.3 days	Held	N. Ferreira	—
RD1A-1008 Research thread at draft findings DQ-10-Q-009	Research & Development RD1A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	4.3 days	In review	N. Ferreira	—
PR10A-1023 Payment run at optimize discount DQ-10-Q-006	Procurement & Source-to-Pay PR10A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	3.9 days	Held	N. Ferreira	—
CS1C-1039 Contact at detect surge DQ-10-Q-001	Customer Service CS1C	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	3.8 days	In review	N. Ferreira	—
MK4A-1007 Content asset at fact verify DQ-10-Q-015	Marketing MK4A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	2.8 days	Held	N. Ferreira	—
SL8B-1014 Partner deal at vet DQ-10-Q-010	Sales SL8B	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	2.3 days	Held	N. Ferreira	—
MK4A-1034 Content asset at sme review DQ-10-Q-011	Marketing MK4A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	45 hr	Released	N. Ferreira	Corrected at source and released back onto the line with the correction recorded.
IT4C-1039 Infrastructure change at run backup DQ-10-Q-003	Information Technology IT4C	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	28 hr	Held	N. Ferreira	—
HR7A-1036 Assignment at offer internal DQ-10-Q-004	Human Resources HR7A	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	2 hr	Released	N. Ferreira	Corrected at source and released back onto the line with the correction recorded.
AD10B-1018 Service request at issue actions DQ-10-Q-012	Administration AD10B	DQ-10	every source system the	outside window	every source system the unit reads has synchronized within its committed freshness window	Enterprise Data Warehouse	2 hr	Rejected at intake	N. Ferreira	Rejected at intake. The unit never entered the line and the requester was told why.

Which lines carry the intake burden

Quarantine volume by function, all time.

Procurement & Source-to-Pay57

Information Technology26

Human Resources22

Supply Chain13

Marketing8

AI GBS & Global Business Services8

Finance7

Administration7

Legal5

Revenue Operations4

Sales4

Customer Service4

Engineering3

Research & Development3

Actions

What is waiting on a person

Quarantine is a holding pen, not a decision. Every item below is work that stopped and is waiting for somebody to say what happens to it.

Judge a quarantined item

Held by a rule. Nobody has looked at it yet.

Fix the source behind a rejection

Rejected items keep arriving until the upstream cause changes.

Finish a review already open

Picked up, not concluded.

Promote a monitoring rule to active

The rule watches and reports but does not hold anything.

Operations

What this desk is allowed to start

A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.

Trigger and bound

This desk can start a rule run across a named batch, and it can move an item into quarantine. It cannot release an item, reject one, or change a threshold — releasing bad data is the whole risk this layer exists to manage, so it stays with a person.

Live observability

What the record shows right now

What happened to everything the rules have held.

Current distribution

171 items

Released4727%

In review2816%

Quarantined6739%

Rejected2917%

Is policy and strategy coming to fruition

Whether the written intent is holding here

14 of 16 rules are enforcing. 95 items are held and undecided.

Not holding on the record

The written intent is that no unchecked record reaches a downstream figure. 14 rules enforce that today and 2 only watch. The queue is the real test: 67 items are held with nobody assigned and 28 are open with somebody assigned, against 47 released and 29 rejected historically. A held item is not a failure of the rule — it is the rule working — but a held item nobody judges is a figure quietly missing its input.

What this page is, and what it is not

The gates, the expressions, the thresholds and the quarantine queue are real mechanisms. They run at the first station of every line and they hold work that fails. What they run against is the modeled feed described on the connector registry — connect a customer instance and the same gates run unchanged against real intake.

2 of the 16 gates are set to monitor rather than enforce. They are counted in the check totals but they stop nothing. That is a deliberate state for a gate whose false-positive rate has not yet been characterized, and it is shown rather than hidden behind an overall pass rate.

62 items have been held for more than seventy-two hours, the oldest for 9.1 days. A quarantine queue that ages without clearing is a queue that people have learned to route around, so the age is shown on every row and never averaged away.