Connect · item 14
Field-level lineage
An agent that cannot say where a number came from has not done the work. For every fact this platform relied on, the register below names the source system, the object and field it was read from, the moment it was extracted, and the transformation applied on the way in. Where no feed exists the fact is marked imputed and carried at low confidence rather than dressed up as observed.
Health
Whether the numbers can be traced
Facts by how they were produced, who consumes them and how confident the chain is.
Facts traced
7,560
Each names a system, a field and an extraction time
Work units covered
185
Every unit on the estate carries a lineage trail
Source systems cited
1
Distinct systems appearing in the trail
Read as presented
53.6%
No transformation between source and platform
Imputed
0
No feed behind them — carried at low confidence
Below 0.75 confidence
0
Flagged wherever they are used
Trace a single work unit
Pick a reference and the platform will list every fact an agent relied on to move it, in the order it was read.
RD1C-1060
Research thread at alert team
Research & Development · Discovery Research · line RD1C · held by GBS spine (gbs)
| Fact | Source system | Object · field | Extracted | Transformation | Relied on by | Used for | Confidence |
|---|---|---|---|---|---|---|---|
Invention disclosure reference ip_disclosure | Document and Matter Management Modeled feed | Matter .matterId | 2026-08-17 19:10 13.8 hr ago | Read as presented Reference only. | GBS spine gbs | Routing a disclosure to counsel. | 0.95 |
Protocol version protocol_version | Research Notebook and Experiment Data Not connected | Protocol .version | 2026-07-15 09:00 34.0 days ago | Imputed No feed exists. The value shown is a placeholder carried by the reference estate and is marked low confidence everywhere it appears. | GBS spine gbs | Nothing that clears a gate. Research units are held evidence-light on purpose. | 0.30 |
Assay result summary assay_result | Research Notebook and Experiment Data Not connected | Result .value, unit | 2026-06-15 09:00 64.0 days ago | Imputed No feed exists. Placeholder only. | GBS spine gbs | Nothing that clears a gate. | 0.30 |
What was then done with those facts — the evidence chain for this unit
1Discovery OrchestratorCleared scan publications2026-08-18 07:39
2Literature Synthesis AgentCleared match to program2026-08-18 08:06
3Hypothesis Generation AgentHolding at alert team2026-08-18 08:33
Where the facts come from
276 facts in the current view, attributed across 1 system.
How values are handled
Between the source field and the platform.
Read as presented148 · 53.6%
Aggregated128 · 46.4%
Facts standing on nothing
Attributed to a system with no feed at all.
No fact in the current view is attributed to a system without a feed.
Every figure this platform asserts
The acceptance test for this wave: each headline number names the system it came from, the arithmetic behind it, the sync it was read at, and the person who owns it.
18 figures · 18 traced
| Figure | Value | Where it appears | Kind | Source system | Read at | Derivation | Owner |
|---|---|---|---|---|---|---|---|
Work units under management fig-work-units | 2,520 units | Subway map, function cockpit | Measured | Platform ledger | continuous | Counted directly from the platform work ledger. No source system is involved because the platform is the system of record for its own queues. This is a count of the reference estate carried by this build, not of a customer production estate. | N. Ferreira |
Agents in the mesh fig-agents | 143 agents | Overview, function cockpit | Measured | Platform ledger | continuous | Counted from the agent register. Agent definitions are modeled for this build. | N. Ferreira |
Evidence records in the spine fig-evidence | 8,080 records | Evidence spine | Measured | Platform ledger | continuous | Counted from the hash-chained evidence spine and verified by recomputing the chain from genesis. The chain is not anchored to an external timestamping authority. | N. Ferreira |
Transactions processed each week fig-tx-week | 900,433 transactions per week | AI GBS towers | Modeled | Enterprise Data Warehouse | 2026-08-18 06:04 2.9 hr ago | Sum of the four tower volumes. In a connected estate this is counted from conformed transaction history in the warehouse. Modeled. The warehouse connector runs against a modeled feed in this build. | A. Whitfield |
Supplier invoice value cleared fig-ap-cleared | $412,880,000 USD | Reconciliation ledger REC-01 | Derived | Group ERP — Financials | 2026-08-18 08:22 38 min ago | Platform side of the accounts payable reconciliation, summed over units that reached a cleared state in the period and converted at the posting-date rate. Does not tie exactly to the ledger. The residual is itemized as breaks on REC-01. | M. Okonjo |
Open purchase order commitment fig-po-commit | $288,400,000 USD | Reconciliation ledger REC-02 | Derived | Group ERP — Materials and Inventory | 2026-08-18 05:49 3.2 hr ago | Ordered value less consumption on open orders held against procurement and supply-chain lines. Commitment drift against materials management is open and aging. | K. Boateng |
Cost per transaction fig-cost-per-tx | $10.76 USD per transaction | AI GBS towers | Derived | Group ERP — Financials | 2026-08-18 08:22 38 min ago | Tower operating cost from the ledger divided by tower volume from the warehouse. Both sides must be dated the same period or the ratio is meaningless. Modeled inputs on both sides of the ratio in this build. | D. Halvorsen |
Touchless processing rate fig-touchless | 76.0% percent | AI GBS towers | Modeled | Platform ledger | continuous | Share of transactions that completed without a human touch, averaged across towers. Modeled. A real reading requires the operational systems to stamp human intervention, which most do not do consistently. | A. Whitfield |
Worker records in scope fig-headcount | 48,120 workers | Human resources cockpit | Modeled | Core HR and Payroll | 2026-08-18 05:37 3.4 hr ago | Active worker records in core human resources at the effective date. Modeled feed. The figure moves the moment a real directory is connected. | S. Bergqvist |
Active supplier records fig-suppliers | 31,447 suppliers | Procurement cockpit | Modeled | Source-to-Pay Suite | 2026-08-18 08:08 52 min ago | Supplier master records with an active, non-blocked status. Modeled feed. | K. Boateng |
Reconciliation breaks open fig-open-breaks | 46 breaks | Reconciliation ledger | Measured | Platform ledger | continuous | Counted from the reconciliation ledger. Open and investigating states only. Breaks are itemized against modeled source counts in this build. | N. Ferreira |
Reconciliation breaks with no owner fig-unowned-breaks | 9 breaks | Reconciliation ledger | Measured | Platform ledger | continuous | Counted from the reconciliation ledger where no owner has been assigned. This figure is deliberately not zero. An unowned break is the finding. | Unassigned |
Units held in intake quarantine fig-quarantine | 95 units | Intake quality | Measured | Platform ledger | continuous | Counted from the quarantine queue in a held state. Quarantine is produced by the gates running against modeled intake. | N. Ferreira |
Traced facts behind unit decisions fig-lineage | 7,560 facts | Data lineage | Measured | Platform ledger | continuous | Counted from the lineage register. Every work unit carries at least three traced facts. Extraction timestamps follow the modeled sync clock of each connector. | N. Ferreira |
Systems of record in the registry fig-systems | 26 systems | Connector registry | Measured | Platform ledger | continuous | Counted from the connector registry. None of them is connected to a customer instance in this build. | N. Ferreira |
Group cash position fig-cash | $1,284,000,000 USD | Finance cockpit | Modeled | Treasury and Cash Management | 2026-08-18 07:49 71 min ago | Bank balances rolled to legal entity, intraday movements excluded. The bank gateway is not connected at all, so this cannot be confirmed against a statement. | D. Halvorsen |
Contract value under management fig-contract-value | $2,940,000,000 USD | Legal cockpit | Modeled | Contract Lifecycle Management | 2026-08-18 07:24 1.6 hr ago | Total contract value of executed, in-term agreements. Modeled feed. 167 obligations are not covered by any recorded owner. | V. Marchetti |
Research lineage confidence fig-rd-confidence | 0.30 confidence | Research and development cockpit | Modeled | Research Notebook and Experiment Data | continuous | Confidence carried by every research fact, because the electronic notebook has no feed. Held low on purpose. Research units are evidence-light and should not clear gates on this basis. | P. Iyer |
Fact register
First 40 of 276 facts matching the current filter.
| Unit | Fact | Source system | Object · field | Extracted | Transformation | Relied on by | Confidence |
|---|---|---|---|---|---|---|---|
| SC10A-1006 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:24 | Aggregated Statistical and consensus streams combined using the plan version in force. | Cost-to-Serve Agent | 0.79 |
| SC10A-1006 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:24 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Cost-to-Serve Agent | 0.88 |
| SC10A-1010 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:16 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Cost-to-Serve Agent | 0.88 |
| SC10B-1002 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:02 | Aggregated Statistical and consensus streams combined using the plan version in force. | Service Level Modeling Agent | 0.79 |
| SC10B-1009 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:20 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Network Modeling Agent | 0.88 |
| SC10B-1009 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:08 | Aggregated Statistical and consensus streams combined using the plan version in force. | Network Modeling Agent | 0.79 |
| SC10B-1015 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:21 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Network Strategy Agent | 0.88 |
| SC10B-1015 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:16 | Aggregated Statistical and consensus streams combined using the plan version in force. | Network Strategy Agent | 0.79 |
| SC10B-1026 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:19 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Cost-to-Serve Agent | 0.88 |
| SC10B-1026 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:25 | Aggregated Statistical and consensus streams combined using the plan version in force. | Cost-to-Serve Agent | 0.79 |
| SC10B-1028 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:10 | Aggregated Statistical and consensus streams combined using the plan version in force. | Footprint Scenario Agent | 0.79 |
| SC10B-1037 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:08 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Network Modeling Agent | 0.88 |
| SC10B-1037 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:21 | Aggregated Statistical and consensus streams combined using the plan version in force. | Network Modeling Agent | 0.79 |
| SC10C-1006 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:12 | Aggregated Statistical and consensus streams combined using the plan version in force. | Carbon Modeling Agent | 0.79 |
| SC10C-1006 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:08 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Carbon Modeling Agent | 0.88 |
| SC10C-1012 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:18 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Service Level Modeling Agent | 0.88 |
| SC10C-1014 supply-chain/network-design | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:13 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Cost-to-Serve Agent | 0.88 |
| SC10C-1014 supply-chain/network-design | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:08 | Aggregated Statistical and consensus streams combined using the plan version in force. | Cost-to-Serve Agent | 0.79 |
| SC11A-1002 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:25 | Aggregated Statistical and consensus streams combined using the plan version in force. | Supply Resilience Orchestrator | 0.79 |
| SC11A-1012 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:18 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Playbook Activation Agent | 0.88 |
| SC11A-1015 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:11 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Recovery Coordination Agent | 0.88 |
| SC11A-1024 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:11 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Supply Resilience Orchestrator | 0.88 |
| SC11A-1033 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:16 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Disruption Sensing Agent | 0.88 |
| SC11A-1040 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:10 | Aggregated Statistical and consensus streams combined using the plan version in force. | Director, Supply Resilience | 0.79 |
| SC11A-1042 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:17 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | GBS spine | 0.88 |
| SC11A-1050 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:02 | Aggregated Statistical and consensus streams combined using the plan version in force. | Single-source Risk Agent | 0.79 |
| SC11B-1005 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:18 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Director, Supply Resilience | 0.88 |
| SC11B-1005 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:25 | Aggregated Statistical and consensus streams combined using the plan version in force. | Director, Supply Resilience | 0.79 |
| SC11B-1009 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:26 | Aggregated Statistical and consensus streams combined using the plan version in force. | Single-source Risk Agent | 0.79 |
| SC11B-1009 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:07 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Single-source Risk Agent | 0.88 |
| SC11B-1018 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:03 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Supply Resilience Orchestrator | 0.88 |
| SC11B-1024 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:06 | Aggregated Statistical and consensus streams combined using the plan version in force. | Supply Resilience Orchestrator | 0.79 |
| SC11B-1029 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:23 | Aggregated Statistical and consensus streams combined using the plan version in force. | Director, Supply Resilience | 0.79 |
| SC11B-1029 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:24 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Director, Supply Resilience | 0.88 |
| SC11B-1038 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:06 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Resilience Posture Agent | 0.88 |
| SC11B-1038 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:04 | Aggregated Statistical and consensus streams combined using the plan version in force. | Resilience Posture Agent | 0.79 |
| SC11B-1042 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:14 | Aggregated Statistical and consensus streams combined using the plan version in force. | Multi-tier Mapping Agent | 0.79 |
| SC11B-1042 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:14 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Multi-tier Mapping Agent | 0.88 |
| SC11C-1005 supply-chain/resilience-and-risk | Planned lead time | Supply and Demand Planning | SupplyScenario .leadTimeDays | 2026-08-18 05:13 | Read as presented Read from the named planning scenario, whose identifier travels with the value. | Resilience Posture Agent | 0.88 |
| SC11C-1012 supply-chain/resilience-and-risk | Demand signal for the horizon | Supply and Demand Planning | DemandPlan .quantity by period | 2026-08-18 05:23 | Aggregated Statistical and consensus streams combined using the plan version in force. | Director, Supply Resilience | 0.79 |
Actions
What is waiting on a person
Lineage is only useful when somebody acts on a weak link. These are the links weak enough to be worth a person.
1,783
Re-check an aggregation rule
A number built from many rows hides its own outliers.
522
Raise the confidence on a weak fact
Confidence below 0.70 on the fact itself.
356
Replace an imputed value with a measured one
No source held this. It was filled in by rule.
0
Attach an evidence reference
The fact exists but points at no record in the spine.
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 trace: take any figure shown anywhere on this platform and walk it back through every transform to the systems it came from. It cannot correct a value, change a transform, or re-run a source extract — a trace tells you where a number came from and stops.
Live observability
What the record shows right now
How each fact was produced. Direct facts came across unchanged; imputed facts were never held by any source.
Current distribution
7,560 facts
Direct4,46959%
Derived95213%
Aggregated1,78324%
Imputed3565%
Is policy and strategy coming to fruition
Whether the written intent is holding here
59.1% of 7,560 facts came straight from a source. 356 were imputed.
Nothing on the record settles this
The written commitment is that every number on this platform can be walked back to something a system said. That holds structurally — all 7,560 facts carry a transform kind and a chain — but it is weaker than it looks: 356 facts were imputed by rule rather than read from a source, 4,227 are consumed directly by an agent rather than a person, and 0 carry no evidence reference. Lineage here proves how a figure was built. It does not prove the figure is right.
What this page is, and what it is not
The lineage mechanism is real. Every one of the 7,560 facts below carries a named system, a named object and field, an extraction timestamp and a stated transformation, and every one of the 185 work units on the estate has a trail. What sits behind those connectors is modeled until customer credentials are supplied — so the timestamps are real timestamps of real extractions from modeled instances, not of extractions from a customer system.
0 facts are attributed to systems with no feed at all. Those are marked imputed and carried at low confidence rather than presented as observed. Research and development is the clearest case: its laboratory notebook has never been connected, so the facts an agent relies on there are inferred from adjacent systems and held at 0.3 confidence. That is a gap, and the platform shows it as one.
Confidence here is a property of the source and the transformation, not a model score. A direct read from a healthy feed is 0.95 or above; an aggregation is lower; an imputation from no feed is lower still. Nothing on this page is rounded up.