> ## Documentation Index
> Fetch the complete documentation index at: https://docs.operata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor

> Core is the CX telemetry pipeline. It ingests signals, correlates them to a contact, applies redaction and validation, stores the result as observations, and derives insights and journeys from them.

Core is the CX telemetry pipeline. It turns the signals [Collect](/docs/signal-overview) collects into a single, queryable record of what happened on every contact.

## How it works

Core runs four steps on every signal it receives.

1. **Ingest** — accept the signal from the collector that emitted it.
2. **Correlate** — attach it to the [contact](/docs/concepts-contacts-and-interactions) it belongs to: `Contact` in Amazon Connect, `Interaction` in NICE CXOne, `Conversation` in Genesys Cloud.
3. **Redact and validate** — apply your account's policy and reject what does not conform.
4. **Persist** — store the result as an [observation](/docs/concepts-signals-and-observations).

The [insight engine](/docs/concepts-insights) then reads the observations on each contact and writes an [insight](/docs/insights-overview) when a known pattern matches — audio one-way, packet loss, agent inactivity, and the rest of the [insights catalog](/docs/insights-catalog). [Customer Journey Trace](/docs/concepts-customer-journey-trace) sits above contacts: when one customer crosses more than one platform, each platform's contact is one span of a single journey.

## Why Core splits signals from observations

The split isolates the wire format from the storage format. Redaction, deduplication, late-arrival reconciliation, and per-account validation all happen between the two, so the value a collector reports is not the value a consumer reads. CTRs can land 5–20 minutes after a contact ends. Storing observations means a query returns a coherent partial view that fills in as more signals arrive, instead of a stream of half-correlated events.

It also means Core can add a new collector without changing anything above it. A new platform emits signals in its own shape, and the observations that reach [Assure](/docs/surface-overview), [Tenor](/docs/guides-mcp-intro), and the [API](/docs/api-getting-started) keep the shape consumers already build against.

## Related

* [Signals and observations](/docs/concepts-signals-and-observations) — what each collector emits and how Operata stores it.
* [Contacts and interactions](/docs/concepts-contacts-and-interactions) — the per-platform record observations attach to.
* [Customer Journey Trace](/docs/concepts-customer-journey-trace) — how Operata links contacts across platforms.
* [Insights](/docs/concepts-insights) — the named detections Operata derives from observations.
* [How Operata works](/docs/get-started-architecture) — the full layer map.