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.

The filter dropdown lists values alphabetically: Build, Code, Deploy, and Runtime. This order does not show lineage progression.

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.