Reference A: Lineage filtering matrix

Before applying filters, ensure you use the correct Class filter. Use this matrix to isolate assets at specific trace stages.

Operational goal	Target class	Operator	Values to select	Value logic	What this reveals
Code assets with no forward trace (untraced)	Code	Not Contains	Build, Deploy, Runtime	OR	Code assets whose lineage stops at the code level. These assets are candidates for onboarding.
Code assets traced beyond code (traced)	Code	Contains	Build, Deploy, Runtime	OR	Code assets traced to build, deployment, or runtime.
Code assets stopping at build	Code	Contains	Build	—	Code assets traced to build pipelines, but no further.
Code assets stopping at deploy	Code	Contains	Deploy	—	Code assets traced to registries or deployments, but not runtime.
Code assets traced to production (fully traced)	Code	Contains	Runtime	—	Code assets with verified end-to-end Code-to-Cloud lineage.
Workloads with no backward trace (untraced)	Compute	Not Contains	Build, Code, Deploy	OR	Active cloud workloads with no backward lineage.
Workloads traced beyond runtime (traced)	Compute	Contains	Build, Code, Deploy	OR	Workloads traced to a deployment registry, pipeline, or repository.
Workloads stopping at deploy	Compute	Contains	Deploy	—	Workloads traced to a container image, but not a pipeline or repository.
Workloads stopping at build	Compute	Contains	Build	—	Workloads traced to a build pipeline, but not source code.
Workloads traced to source code (fully traced)	Compute	Contains	Code	—	Workloads traced back to their originating VCS repositories.