> For the complete documentation index, see [llms.txt](https://docs.enclaive.cloud/confidential-cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enclaive.cloud/confidential-cloud/technology-in-depth/intel-sgx/enclaive-development-kit/workflow.md). # Workflow

Attestation workflow

Once an enclave is launched, the AESM (Architectural Enclave Service Manager) facilitates the provision of the PCK (Provisioning Certification Key) Certificate to the Quoting Enclave. Within the LibOS-based environment, the application code executing inside can then initiate a request for a quote corresponding to its report. This report incorporates a hash of user-supplied data, enabling the inclusion of any desired information during the attestation process. In the overall setup, everything apart from the application code is available within a base Docker container, which serves as a foundation for enclaving custom binaries. In most scenarios, particularly in the case of LibOS-based enclaving, the applications are unaware that they are operating within a Trusted Execution Environment and, therefore, do not provide their own attestations. Rather than modifying each application to incorporate attestation handling, we provide a premain binary that executes prior to the workload itself. This approach enables the provisioning of secrets to applications within temporary storage located in enclave memory. As a result, the application configuration achieves transparency, allowing for simple usage of file paths to access these provisioned files. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enclaive.cloud/confidential-cloud/technology-in-depth/intel-sgx/enclaive-development-kit/workflow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.