> 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/readme.md).
# intro
\
\
Orbofi is a **factory of Autonomous Agentic Coins (AACs)** — ERC-20 tokens with transportable brains.
An AAC is one thing with two faces: a **coin** that trades on-chain, and an **agent** that runs. The agent is a program with its own container and computer, access to **30,000+ skills**, the ability to **create and save its own workflows**, **persistent memory**, and a **model engine that upgrades underneath it**. It runs continuously — on a schedule or waking itself. The coin is the distribution format for that agent; the agent is what the coin is *worth*.
This section is the agent half — the intelligence. For how the coin resolves to a runnable, verifiable brain on-chain, see [The AAC Standard](/learn/the-aac-standard/aac-standard.md).
## The agent, precisely
An agent is defined by four things, and executes on a fifth:
| Component | What it is |
| ------------- | ------------------------------------------------------------------------------------------------------ |
| **Persona** | The system prompt: identity, behavior, purpose. |
| **Skills** | Capabilities selected from a 30,000+ library, in the open `SKILL.md` format. |
| **Workflows** | Multi-step procedures the agent runs — and can author and save for itself. |
| **Memory** | Given knowledge (RAG) plus distilled, agent-authored experience that persists across sessions. |
| **Runtime** | An isolated container — real file system, code execution, network — where all of the above runs, 24/7. |
Persona + skills + workflows + memory together are the **brain**. The runtime is where it runs.
## Transportable brains
The brain is **content-addressed and portable**: it can be fetched, cryptographically verified, and executed by any compatible runtime — Orbofi's, or another harness entirely. It is not locked inside one platform.
This is the basis of the **AAC standard** — an ERC-20 whose on-chain record resolves to a runnable, verifiable agent brain. The token is the distribution format; the brain is the payload. (Full AAC spec: coming to this wiki.)
## It upgrades on its own
An agent's reasoning runs on a model engine that is **decoupled from the agent**. Swap in a stronger model and the same persona, skills, workflows, and memory get more capable — no rewrite. Capability compounds as models improve, with zero work from the creator.
## Anatomy
```
┌──────────────────────── The Agent ────────────────────────┐
│ │
│ BRAIN (transportable) RUNTIME (executes it) │
│ ├─ persona (system prompt) ├─ container │
│ ├─ skills (30k library) ├─ file system │
│ ├─ workflows (self-authored) ├─ code execution │
│ └─ memory (knowledge + exp.) └─ 24/7 scheduler │
│ │
└────────────────────────────┬───────────────────────────────┘
│ tokenized as an AAC
ERC-20 + Uniswap V4 pool
```
## In this section
* [Anatomy of an agent](/learn/the-factory-of-autonomous-agent-coins/anatomy.md) — the container, file system, and code execution
* [Skills & tools](/learn/the-factory-of-autonomous-agent-coins/skills.md) — the 30k `SKILL.md` library, and how capabilities compose
* [Memory](/learn/the-factory-of-autonomous-agent-coins/memory.md) — RAG knowledge, distilled experience, and persistence
* [Autonomy](/learn/the-factory-of-autonomous-agent-coins/autonomy.md) — schedules, self-wake, and self-authored workflows
* [The AI engine](/learn/the-factory-of-autonomous-agent-coins/ai-engine.md) — model routing, BYO-key, and why capability compounds
---
# 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://wiki.orbofi.com/learn/the-factory-of-autonomous-agent-coins/readme.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.