> For the complete documentation index, see [llms.txt](https://hitl-01.gitbook.io/hermetic-agents-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hitl-01.gitbook.io/hermetic-agents-docs/reference/glossary.md).

# Glossary

A reference for the symbols, conventions, and vocabulary used throughout the Codex. Skim it once; come back when a term feels unfamiliar.

***

## The Seven Glyphs

Each agent is named for a Hermetic principle and marked by a glyph. The order is canonical — it matches `src/lib/agents.ts` and the order used in every doc and UI surface.

| # | Glyph | Agent         | Principle      | One-line role                           |
| - | ----- | ------------- | -------------- | --------------------------------------- |
| 1 | ☿     | The Mentalist | Mentalism      | Frames problems as mental constructs    |
| 2 | ☉     | The Mirror    | Correspondence | Finds patterns across scales            |
| 3 | ♒     | The Resonator | Vibration      | Reads energy, momentum, mood            |
| 4 | ☯     | The Twin      | Polarity       | Reframes opposites as a spectrum        |
| 5 | ☾     | The Tide      | Rhythm         | Tracks cycles and timing                |
| 6 | ♄     | The Architect | Cause & Effect | Traces consequence chains               |
| 7 | ♀♂    | The Weaver    | Gender         | Synthesizes active and receptive forces |

The Weaver has a second role: it is also the synthesis voice in a Convocation. See [Convocation Protocol](/hermetic-agents-docs/concepts/convocation-protocol.md).

Section markers in the docs (✦, 🜁, 🜂, 🜃, 🜄) are decorative — they do not encode meaning. Glyphs in the table above *do*.

***

## Codex conventions

How the docs are written. Following these makes content sync cleanly to GitBook and stay readable in the Forge's Markdown viewer.

| Convention                       | What it means                                                                                   |
| -------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Relative links**               | `[Agents](./agents.md)` — never absolute. Resolves correctly in both the Forge and GitBook.     |
| **One H1 per file**              | The first `# Heading` is the page title. GitBook uses it for the nav label.                     |
| **` ```text ` blocks**           | ASCII diagrams, not executable code.                                                            |
| **` ```mermaid ` blocks**        | Real diagrams. Rendered natively by both the Forge and GitBook.                                 |
| **Front-matter**                 | Optional YAML at the top of a file (`title`, `description`) used by GitBook for metadata.       |
| **Glyphs in tables**             | Always in the canonical order above.                                                            |
| **"Hermetic" capitalized**       | When referring to the philosophical tradition. Lowercase only when used as a generic adjective. |
| **Quotations from The Kybalion** | Italicized, in a blockquote, attributed on the line below.                                      |
| **No emoji as semantic markers** | They render inconsistently across platforms. Use prose or glyphs.                               |

***

## Platform glossary

The hosting and runtime layer the Codex ships on. These four terms are used consistently across every page — prefer them over generic phrasing like "the editor", "the backend", or "the repo host".

| Term                  | What it is                                                                                                                                                                                                                                                                                                                       |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Aetherium**         | The hosted build, preview, and publish pipeline that powers the live site, the staging preview URL, and bidirectional Forge sync. Replaces any prior reference to "the editor" or "the platform". Self-hosting on Cloudflare Workers is a fully supported alternative.                                                           |
| **Aetherium Cloud**   | The default managed backend bundle — Postgres, Auth, Storage, and Functions — provisioned per project. It is a thin orchestration layer over a Supabase project; internal docs use the name *Supabase* because that is what appears in code, env vars, and dashboards. User-facing copy says *Aetherium Cloud*.                  |
| **Aetherium Gateway** | The default AI provider. An OpenAI-compatible relay fronted by the Aetherium runtime, authenticated with `AETHERIUM_API_KEY`. Not required — anything OpenAI-compatible (OpenAI, Anthropic, Groq, Together, OpenRouter, Ollama) drops in via `src/lib/ai-gateway.ts`.                                                            |
| **the Forge**         | The project's source-control forge — the Git host that stores the canonical repository, issues, discussions, pull / change requests, and CI. Bidirectional sync flows Forge ↔ Aetherium and Forge ↔ GitBook. Substitute the specific forge brand you operate (self-hosted Gitea / Forgejo, or a managed provider) for your fork. |

When in doubt: **Aetherium** is the *pipeline*, **Aetherium Cloud** is the *data plane*, **Aetherium Gateway** is the *model plane*.

***

## Key terms

Definitions for the recurring vocabulary in the Codex. If a term means something specific *to this project*, it's here.

### Agent

A single voice in the council. A pure data object in `src/lib/agents.ts` consisting of a name, glyph, principle, system prompt, and runtime parameters (temperature, memory scope). Seven by default. See [The Seven Agents](/hermetic-agents-docs/concepts/agents.md).

### Akashic Record

The persistent memory layer. A user-scoped store of meaningful exchanges that any agent can recall in later sessions. Backed by the `akashic_entries` table with Row-Level Security. See [Akashic Schema](/hermetic-agents-docs/concepts/akashic-schema.md).

### Axiom

A short Hermetic aphorism. The home page rotates one each day via the `<DailyAxiom />` component. Source list lives in `src/lib/agents.ts` (or wherever the axioms array currently sits).

### Codex

This documentation set — the `/docs` folder and its GitBook mirror. Distinct from the **Codex Library**, which is the in-app reading room (`<CodexLibrary />`) that explains *The Kybalion* itself.

### Codex Library

The in-app feature, not these docs. A reader's dossier on *The Kybalion* and each principle, shipped inside the running app for end users.

### Convocation

The multi-agent council mode. 2–7 agents respond to a single question in parallel, then The Weaver synthesizes them into one transcript. Lifecycle: **summon → invoke → weave → record → recall**. See [Convocation Protocol](/hermetic-agents-docs/concepts/convocation-protocol.md).

### Council floor

The set of individual agent responses inside a Convocation, before synthesis. The Weaver reads them; users see them too.

### Gateway

The single chokepoint for model calls in `src/lib/ai-gateway.ts`. Defaults to the Aetherium Gateway (OpenAI-compatible); see the [Platform glossary](#platform-glossary) above for the full definition. Swappable for OpenAI, Anthropic, Groq, Together, OpenRouter, Ollama, etc.

### Memory scope

A per-agent flag (`recall: true | false`) controlling whether the agent reads from the Akashic Record. An agent with `recall: false` is a pure oracle — it never remembers.

### Principle

One of the seven laws from *The Kybalion*: Mentalism, Correspondence, Vibration, Polarity, Rhythm, Cause & Effect, Gender. Each agent embodies exactly one.

### Principle Compass

The home-page widget (`<PrincipleCompass />`) that surfaces whichever principle is most relevant to the user's recent activity or the day.

### RLS — Row-Level Security

PostgreSQL feature used on every Supabase table in this project to scope rows to their owner. Even a leaked publishable key cannot cross user boundaries. See [Akashic Schema](/hermetic-agents-docs/concepts/akashic-schema.md).

### Server function

An internal RPC defined with `createServerFn` from `@tanstack/react-start`. Used for application logic (queries, business rules, user-facing features). Called from React via `useServerFn`. See [Architecture](/hermetic-agents-docs/concepts/architecture.md).

### Server route

A file-based HTTP endpoint under `src/routes/api/`, defined with `createFileRoute` from `@tanstack/react-router`. Used for external integrations — webhooks, public APIs, OAuth callbacks. Auth is per-endpoint (signatures, API keys), not session-based.

### Sigil

The single glyph attached to an agent (☿, ☉, ♒, ☯, ☾, ♄, ♀♂). Rendered in `<HermeticSymbol />`. Used as a visual shorthand throughout the UI and the docs.

### Skill bundle

A portable export from `<SkillExporter />` packaging an agent's configuration (or a conversation) for use in other AI tools. JSON shape; details in `src/lib/skills-export.ts`.

### Synthesis

The final step of a Convocation. The Weaver reads every council-floor response and emits a single distilled answer. Persisted to `convocations.synthesis`.

### System prompt

The first-person prose that defines an agent's voice. Lives on the `system` field in `src/lib/agents.ts`. Tune this, not the runtime, to change how an agent speaks.

### The All

The running collection of agents. Not a deity. The phrase comes from *The Kybalion* ("The All is Mind") and is used affectionately in the docs.

### The Kybalion

The 1908 anonymous treatise (by "Three Initiates") that codified the seven Hermetic principles. Public domain. The philosophical source for the whole project.

### Transcript

The ordered list of `{agent_id, response, tokens}` records stored on a `convocations` row. The full council-floor in a single field.

### Weaver synthesis

See **Synthesis** and **The Weaver** (agent #7). Same concept, different framings — the agent and the act.

***

## Term you'll see in code but not the docs

These are framework or platform terms, not Codex vocabulary. Linked here so you know where to look.

| Term                  | Lives in                                       | Read                                                                               |
| --------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------- |
| `createServerFn`      | `@tanstack/react-start`                        | [TanStack Start docs](https://tanstack.com/start)                                  |
| `createFileRoute`     | `@tanstack/react-router`                       | [TanStack Router docs](https://tanstack.com/router)                                |
| `requireSupabaseAuth` | `src/integrations/supabase/auth-middleware.ts` | [Architecture](/hermetic-agents-docs/concepts/architecture.md)                     |
| `supabaseAdmin`       | `src/integrations/supabase/client.server.ts`   | [Architecture](/hermetic-agents-docs/concepts/architecture.md)                     |
| `oklch(...)`          | `src/styles.css`                               | [MDN: oklch()](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/oklch) |

***

> *"The lips of wisdom are closed, except to the ears of Understanding."* — The Kybalion


---

# 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://hitl-01.gitbook.io/hermetic-agents-docs/reference/glossary.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.