# Context Formation

Context Formation is the **first and foundational stage** of the Context Engine — the process by which raw, fragmented data from multiple systems is collected, normalized, enriched, and correlated into structured, meaningful context that downstream AI systems and automation workflows can reliably use.

Raw data from a CI/CD pipeline means very little in isolation. A failed build, a new deployment, a security alert — each is a signal. Context Formation connects these signals into a coherent picture: *which code change caused this build? Which deployment introduced this vulnerability? Which runtime anomaly correlates with this infrastructure change?*

## **Why Context Formation Is Used in OpsMx**

OpsMx uses Context Formation in the Context Engine to:

* **Eliminate data silos** — normalizing data from 100+ integrated tools into a consistent, unified representation that all AI components can consume
* **Connect events across the lifecycle** — linking a deployment event to the specific code changes that triggered it, the pipeline that built it, and the runtime behavior it produced
* **Enrich raw signals with business context** — adding environment, team, service, and risk-level metadata to make every data point contextually meaningful
* **Ensure downstream AI quality** — garbage-in, garbage-out applies directly to AI systems; Context Formation ensures the data feeding every AI interaction is accurate, complete, and relevant
* **Build the foundation for root cause analysis** — by correlating inputs across systems, Context Formation makes it possible to trace a production incident back through runtime signals, deployment events, code changes, and pipeline executions in a single connected timeline.

## **Key Capabilities**

| Capability                     | Description                                                                                                    |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------- |
| **Multi-Source Ingestion**     | Continuously ingests data from CI/CD pipelines, SCM, cloud platforms, security tools, and runtime environments |
| **Data Normalization**         | Converts heterogeneous data formats from 100+ tools into a consistent, structured representation               |
| **Signal Enrichment**          | Adds environment, team, service, and risk metadata to every ingested event                                     |
| **Cross-System Correlation**   | Links events across tools and timelines — deployment events to code changes, findings to pipeline executions   |
| **Lifecycle Context Building** | Forms a complete picture of each change — from code commit through build, test, deploy, and runtime outcome    |
| **Continuous Ingestion**       | Processes data in real time as events occur — not in periodic batch runs — ensuring context is always current  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/context-engine/context-formation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.