7.0 KiB
Thoth Gateway Infrastructure — Project State
Version: 0.0.1 Status: Active Last Updated: 2026-07-28
Current Focus
Gateway Base Commissioning
The current objective is to establish thoth-gateway as a stable, reproducible, and documented container host for Project Thoth services.
The immediate commissioning path is:
- Complete the Gateway base configuration.
- Establish the infrastructure repository and project self-description.
- Install and validate Docker Engine and Docker Compose.
- Deploy Open WebUI.
- Connect Open WebUI to Oracle.
- Verify Gemma 4 inference end to end.
System Role
thoth-gateway is the orchestration and service-interface host for the Project Thoth environment.
Gateway responsibilities include:
- Hosting containerized services.
- Providing user-facing service interfaces.
- Coordinating agentic workflows.
- Providing retrieval and integration services.
- Routing approved inference requests to local or frontier AI providers.
- Connecting Project Thoth consumers to the knowledge repository.
Gateway is not the primary local inference host.
Local model execution is assigned to thoth-oracle.
Current Environment
Gateway
| Property | Value |
|---|---|
| Hostname | thoth-gateway |
| Operating System | Pop!_OS |
| Primary User | kschaefer |
| Role | Container orchestration and service host |
| Infrastructure Root | /srv/thoth |
| Infrastructure Repository | /srv/thoth/containers |
Oracle
| Property | Value |
|---|---|
| Hostname | thoth-oracle |
| Address | 192.168.5.52 |
| Ollama Endpoint | http://192.168.5.52:11434 |
| Role | Local model runtime and GPU inference |
| Initial Target Model | gemma4:e4b |
Completed
- Rebuilt Gateway operating system.
- Assigned the
thoth-gatewayhostname. - Established base network connectivity.
- Confirmed Gateway can reach the local network.
- Installed Docker Engine.
- Installed the Docker Compose plugin.
- Added
kschaeferto thedockergroup. - Selected
compose.yamlas the canonical Compose filename. - Selected
/srv/thoth/containersas the Git-managed infrastructure repository. - Selected
/srv/thoth/dataas the root for mutable service data. - Adopted the Project Thoth
.thothself-description structure for the infrastructure repository.
In Progress
- Activate non-root Docker access for the current login session.
- Verify Docker operation with the
hello-worldcontainer. - Create the
/srv/thothdirectory structure. - Initialize the infrastructure Git repository.
- Populate the
.thothproject self-description. - Establish the initial repository documentation.
- Create the Open WebUI service project.
- Create the Open WebUI
compose.yaml. - Configure Open WebUI to use Oracle as its Ollama endpoint.
- Start Open WebUI and validate container health.
Blocked
No known architectural blockers.
Current Operational Issue
The current shell session does not yet have effective membership in the docker group.
Observed error:
permission denied while trying to connect to the docker API at unix:///var/run/docker.sock
Expected resolution:
- Start a new login session, or
- Run
newgrp docker.
The Docker socket permissions must not be weakened as a workaround.
Next Milestone
Gateway-to-Oracle Gemma 4 Verification
The next milestone is complete when a user can submit a prompt through Open WebUI on Gateway and receive a response generated by gemma4:e4b on Oracle.
The verified request path must be:
User Browser
↓
Open WebUI on Gateway
↓
Ollama API on Oracle
↓
Gemma 4
↓
Open WebUI
↓
User Browser
Milestone Acceptance Criteria
- Gateway survives reboot with its expected hostname and network configuration.
- Docker starts automatically.
kschaefercan run Docker commands withoutsudo.docker run --rm hello-worldcompletes successfully.- The infrastructure repository exists at
/srv/thoth/containers. - Runtime data is stored outside the Git repository.
- The repository contains a complete
.thothself-description. - Open WebUI starts through
docker compose. - Open WebUI persistent data survives a container restart.
- Gateway can reach
http://192.168.5.52:11434. - Gateway can enumerate the models available through Oracle.
gemma4:e4bappears in the Open WebUI model selector.- A prompt submitted through Open WebUI is processed by Gemma 4 on Oracle.
- The resulting conversation remains available after Open WebUI restarts.
- The deployment and verification procedures are documented.
Current Repository Target
/srv/thoth/
├── containers/
│ ├── .git/
│ ├── .thoth/
│ │ ├── 00-project-state.md
│ │ ├── 10-architecture.md
│ │ ├── 20-philosophy.md
│ │ ├── 30-glossary.md
│ │ ├── 40-coding-standards.md
│ │ └── 50-roadmap.md
│ ├── docs/
│ ├── scripts/
│ ├── open-webui/
│ │ ├── compose.yaml
│ │ ├── .env.example
│ │ └── README.md
│ ├── .gitignore
│ └── README.md
├── data/
│ └── open-webui/
├── config/
├── backups/
└── logs/
Immediate Work Queue
- Resolve the current Docker group session.
- Run the Docker
hello-worldvalidation. - Create the
/srv/thothdirectory structure. - Initialize the infrastructure Git repository.
- Complete the remaining
.thothdocuments. - Commit the initial project self-description.
- Create the Open WebUI deployment definition.
- Validate the Compose configuration.
- Deploy Open WebUI.
- Verify direct Gateway-to-Oracle API access.
- Verify Open WebUI-to-Oracle model access.
- Perform the Gemma 4 end-to-end test.
Definition of Done
Gateway Base Commissioning is complete when:
- The host is stable and reproducible.
- Its infrastructure architecture is documented.
- Its deployment definitions are version controlled.
- Its mutable data is separated from source control.
- Its services can be restored from repository documentation.
- Open WebUI operates persistently on Gateway.
- Oracle provides Gemma 4 inference to Gateway.
- The complete request path has been tested and documented.
Completion requires evidence from successful commands, service health checks, and end-to-end inference. Installation alone does not constitute completion.