> For the complete documentation index, see [llms.txt](https://docs.earthbuild.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthbuild.dev/docs/misc/definitions.md).

# Definitions

This page presents some common terms used throughout the EarthBuild documentation. Understanding these terms will help you understand how to use `earth`.

* **EarthBuild** - the build automation system as a whole
* **`earth`** - the CLI tool used to interact with EarthBuild
* **Earthfile** - a file (named literally `Earthfile`) which contains a series of targets and their respective recipes
* **buildkitd** - a [daemon built by the Docker team](https://github.com/moby/buildkit) and used by EarthBuild to execute builds. It executes LLB, the same low-level primitives used when building Dockerfiles. The buildkitd daemon is started automatically in a docker container, by `earth`, when executing builds.
* **recipe** - a specific series of build steps
* **target** - the label used to identify a recipe. 'Target' is also used to refer to a build of a specific target.
* **build context** - the main directory made available to the build for copying files from
* **artifact** - a file resulting from executing a target (not all targets have artifacts)
* **image** - a docker image resulting from executing a target (not all targets have images)

## See also

* The [Earthfile reference](https://docs.earthbuild.dev/docs/earthfile.md)
* The [earth command reference](https://docs.earthbuild.dev/docs/earth-command.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.earthbuild.dev/docs/misc/definitions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
