# CORES Packages

A CORE(s) package is a series of instructions bundled in a way that allows each node within the network to receive just enough information to make a decision on how to handle a request. CORES stands for **C**lient-**O**rigin-**R**elay-**E**xit-**S**erver

CORE(s) packages contain layers of requests that inform nodes how to perform one of three actions.

1. Create the request
2. Pass the request along
3. Process the request.

Each Node that handles a CORES package plays a specific role in the life-cycle of the package route:

* **Client:** This is the device that is initializing the request such as a browser, or a video game.
* **Originator:** The identity of the originating request node.
* **Relay:** Identifies Nodes that will be used to hop along routes to get to its destination.
* **Exit:** The exit node will make the true web request on behalf of the originator and send it back along the route stack.
* **Server:** Information about the server that is hosting the requested information.


---

# Agent Instructions: 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:

```
GET https://docs.masqbrowser.com/masq/core-concepts/cores-packages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.