# Naming glossary

*Owner ruling 2026-09-02. Written in Phase 0 of the naming shift and **final since Phase 4
(2026-09-02)**: the four names below are what the code, the documents and the memory say. This
file is the single source for what each name means; every later document links here instead of
redefining a term. What remains of the shift is owner-run infrastructure (Phase L, Phase D), kept
in `apollo-naming-shift-prompt-260902.md`.*

## The four names

| Name | Means | What the code says (after Phases 1 and 3, 2026-09-02) |
|---|---|---|
| **Argus** | The financial-documents module inside the platform: the FDR schema as an EF model, the Documents / Processing / Quality / Audit / Integration / Reconciliation / Management / Administration screens, the engines (review, flags, ERP push, settlement, matching, master data, catalogues), the FDR sync and the document worker's module side. | `Sibyla.Modules.Argus.*`, `ArgusDbContext`, routes `/argus/*` (old `/sibyla/*` links redirect), module key `argus`, `tests/Sibyla.Tests.Argus`, display name "Argus". Before Phase 1 it said `Apollo.Modules.Sibyla.*`, `/sibyla/*`, key `sibyla`. |
| **Sibyla** | The platform: this repository, the multi-tenant Blazor host, tenancy and licences, the AI Projects area, ingestion, the module seam, and the channel-intake API when it is built. The product a licence holder logs into. | `Sibyla.Platform.*`, `Sibyla.Web`, `Sibyla.Sync`, `Sibyla.Worker.Documents`, `SibylaDbContext`, `SibylaModuleDescriptor`, brand "Sibyla", cookie `sibyla.auth`, config key `ConnectionStrings:SibylaDb`, env `SIBYLA_DB`, hostnames `sibyla.gottsolutions.net` / `api.sibyla.gottsolutions.net`. Before Phase 3 it said `Apollo.*`, `apollo.auth`, `ApolloDb`. |
| **Sibyla Legacy** | The retired stack: `Sibyla.Web`, `Sibyla.Api`, `Sibyla.Worker`, the dashboard and the other applications under `C:\SibylaApps`, the database `gott_sibyla`, the IIS sites `sibyla.gottsolutions.net`, `api.sibyla.gottsolutions.net`, `docs.sibyla.gottsolutions.net`, the Hermes plugin `sibyla-channel-intake` and the cron `sibyla-email-graph-gateway`. Frozen at the cutover; never extended. | Written as plain "Sibyla" in older docs and memory. |
| **Apollo** | GOTT's gateway agent: the Hermes Agent instance that reads email, WhatsApp, Telegram and the other channels, files what it receives into Sibyla through the channel-intake plugin, and answers questions with licence data read from the database under the read-only role. | The AI project `apollo` ("Apollo", harness HERMES), the plugin `apollo-channel-intake`, the cron `apollo-email-gateway` (when created), the role `apollo_ai_reader`. The runtime it runs on is still written "Hermes" (ruling N8): the harness selector says Hermes, the agent says Apollo. |

## Names that do not change

| Name | Why it stays |
|---|---|
| **FDR** and `Interface/sibyla-registry-web`, the workbook, the stamps "Build 060200 @ 56126f8" | External authority; the FDR names its own things. |
| **Hermes Agent** (the runtime, `AppData\Local\hermes\hermes-agent`, harness key `HERMES`, `HarnessCliOptions.Hermes`) | Product name of the CLI. Apollo is the instance, Hermes is what runs it. |
| **Medusa**, **Calypso** | Other modules; unaffected. |
| `sib-*` CSS classes and the `Sib*` shared components | The prefix was always the platform's, and after the shift it reads as Sibyla. |
| Applied migration ids (`20260828003014_SibylaWave1MasterData`, …) and the history table `__EFMigrationsHistory_Sibyla` | Applied history is never rewritten. Migrations created after Phase 1 use the `Argus` prefix in their class and file names. |
| Provenance sentences already stored in rows ("… (Apollo association form)", "Raised by Apollo capture …") | History. Rows written after Phase 3 use the new names. |
| PostgreSQL databases `gott_sibyla`, `gott_sibyla_preview` and roles `sibyla_app`, `sibyla_migrator`, `sibyla_worker`, `sibyla_api`, `sibyla_preview_*`, `apollo_ai_reader`; IdP clients `apollo-web`, `apollo-worker` and scope `apollo-api`; repo folder `GOTT.Sibyla`; GitLab project `GOTT.Sibyla` | Infrastructure identifiers. They change only by the owner's hand, per decisions N1 and N3 in the prompt document. Ruled 2026-09-02 that the databases and roles would be renamed last (Phase D); **renamed 2026-09-03 on the owner's word, ahead of the legacy decommissioning** (`gott_apollo` → `gott_sibyla`, the legacy database moved aside as `gott_sibyla_legacy`, `apollo_*` roles → `sibyla_*`; record in `apollo-naming-shift-phase-d-260903.md`); The folder and the GitLab project were **renamed 2026-09-08, superseding N3** (`GOTT.Apollo` -> `GOTT.Sibyla`; the legacy project archived as `gott-sibyla-legacy`, its source under `legacy/`; record in `repo-rename-260908.md`). `apollo_ai_reader` reads correctly after the shift: it is the agent's role. |
| Apollo's plugin `apollo-channel-intake` (a Hermes-runtime plugin) | Ruled 2026-09-02 (N4): it is Apollo's, the agent's, plugin into Sibyla, so the name is right. The API it posts to is Sibyla's: contract `sibyla.channel-intake.v1`, host `src/Sibyla.Api` at `api.sibyla.gottsolutions.net`, scope `sibyla.channel-intake.write`, IdP client `sibyla-channel-intake`. |

