Systems of record
Every system the platform reads, and whether it is actually current
A platform that cannot name where a number came from is asserting, not reporting. This registry lists each system of record behind the estate, who owns the connection, how it authenticates, when it last synchronized successfully, and whether that sync met the freshness its owner committed to. Health is derived from the clock, never declared.
Health
What is actually connected
Source systems by connection state and feed health, with the sync runs behind them.
Without customer credentials these connectors run against modeled feeds. The registry, the reconciliation ledger, the lineage and the quality gates are real mechanisms; the connections behind them are simulated until real credentials are supplied. Two systems are not even modeled — they carry the reason on their row, because a gap that is written down can be closed and a gap that is hidden cannot.
Connector registry
2 of 26 systems shown
| System | Domain | Direction | Authentication | Owner | Last sync | Commitment | Health | Facts traced |
|---|---|---|---|---|---|---|---|---|
| Core HR and Payroll Workday HCM · hcm Modeled feedcritical | hcm | bidirectional writes back | OAuth 2.0 client credentials | S. Bergqvist People Systems | 3.4 hr ago | 4.0 hr 85% of window used | Inside commitment | 436 |
| Recruiting and Applicant Tracking Greenhouse · ats Modeled feed | hcm | inbound | API key | S. Bergqvist People Systems | 11.1 hr ago | 12.0 hr 92% of window used | Inside commitment | 146 |
Systems with no feed
Declared gaps, not silent ones
Bank onboarding, key ceremony and a payment-channel penetration test are all customer-side prerequisites. No modeled feed is offered here on purpose: pretending to hold a bank channel would be the wrong thing to model.
Research data classification review is not complete. Until the data protection assessment lands, no feed is stood up, modeled or otherwise.
Running late
Feeds outside the freshness their owner committed to
Most recent sync attempt on each feed
| Run | System | Started | Duration | Read | Written | Failed | Outcome |
|---|---|---|---|---|---|---|---|
| SYN-CMDB-01 | Configuration Management Database | 2.5 days ago | 700s | 3,917 | 0 | 3,917 | failed Extract aborted. The feed has not produced a usable payload since, which is why the registry shows it outside its commitment. |
| SYN-WEB-ANALYTICS-01 | Digital Analytics | 10.3 hr ago | 651s | 451,163 | 0 | 451,163 | failed Extract aborted. The feed has not produced a usable payload since, which is why the registry shows it outside its commitment. |
| SYN-TMS-01 | Transportation Management | 33.1 hr ago | 239s | 4,102 | 0 | 4,102 | failed Extract aborted. The feed has not produced a usable payload since, which is why the registry shows it outside its commitment. |
| SYN-ERP-FI-01 | Group ERP — Financials | 42 min ago | 346s | 22,738 | 5,606 | 0 | succeeded Completed inside the committed window. |
| SYN-ERP-MM-01 | Group ERP — Materials and Inventory | 3.3 hr ago | 298s | 30,106 | 2,470 | 0 | succeeded Completed inside the committed window. |
| SYN-S2P-SUITE-01 | Source-to-Pay Suite | 56 min ago | 356s | 8,442 | 1,197 | 0 | succeeded Completed inside the committed window. |
| SYN-AP-AUTOMATION-01 | Invoice Capture and AP Automation | 31 min ago | 585s | 13,013 | 2,075 | 0 | succeeded Completed inside the committed window. |
| SYN-CRM-01 | Customer Relationship Management | 15 min ago | 921s | 15,141 | 1,774 | 0 | succeeded Completed inside the committed window. |
| SYN-CPQ-01 | Configure, Price and Quote | 48 min ago | 658s | 3,163 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-HCM-01 | Core HR and Payroll | 3.5 hr ago | 931s | 2,524 | 523 | 0 | succeeded Completed inside the committed window. |
| SYN-ATS-01 | Recruiting and Applicant Tracking | 11.1 hr ago | 827s | 958 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-ITSM-01 | IT Service Management | 13 min ago | 142s | 9,037 | 2,000 | 0 | succeeded Completed inside the committed window. |
| SYN-CLM-01 | Contract Lifecycle Management | 1.7 hr ago | 657s | 873 | 182 | 0 | succeeded Completed inside the committed window. |
| SYN-DMS-01 | Document and Matter Management | 13.6 hr ago | 936s | 11,349 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-EDW-01 | Enterprise Data Warehouse | 3.0 hr ago | 888s | 438,407 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-BI-SEMANTIC-01 | Reporting Semantic Layer | 21.6 hr ago | 759s | 120 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-TREASURY-01 | Treasury and Cash Management | 75 min ago | 646s | 539 | 105 | 0 | succeeded Completed inside the committed window. |
| SYN-TAX-01 | Indirect Tax Engine | 18.4 hr ago | 152s | 220 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-MKT-AUTOMATION-01 | Marketing Automation | 1.5 hr ago | 360s | 14,430 | 1,229 | 0 | succeeded Completed inside the committed window. |
| SYN-PLM-01 | Product Lifecycle Management | 6.8 hr ago | 148s | 6,238 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-CCAAS-01 | Contact Center Platform | 17 min ago | 451s | 50,680 | 8,241 | 0 | succeeded Completed inside the committed window. |
| SYN-WFM-01 | Workforce Management | 11.6 hr ago | 139s | 347 | 0 | 0 | succeeded Completed inside the committed window. |
| SYN-PLANNING-01 | Supply and Demand Planning | 3.6 hr ago | 875s | 20,119 | 3,842 | 0 | succeeded Completed inside the committed window. |
| SYN-FPA-01 | Planning and Consolidation | 22.6 hr ago | 227s | 3,257 | 715 | 0 | succeeded Completed inside the committed window. |
Actions
What is waiting on a person
Every connection on this page is described, not established. The queue below is the work that turns a description into a running feed.
Commission a real connection
The contract is written and the shape is known. Nothing is flowing.
Re-run a sync that did not fully land
Failed or partial runs leave the downstream figure short without saying so.
Clear a blocked or degraded feed
The system names what is stopping it. None of these clear themselves.
Chase a stale feed past its freshness commitment
Older than the interval the system itself promised.
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 one thing: a sync run against a named system, recording what it pulled, what it dropped and how long it took. It cannot create the connection itself, change what the source holds, or write back into a system of record — every write-back on this estate is still a person in the source application.
Live observability
What the record shows right now
Connection state, which is the only honest axis for this page: it says whether a feed exists at all. Health describes how a feed behaves once it runs, so with nothing live on the estate the 18 rows it currently calls healthy are modeled, not observed.
Current distribution
26 systems
Is policy and strategy coming to fruition
Whether the written intent is holding here
No source system carries a live connection: 24 are modeled and 2 are not connected.
Not holding on the record
The written intent is that this platform is the spine every system feeds. Measured against that, 24 systems are modeled — the interface contract exists and the data shape is agreed, but nothing is flowing — and 2 are not connected at all. That is 100% of the estate. Every figure elsewhere on this platform that depends on those systems is therefore a modeled figure, and is labeled as one at the point it is shown. Nothing here should be read as a live integration status until a connection state changes.
What this page is, and what it is not
It is a registry of the systems the platform depends on, with an owner, an authentication mode, a freshness commitment and a derived health state on every row. Health is computed by comparing the last successful sync against the commitment; nothing declares itself healthy.
It is not a live integration console. 0 of 26 systems are reading a customer instance in this build. 24 carry modeled feeds and 2 carry no feed at all. Connecting any of them requires the customer's own credentials, a network path and, for the write-back systems, a change record in the receiving system.