---
title: "Cyber-Market Fusion"
description: "Understand company exposure paths, event timing, and coverage limits."
canonical: https://y2.dev/docs/ontology/explanation/cyber-market-fusion/
---

Ontology & Fusion

# Cyber-Market Fusion

Understand company exposure paths, event timing, and coverage limits.

Cyber-market fusion combines events about a company and the parties connected to it. A supplier's cyber incident and a customer's financial result can appear on the same timeline. Their proximity helps investigation but does not establish causation.

## What the fused view does

For an organization or vendor, fusion:

1. Builds an exposure path from suppliers, customers, parents, subsidiaries, and operated systems.
2. Gathers relevant cyber, market, supply-chain, and geopolitical events.
3. Orders dated events and shows their domain, path, severity, and source.
4. Pairs cyber events with later market events within the selected interval.
5. Identifies workspace topics connected to the company or its counterparties.

Relationships come from the shared catalog and your workspace's ledger. Ledger relationships retain their supporting evidence and verification state.

## What it deliberately does not claim

An adjacency means that a market event followed a cyber event within the selected interval. It can also show whether both events share an exposure path. It does not mean that one caused the other.

Events without a source time remain in **Undated**. They are never assigned a guessed date. Each data source has a read limit. The response reports reached limits in `coverage`. An empty timeline means no matching events were found within those limits. It does not establish that the company has no exposure.

## Why the ledger matters here

An exposure path needs evidence for its relationships. A ledger supplier claim identifies the public page that supports the relationship. Its verification state shows how that evidence was assessed. When both layers link the same counterparty, fusion prefers the ledger relationship.

## Related pages

- [Read a company ledger](https://y2.dev/docs/ontology/tutorial)
- [Record a relationship with evidence](https://y2.dev/docs/ontology/how-to/record-evidence#record-a-supply-or-ownership-tie-in-the-app)
- [Fusion response](https://y2.dev/docs/ontology/reference/fusion)
- [Why a claim ledger](https://y2.dev/docs/ontology/explanation/claim-ledger)