This document explains how components relate to jobs, processes, and threads.
There is no inherent relationship between component instances and a Zircon task (job, process, or thread). It's best to avoid a mental model with a fixed relationship between components and Zircon tasks.
There's no inherent relationship between Zircon tasks and components.
Note: Compare with section Dynamic relationships.
To illustrate that there is no inherent relationship, consider that a component may:
Different components are expressed, or implemented, differently (even in ways we haven't yet explored).
The way components and Zircon tasks relate is dynamic. On initial inspection it may appear that there is a hierarchy, but there is no hierarchy between components and processes.
Here are some examples of specific component types to illustrate the nature of the component abstraction: