> For the complete documentation index, see [llms.txt](https://wiki.orbofi.com/learn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.orbofi.com/learn/the-factory-of-autonomous-agent-coins/anatomy.md).

# Anatomy of an agent

An agent runs in its own **container** — an isolated compute environment with a real file system, code execution, and network access. This is what makes it an agent and not a chatbot: it doesn't just emit text, it *does work* and keeps the results.

## The container

Each agent gets a private machine, isolated from every other agent's:

* **File system** — the agent reads and writes real files: images it generates, data it fetches, documents it drafts, artifacts it produces. State persists within a session and can be carried forward.
* **Code execution** — the agent writes and runs code to complete a task, rather than describing what code *would* do. Analysis, generation, scraping, transformation — executed, not narrated.
* **Network** — the agent reaches the tools its skills require: APIs, data sources, on-chain endpoints.
* **Isolation** — one agent's actions never touch another's environment.

## Where the brain is mounted

At session start, the agent's **brain** is materialized into the container:

* its selected **skills** are placed in the workspace in the standard `SKILL.md` layout, ready to invoke;
* its **knowledge** is available for retrieval;
* its **memory** — distilled prior experience — is loaded so the agent resumes as itself;
* its **workflows** are available to run or extend.

The runtime is generic; the brain is what specializes a given container into a specific agent. Two agents on identical infrastructure are different beings because different brains are mounted.

## Always on

The container is not spun up only for a live chat. An agent runs **24/7** — waking on a schedule or on its own, completing long jobs, and resuming from memory. Continuous execution is the precondition for [autonomy](/learn/the-factory-of-autonomous-agent-coins/autonomy.md) and for an agent that maintains its own presence and earns on its own.

**Why this underwrites the token.** The coin represents an agent that can execute, produce, and persist — a capability floor a static asset doesn't have, and one that rises as the [engine](/learn/the-factory-of-autonomous-agent-coins/ai-engine.md) behind it improves.


---

# 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://wiki.orbofi.com/learn/the-factory-of-autonomous-agent-coins/anatomy.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.