CTR-ATS · version 1
Recruiting and Applicant Tracking — Applications
The fairness monitoring surface depends on this feed and cannot be trusted until the contract is reviewed, because adverse-impact measurement on unreviewed candidate data is itself a risk.
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 |
|---|---|---|---|---|---|---|
| Application id | application.id | application.ref | string(24) | keyinternal | Never checked | Source-generated. |
| Requisition id | application.job_id | application.requisitionRef | string(24) | internal | Never checked | Must resolve to an open or recently closed requisition. |
| Stage | application.status | application.stage | enum(6) | internal | Never checked | Six declared stages. |
| Candidate id | application.candidate_id | application.candidateHash | string(64) | personalrestricted | Never checked | Pseudonymized. Consent basis, which means a withdrawal has to propagate and no mechanism for that exists yet. |
| Source channel | application.source | application.channel | string(40) | internal | Never checked | Free text in the source. Mapped against a 22-value table; unmapped values land as other rather than being invented. |
What has passed the staging boundary against this contract
1 batch · 640 arrived · 623 admitted · 0 quarantined · 17 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0014 | Aug 17, 21:00 | 640 | 623 | 0 | 17 | Partly admitted | 623 admitted · 0 quarantined · 17 rejected outright. |
Rejects raised against these batches
1 reason covering 17 records. Each one names a field, what was observed and what the contract expected.
Replay windows
No replay has been requested 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 Recruiting and Applicant Tracking. 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 |
|---|---|---|---|---|
| Worker records in scope | Human resources cockpit | contributing | Show it unchanged | Pending hires are shown separately and are not inside the in-scope count. |
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.