> 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/references/reference-g-unified-asset-inventory-fields-and-deep-links.md).

# Reference G: Unified Asset Inventory fields and deep links

Reference Unified Asset Inventory fields and deep links for Code-to-Cloud.

This appendix documents the two Code-to-Cloud fields recorded on every code-side and cloud-side asset in the Unified Asset Inventory (UAI), used both by the dashboard's Traced/Untraced counts and as filters within the UAI tables.

| Field name     | Direction | Possible values                      | Meaning                                                                                                                                                        |
| -------------- | --------- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Code-2-Cloud` | Forward   | `CODE`, `BUILD`, `DEPLOY`, `RUNTIME` | The furthest forward stage the asset's lineage reaches. `CODE` means no forward trace was established; `RUNTIME` means the lineage reaches a runtime workload. |
| `Cloud-2-Code` | Backward  | `CODE`, `BUILD`, `DEPLOY`, `RUNTIME` | The furthest backward stage the asset's lineage reaches. `CODE` means the lineage reaches a repository; `RUNTIME` means no backward trace was established.     |

## Examples

| UAI asset type           | Field          | Value     | Meaning                                                                         |
| ------------------------ | -------------- | --------- | ------------------------------------------------------------------------------- |
| Onboarded VCS Repository | `Code-2-Cloud` | `CODE`    | The repository could not be traced to any pipeline, registry, or runtime asset. |
| CI/CD Pipeline           | `Code-2-Cloud` | `RUNTIME` | The pipeline's lineage reaches a runtime workload.                              |
| Runtime Container Image  | `Cloud-2-Code` | `BUILD`   | The runtime image was traced back to a CI/CD pipeline but not to a repository.  |
| IaC Resource             | `Code-2-Cloud` | `RUNTIME` | The IaC resource has a YOR tag and matches a deployed cloud asset.              |

> **Note:** A `NULL` value for either field indicates that lineage has not yet been calculated for the asset (for example, the asset was recently onboarded). The dashboard treats `NULL` as untraced for the per-stage map.

## Cross-page deep links

Every map element in the Coverage dashboard links to the corresponding UAI page with the C-2-C field filter pre-applied, and inherits the dashboard's active page-level filters (Application, Provider, Organization). For example, in the Code-2-Cloud Artifact view, selecting the Code-stage untraced area links to the VCS Repository page filtered to `Code-2-Cloud = CODE`; selecting the Runtime-stage traced area links to the same page filtered to `Code-2-Cloud = RUNTIME`. The per-provider tooltip on each color area appends a `provider = <hovered provider>` filter to the link target.


---

# 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/references/reference-g-unified-asset-inventory-fields-and-deep-links.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.