> For the complete documentation index, see [llms.txt](https://emeth-1.gitbook.io/emeth-white-paper-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emeth-1.gitbook.io/emeth-white-paper-en/7.-emeth-architecture/7-1.-overview/7-1-2.-aggregator.md).

# 7-1-2. Aggregator

The Aggregator plays a crucial role in integrating distributed (confidentially encrypted) processing results. The following are the main roles and process flow of the Aggregator:

1. Integration of SubJob results and generation of final results The Aggregator receives the results of processed SubJobs and applies unique integration processing logic corresponding to the ProgramId to consolidate them. This integration process combines the processing results obtained from each SubJob to generate the overall final processing result. This maintains the consistency of the distributed processing process and enables efficient processing.

The Aggregator plays an essential role in the distributed processing process. By appropriately integrating the processing results obtained from each SubJob, it ensures quality and consistency. Additionally, since the Aggregator also handles processing results in a confidentially encrypted state, it protects data privacy and security.


---

# 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://emeth-1.gitbook.io/emeth-white-paper-en/7.-emeth-architecture/7-1.-overview/7-1-2.-aggregator.md?ask=<question>&goal=<endgoal>
```

`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.
