why workers generate input for temporal ?

Airbyte uses Temporal for orchestration, which helps in managing and scaling hundreds to thousands of jobs simultaneously. The workers in Airbyte interact with connectors and run as jobs. Each job has a corresponding worker, such as Spec worker, Check connection worker, Discovery worker, and Sync worker. These workers handle the process lifecycle for job-related processes, facilitate message passing to or from various processes, and handle job-related operational work. The workers generate input for Temporal as they are responsible for handling the process lifecycle for job-related processes, including starting, monitoring, and shutting down processes. They also facilitate message passing to or from various processes, if required. This is crucial for Temporal's orchestration as it allows for the serializing of the jobs' current runtime memory into a database, making it easy to recover from failures and determine if a job was assigned correctly. It's important to note that there are two types of workers in Airbyte: Synchronous Job Worker and Asynchronous Job Worker. Synchronous Job Workers interact with a single connector and are part of the configuration process, while Asynchronous Job Workers interact with two connectors and are often long-running resource-intensive processes. For more information, you can refer to the [Airbyte Documentation](https://docs.airbyte.com/understanding-airbyte/jobs) and [Airbyte Technical Stack](https://docs.airbyte.com/understanding-airbyte/tech-stack).