Connect · ingestion spine
Freshness and staleness
A feed carries a commitment in minutes, the same way a service carries a service level. Missing it is not a background condition to be discovered later — it is an event with a consequence, and the consequence is written on the figures the feed supports. This page holds the commitments, what was last observed against them, and exactly which asserted figures change on screen when a feed goes stale.
Health
Commitments against what was last observed
Every feed on the estate carries a commitment. Not every feed has ever reported a latency against it.
Commitment against observation
Ordered by how far past the commitment the feed is. A feed with no observation sits at the bottom because there is nothing to rank it on.
| Feed | Domain | Commit | Observed | Against commitment | Last sync | Feed health | Figures | Contract |
|---|---|---|---|---|---|---|---|---|
Transportation Management Blue Yonder TMS · medium | supply | 12 h | 1.4 d | +21 h over | Aug 17, 00:00 | stale | 0 | draft · never-checked |
Digital Analytics Adobe Analytics · medium | marketing | 4 h | 10.2 h | +6.2 h over | Aug 17, 22:48 | stale | 0 | draft · never-checked |
Configuration Management Database ServiceNow CMDB · high | itsm | 1 d | 2.5 d | +1.5 d over | Aug 15, 20:50 | stale | 1 | in-review · never-checked |
Configure, Price and Quote Salesforce CPQ · high | crm | 30 min | 44 min | +14 min over | Aug 18, 08:16 | degraded | 0 | in-review · never-checked |
Treasury and Cash Management Kyriba · critical | banking | 1 h | 1.2 h | +11 min over | Aug 18, 07:49 | degraded | 2 | in-review · never-checked |
Document and Matter Management iManage · medium | legal | 12 h | 13.5 h | +1.5 h over | Aug 17, 19:30 | degraded | 1 | draft · never-checked |
Workforce Management NICE WFM · medium | service | 12 h | 11.5 h | 96% of it | Aug 17, 21:30 | healthy | 0 | in-review · never-checked |
Planning and Consolidation Anaplan · high | ledger | 1 d | 22.6 h | 94% of it | Aug 17, 10:25 | healthy | 0 | ratified · in-contract |
Recruiting and Applicant Tracking Greenhouse · medium | hcm | 12 h | 11.1 h | 92% of it | Aug 17, 21:56 | healthy | 1 | draft · never-checked |
Invoice Capture and AP Automation Basware · high | procurement | 30 min | 27 min | 90% of it | Aug 18, 08:33 | healthy | 4 | ratified · in-contract |
Reporting Semantic Layer Power BI shared datasets · medium | analytics | 1 d | 21.5 h | 90% of it | Aug 17, 11:30 | healthy | 1 | superseded · never-checked |
Supply and Demand Planning Kinaxis RapidResponse · high | supply | 4 h | 3.6 h | 89% of it | Aug 18, 05:26 | healthy | 0 | ratified · in-contract |
Source-to-Pay Suite SAP Ariba · critical | procurement | 1 h | 52 min | 87% of it | Aug 18, 08:08 | healthy | 5 | ratified · drifted |
Contact Center Platform Genesys Cloud CX · high | service | 15 min | 13 min | 87% of it | Aug 18, 08:47 | healthy | 0 | ratified · in-contract |
Core HR and Payroll Workday HCM · critical | hcm | 4 h | 3.4 h | 85% of it | Aug 18, 05:37 | healthy | 2 | ratified · in-contract |
Product Lifecycle Management Siemens Teamcenter · high | engineering | 8 h | 6.7 h | 84% of it | Aug 18, 02:18 | healthy | 1 | in-review · never-checked |
Contract Lifecycle Management Icertis · high | legal | 2 h | 1.6 h | 80% of it | Aug 18, 07:24 | healthy | 1 | ratified · drifted |
Group ERP — Materials and Inventory SAP S/4HANA MM · high | supply | 4 h | 3.2 h | 80% of it | Aug 18, 05:49 | healthy | 2 | ratified · in-contract |
Indirect Tax Engine Vertex · high | tax | 1 d | 18.4 h | 77% of it | Aug 17, 14:38 | healthy | 0 | ratified · in-contract |
Customer Relationship Management Salesforce Sales Cloud · critical | crm | 15 min | 11 min | 73% of it | Aug 18, 08:49 | healthy | 3 | ratified · in-contract |
Enterprise Data Warehouse Snowflake · critical | analytics | 4 h | 2.9 h | 73% of it | Aug 18, 06:04 | healthy | 3 | ratified · in-contract |
Marketing Automation Marketo Engage · medium | marketing | 2 h | 1.5 h | 73% of it | Aug 18, 07:32 | healthy | 0 | in-review · never-checked |
Group ERP — Financials SAP S/4HANA · critical | ledger | 1 h | 38 min | 63% of it | Aug 18, 08:22 | healthy | 6 | ratified · in-contract |
IT Service Management ServiceNow ITSM · high | itsm | 15 min | 9 min | 60% of it | Aug 18, 08:51 | healthy | 3 | ratified · in-contract |
Bank Connectivity Gateway SWIFT and host-to-host channels · critical | banking | 1 h | — | Never measured | — | blocked | 3 | draft · never-checked |
Research Notebook and Experiment Data Benchling · medium | engineering | 1 d | — | Never measured | — | blocked | 1 | draft · never-checked |
What goes stale when a feed does
18 asserted figures carried on the lineage register, mapped through 40 dependencies back to the feeds that produce them. The rule column is what the surface does at the moment the figure is displayed, not a background job that runs later.
What the rule does when the feed is late
An exhaustive partition of all 40 mapped dependencies. Each dependency carries exactly one rule, and the rule is written on the dependency rather than decided by whoever is looking at the screen.
Where the discipline runs out
Two honest gaps, both of which weaken every claim on this page.
Actions
What is waiting on a person
Freshness is a service level a feed promises about itself. When it is missed, the work is not to hide the number but to mark every figure that leans on it.
Bring a feed back inside its commitment
Running, but slower than the interval the system itself declared.
Explain a suppressed figure
A blocking dependency is stale or absent, so the figure is withheld rather than shown wrong.
Map an asserted figure to its feeds
The figure is published with no recorded dependency, so a stale feed cannot mark it.
Get a first arrival from a feed that has never run
No actual interval has ever been observed, so the commitment is untested.
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 compare an observed arrival interval against the commitment on the contract, and propagate the result to every figure that declares a dependency on that feed. It cannot make a feed arrive sooner, change a commitment without a contract version, or decide on its own that a stale figure is close enough — the response to staleness is declared per dependency, not chosen at display time.
Live observability
What the record shows right now
Freshness state, an exhaustive partition of all 26 source systems: each is inside its commitment, outside it, or has never produced a measurable interval.
Current distribution
26 systems
Is policy and strategy coming to fruition
Whether the written intent is holding here
6 of the 18 asserted figures lean on a feed that is late or has never arrived.
Not holding on the record
The written intent is that a stale feed marks every figure derived from it, at the point the figure is displayed rather than in a footnote nobody reads. The mechanism exists: 40 dependencies are recorded across 16 of the 18 asserted figures, and each one declares what happens when the feed goes stale. Measured against it, 6 systems are outside their own commitment and 2 have never produced a measurable interval, which together touch 6 figures. 4 of those carry a blocking dependency, meaning the honest response is to withhold the number entirely. 2 figures have no dependency recorded at all, so nothing would mark them either way.
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.
The observed latency on each row is the last figure the connector reported, not a rolling distribution. There is no percentile here, no time series and no alerting history, because none of those exist yet. A feed shown inside its commitment is a feed that was inside it the last time anything measured, and 2 feeds have never measured at all.
16 of the 18 asserted figures are mapped back to the feeds that produce them, through 40 dependencies. The mapping is authored, not derived: somebody wrote down which feed a figure depends on, and nothing in the platform verifies that the query behind the figure actually reads that feed. Until it does, the staleness marking is only as good as the mapping.