> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/code-to-cloud/code-to-cloud/c2c-in-unified-asset-inventory/reference-c-technical-background.md).

# Reference C: Technical background

These details explain how the system calculates lineage and how the inventory interacts with other dashboards.

## Core concept: The single bidirectional field

The Unified Asset Inventory stores software lineage in one bidirectional field: **Development Cycle Stages**.

* The field records the furthest stage that an asset’s lineage reached.
* The **Class** filter determines the trace direction automatically.
* The inventory traces from code or build toward runtime for the **Code** class.
* The inventory traces from runtime or deploy toward code for the **Compute** class.

## The four stages and dropdown behavior

The **Development Lifecycles** filter contains four chronological lifecycle stages: **Code → Build → Deploy → Runtime**.

* **Code**: Source code repositories.
* **Build**: Build pipelines and CI/CD runs.
* **Deploy**: Container registries, deployment packages, and IaC definitions.
* **Runtime**: Running compute workloads in production.

{% hint style="warning" %}
The filter dropdown lists values alphabetically: **Build**, **Code**, **Deploy**, and **Runtime**. This order does not show lineage progression.
{% endhint %}

## Troubleshoot empty tables

Check these causes in order:

1. **Value logic uses AND.** Join multiple filter criteria with **OR**.
2. **The tracing job has not run.** Recently onboarded assets have an empty (`NULL`) lineage stage. A **Not Contains** filter cannot match them before analysis.
3. **The table context is incorrect.** Confirm that your filter matches the asset class. For example, **Contains Code** on a Code table does not show forward tracing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/code-to-cloud/code-to-cloud/c2c-in-unified-asset-inventory/reference-c-technical-background.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.