## Names that change by ruling of 2026-09-02

| Name | Becomes | When |
|---|---|---|
| Legacy hostnames `sibyla.gottsolutions.net`, `api.sibyla.gottsolutions.net` | `legacy.gottsolutions.net`, `api.legacy.gottsolutions.net` (N2) | Owner-run, before the platform's production deployment (Phase L); the Hermes plugin is repointed first. |
| Platform hostnames (planned `apollo.gottsolutions.net`, `api.apollo.gottsolutions.net`) | `sibyla.gottsolutions.net`, `api.sibyla.gottsolutions.net` (N2) | Written in Phase 3; live once Phase L has freed the names. |
| Cookie `apollo.auth`, config key `ConnectionStrings:ApolloDb` | `sibyla.auth`, `ConnectionStrings:SibylaDb` (N5) | Phase 3. |

## Public hostnames since 2026-09-10 (owner instruction, `sibyla.pt`)

The public names above were superseded on 2026-09-10 by the `sibyla.pt` domain; the old names answer
with permanent redirects. Run record: `docs/sibyla-pt-hostname-cutover-260910.md`.

| Service | Hostname | Replaced |
|---|---|---|
| Sibyla (web) | `app.sibyla.pt` | `sibyla.gottsolutions.net` |
| Channel-intake API | `api.sibyla.pt` | `api.sibyla.gottsolutions.net` |
| Documentation | `docs.sibyla.pt` | `docs.sibyla.gottsolutions.net` |
| GOTT.IdentityServer (issuer) | `login.sibyla.pt` | `login.gottsolutions.net` |
| Nextcloud | `nextcloud.sibyla.pt` | `nextcloud.gottsolutions.net` |
| Hermes dashboard (Apollo) | `dashboard.sibyla.pt` | `dashboard.gottsolutions.net` |
| Buzz relay | `buzz.sibyla.pt` | `buzz.gottsolutions.net` |
| Postiz | `postiz.sibyla.pt` | `postiz.gottsolutions.net` |

IIS site and application-pool names did not change (`Sibyla.Web`, `Sibyla.Api`, `Sibyla.Docs`,
`login.gottsolutions.net`, …); mailboxes stay under `gottsolutions.net`.

## Forbidden usages after the shift

- "Sibyla" alone never means the legacy stack. Say "Sibyla Legacy" or the concrete identifier (`gott_sibyla`, `Sibyla.Api`).
- "Sibyla" alone never means the module. The module is Argus.
- "Apollo" alone never means the platform. The platform is Sibyla.
- "Hermes" alone never means GOTT's agent. The agent is Apollo; Hermes is the runtime it runs on.
- A sentence a user reads (label, notice, refusal, provenance) uses the product names. A sentence an operator reads (script output, connection guard, checklist) may use the infrastructure identifiers, and says which one it means.

## Already aligned with the ruling

The AI Projects seed (`20260901132338_AiProjects`) anticipated the ruling: project `apollo`, "Licence-scoped Gateway and database analysis", runs on the Hermes harness, and project `sibyla`, "Development of the GOTT.Sibyla repository", runs on Codex. Those two rows already carry the final names of the agent and the platform.