Connect · ingestion spine
Connector contracts
Nothing is read from a source system until the shape of what will be read is written down and agreed. The contract names the entity, the primary key, the cardinality, every field with its type and lawful basis, the validation rule that admits or rejects a record, the freshness commitment and what may be written back. Security and privacy review the contract. The connector is generated against it. When the source moves, the contract is what detects it.
Health
How much of the estate has a contract behind it
Coverage, ratification, and whether the declared shape has ever been compared against a real extract.
The contract register
26 contracts carrying 128 fields and a declared 5,525,800 records a day. Open a row for the field list, the validation rules and everything that has passed through the staging boundary against it.
| System | Entity | Ver | Status | Drift | Fields | Per day | Commit | Last validated | Owner | |
|---|---|---|---|---|---|---|---|---|---|---|
| Group ERP — Financials SAP S/4HANA · critical | Journal lines | v2 | Ratified | In contract | 7 | 148,000 | 1 h | 11 d ago · 25,000 rows | D. Halvorsen | Open |
| Group ERP — Materials and Inventory SAP S/4HANA MM · high | Material movements | v2 | Ratified | In contract | 6 | 96,000 | 4 h | 18 d ago · 12,000 rows | R. Nakamura | Open |
| Source-to-Pay Suite SAP Ariba · critical | Purchase requisitions | v2 | Ratified | Drifted | 6 | 34,000 | 1 h | 6 d ago · 8,000 rows | K. Boateng | Open |
| Invoice Capture and AP Automation Basware · high | Supplier invoices | v2 | Ratified | In contract | 6 | 82,000 | 30 min | 9 d ago · 15,000 rows | M. Okonjo | Open |
| Customer Relationship Management Salesforce Sales Cloud · critical | Opportunities | v2 | Ratified | In contract | 6 | 21,000 | 15 min | 21 d ago · 9,000 rows | A. Whitfield | Open |
| Configure, Price and Quote Salesforce CPQ · high | Quote lines | v1 | In review | Never checked | 5 | 14,000 | 30 min | Never | A. Whitfield | Open |
| Core HR and Payroll Workday HCM · critical | Worker records | v2 | Ratified | In contract | 7 | 4,200 | 4 h | 14 d ago · 3,000 rows | S. Bergqvist | Open |
| Recruiting and Applicant Tracking Greenhouse · medium | Applications | v1 | Draft | Never checked | 5 | 2,400 | 12 h | Never | S. Bergqvist | Open |
| IT Service Management ServiceNow ITSM · high | Service requests | v2 | Ratified | In contract | 6 | 62,000 | 15 min | 4 d ago · 20,000 rows | J. Petrakis | Open |
| Configuration Management Database ServiceNow CMDB · high | Configuration items | v1 | In review | Never checked | 5 | 8,000 | 1 d | Never | J. Petrakis | Open |
| Contract Lifecycle Management Icertis · high | Contracts | v2 | Ratified | Drifted | 5 | 900 | 2 h | 27 d ago · 600 rows | V. Marchetti | Open |
| Document and Matter Management iManage · medium | Matter documents | v1 | Draft | Never checked | 5 | 5,400 | 12 h | Never | V. Marchetti | Open |
| Enterprise Data Warehouse Snowflake · critical | Conformed fact rows | v2 | Ratified | In contract | 5 | 2,400,000 | 4 h | 8 d ago · 100,000 rows | N. Ferreira | Open |
| Reporting Semantic Layer Power BI shared datasets · medium | Reporting measures | v3 | Superseded | Never checked | 3 | 1,200 | 1 d | Never | N. Ferreira | Open |
| Treasury and Cash Management Kyriba · critical | Cash positions | v1 | In review | Never checked | 4 | 3,200 | 1 h | Never | L. Duarte | Open |
| Bank Connectivity Gateway SWIFT and host-to-host channels · critical | Payment instructions | v1 | Draft | Never checked | 4 | 0 | 1 h | Never | L. Duarte | Open |
| Indirect Tax Engine Vertex · high | Tax determinations | v2 | Ratified | In contract | 4 | 1,900 | 1 d | 33 d ago · 2,000 rows | F. Aubert | Open |
| Marketing Automation Marketo Engage · medium | Campaign engagements | v1 | In review | Never checked | 5 | 210,000 | 2 h | Never | C. Delgado | Open |
| Digital Analytics Adobe Analytics · medium | Session events | v1 | Draft | Never checked | 4 | 1,800,000 | 4 h | Never | C. Delgado | Open |
| Product Lifecycle Management Siemens Teamcenter · high | Part revisions | v1 | In review | Never checked | 4 | 6,200 | 8 h | Never | H. Lindgren | Open |
| Research Notebook and Experiment Data Benchling · medium | Experiment records | v1 | Draft | Never checked | 3 | 0 | 1 d | Never | P. Iyer | Open |
| Contact Center Platform Genesys Cloud CX · high | Contact interactions | v2 | Ratified | In contract | 5 | 420,000 | 15 min | 16 d ago · 40,000 rows | T. Abara | Open |
| Workforce Management NICE WFM · medium | Schedule intervals | v1 | In review | Never checked | 4 | 1,400 | 12 h | Never | T. Abara | Open |
| Supply and Demand Planning Kinaxis RapidResponse · high | Supply plan lines | v2 | Ratified | In contract | 5 | 168,000 | 4 h | 12 d ago · 30,000 rows | R. Nakamura | Open |
| Transportation Management Blue Yonder TMS · medium | Shipments | v1 | Draft | Never checked | 4 | 12,000 | 12 h | Never | G. Mwangi | Open |
| Planning and Consolidation Anaplan · high | Plan version lines | v2 | Ratified | In contract | 5 | 24,000 | 1 d | 20 d ago · 18,000 rows | D. Halvorsen | Open |
Who has read the contract
Security reviews what the connector authenticates as and what it can reach. Privacy reviews what personal data is inside the field list and on what lawful basis. Neither review is done by the team that wrote the contract.
Field-level drift
Every one of the 128 contracted fields is in exactly one of these states. A field is only ever moved out of never-checked by reading a sample.
Personal data inside the contracts
19 fields of 128 carry personal data. Each one names a lawful basis on the contract itself, which is what privacy review reads.
| Field | Contract | Basis | Sensitivity | Handling at the boundary |
|---|---|---|---|---|
| Candidate id | Recruiting and Applicant Tracking | Consent | restricted | Pseudonymized. Consent basis, which means a withdrawal has to propagate and no mechanism for that exists yet. |
| Creditor account | Bank Connectivity Gateway | Legal obligation | restricted | Hashed at the boundary. The clear IBAN never enters the platform. |
| Transcript | Contact Center Platform | Consent | restricted | Excluded from the contract. This exclusion is the privacy condition. |
| Approved by | Configure, Price and Quote | Legitimate interest | confidential | Pseudonymized. This field is the reason the security review is still open. |
| Owner | Customer Relationship Management | Legitimate interest | confidential | Pseudonymized. Used for routing only, never for individual performance measurement, which the contract states in words. |
| Author | Document and Matter Management | Legitimate interest | restricted | Pseudonymized. |
| Author | Research Notebook and Experiment Data | Performance of a contract | restricted | Pseudonymized. |
| Entered by | Group ERP — Financials | Legitimate interest | confidential | Pseudonymized at the staging boundary. The clear value never enters the spine; only the hash is stored. |
| Worker id | Core HR and Payroll | Performance of a contract | confidential | Stable across the employment lifecycle. Never reused. |
| Compensation | Core HR and Payroll | Performance of a contract | restricted | Excluded from the contract. The platform has no use for individual compensation and does not ingest it. |
| Performance rating | Core HR and Payroll | Legitimate interest | restricted | Excluded. Named in the works-council pack as a field the platform will not read. |
| Caller | IT Service Management | Legitimate interest | confidential | Pseudonymized at the boundary. |
| Person id | Marketing Automation | Consent | restricted | Pseudonymized, nullable for anonymous engagement. The consent basis is why the privacy review is open. |
| Consent state | Marketing Automation | Consent | restricted | Must be present on every non-anonymous row. A missing consent state rejects the record outright rather than quarantining it. |
| Requested by | Source-to-Pay Suite | Performance of a contract | confidential | Pseudonymized at the boundary. This is the condition attached to the privacy approval. |
| Approval delegate | Source-to-Pay Suite | Legitimate interest | confidential | Not declared in this version of the contract. |
| Visitor id | Digital Analytics | Consent | restricted | Pseudonymized. Under the draft contract this field is the reason privacy review has not started. |
| Agent id | Workforce Management | Performance of a contract | confidential | Pseudonymized. |
| Adherence percent | Workforce Management | Legitimate interest | restricted | Held out of the contract until the works-council restriction is written into it. |
Actions
What is waiting on a person
A contract is the artifact security and privacy review, and the connector is generated against it. The queue below is contract work, not connection work: none of it makes a feed run.
Validate a contract against a sample
Written and never tested. Until a sample is read, the declared shape is an assertion.
Take a contract to ratification
Still draft or in review. A connector generated from it can change underneath the estate.
Start a security review
No reviewer has looked at what this contract reads or how it authenticates.
Start a privacy review
Personal fields may be inside the contract with no lawful basis recorded against them.
Close a drift finding
The source no longer matches the contract. Downstream figures are wrong in a way nothing else detects.
Trace out a superseded contract
Replaced, still being read. Every consumer has to move before it can be switched off.
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 write a contract, validate it against a sample extract and record a drift finding against a named field. It cannot establish the connection, change what the source system holds, or sign off its own security and privacy review — all three sit with people outside this platform.
Live observability
What the record shows right now
Drift state, which is an exhaustive partition of all 26 contracts: every contract is either in contract against its last sample, drifted, or has never been checked at all.
Current distribution
26 contracts
Is policy and strategy coming to fruition
Whether the written intent is holding here
13 of 26 contracts are ratified, and 13 have never been validated against a sample.
Not holding on the record
The written intent is contract-first: nothing is read from a source system until the shape of what will be read is agreed, reviewed and ratified. Measured against that, 13 contracts are ratified, 6 are in review, 6 are still draft and 1 is superseded but still being read. The harder finding is validation: 13 contracts — 50% — have never been tested against a real sample, so their declared shape is an assertion rather than an observation. Of the 13 that have been tested, 2 are drifted. The discipline exists and it is written down. It has not yet been applied across the estate.
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.
13 of the 26 contracts have never been compared against an extract. For those, the field list, the types and the cardinality are what somebody wrote down after reading documentation — not what a sample proved. Drift cannot be detected on a contract that has never been validated, so their in-contract state is unknown rather than good, and the register says never checked rather than showing a green mark.
The register carries a declared 5,525,800 records a day. That figure is the contracted volume, not observed throughput. Observed volume only exists for the batches that have passed the staging boundary, and it is shown there.