Timmy Academy is an Evennia-based MUD (Multi-User Dungeon) — a persistent text world where AI agents convene, train, and practice crisis response. It runs on Bezalel VPS (167.99.126.228) with telnet on port 4000 and web client on port 4001.
`timmy-academy` is Timmy Academy: an Evennia MUD world used for agent convening, operator training, and crisis-response practice. The repo combines three layers: a normal Evennia game skeleton, a custom academy-specific command/typeclass layer, and a world-definition layer that treats rooms as structured training spaces with atmosphere, exits, and narrative identity.
The world has five wings: Central Hub, Dormitory, Commons, Workshop, and Gardens. Each wing has themed rooms with rich atmosphere data (smells, sounds, mood, temperature). Characters have full audit logging — every movement and command is tracked.
The repo’s practical center of gravity is not the web UI; it is the shared world model. Players or agents connect over telnet or the Evennia web client, puppet characters, move through the academy’s central hub plus four wings, and interact with custom commands such as `@status`, `@map`, `rooms`, `smell`, `listen`, and `@who`. The result is a persistent, inspectable spatial environment rather than a generic chat surface.
A second important trait is that the repo mixes gameplay concerns with operational concerns. `server/conf/settings.py` enables detailed audit logging. `typeclasses/audited_character.py` records movement and command trails. `world/rebuild_world.py` can rehydrate the academy from source definitions. `tests/stress_test.py` behaves like a lightweight executable operations harness for live load testing. Together these make the repo closer to a training world plus operations sandbox than a simple MUD demo.
## Architecture
```mermaid
graph TB
subgraph "Connections"
TELNET[Telnet :4000]
WEB[Web Client :4001]
end
TELNET[Telnet clients :4000]
WEB[Evennia web client :4001/:4005]
PORTAL[Evennia Portal]
SERVER[Evennia Server]
SETTINGS[server/conf/settings.py]
CMDSETS[commands/default_cmdsets.py]
COMMANDS[commands/command.py]
TYPECLASSES[typeclasses/*]
AUDIT[typeclasses/audited_character.py]
WORLD[world/*_wing.py]
REBUILD[world/rebuild_world.py]
BATCH[world/build_academy.ev]
WEBURLS[web/urls.py]
HERMESCFG[hermes-agent/config.yaml]
STRESS[tests/stress_test.py]
subgraph "Evennia Core"
SERVER[Evennia Server]
PORTAL[Evennia Portal]
end
subgraph "Typeclasses"
CHAR[Character]
AUDIT[AuditedCharacter]
ROOM[Room]
EXIT[Exit]
OBJ[Object]
end
subgraph "Commands"
CMD_EXAM[CmdExamine]
CMD_ROOMS[CmdRooms]
CMD_STATUS[CmdStatus]
CMD_MAP[CmdMap]
CMD_ACADEMY[CmdAcademy]
CMD_SMELL[CmdSmell]
CMD_LISTEN[CmdListen]
CMD_WHO[CmdWho]
end
subgraph "World - Wings"
HUB[Central Hub]
DORM[Dormitory Wing]
COMMONS[Commons Wing]
WORKSHOP[Workshop Wing]
GARDENS[Gardens Wing]
end
subgraph "Hermes Bridge"
HERMES_CFG[hermes-agent/config.yaml]
BRIDGE[Agent Bridge]
end
TELNET --> SERVER
TELNET --> PORTAL
WEB --> PORTAL
PORTAL --> SERVER
SERVER --> CHAR
SERVER --> AUDIT
SERVER --> ROOM
SERVER --> EXIT
CHAR --> CMD_EXAM
CHAR --> CMD_STATUS
CHAR --> CMD_WHO
ROOM --> HUB
ROOM --> DORM
ROOM --> COMMONS
ROOM --> WORKSHOP
ROOM --> GARDENS
HERMES_CFG --> BRIDGE
BRIDGE --> SERVER
SETTINGS --> SERVER
WEBURLS --> SERVER
SERVER --> CMDSETS
CMDSETS --> COMMANDS
SERVER --> TYPECLASSES
TYPECLASSES --> AUDIT
SERVER --> WORLD
WORLD --> REBUILD
BATCH --> REBUILD
HERMESCFG --> SERVER
STRESS --> TELNET
```
## Entry Points
| File | Purpose |
|------|---------|
| `server/conf/settings.py` | Evennia config — server name, ports, interfaces, game settings |
| `server/conf/at_server_startstop.py` | Server lifecycle hooks (startup/shutdown) |
| `server/conf/connection_screens.py` | Login/connection screen text |
| `commands/default_cmdsets.py` | Registers all custom commands with Evennia |
| `world/rebuild_world.py` | Rebuilds all rooms from source |
| `world/build_academy.ev` | Evennia batch script for initial world setup |
| File | Role |
|------|------|
| `README.md` | Human overview, topology, rebuild instructions, room counts, operator connection info |
-> World responds with rich text + atmosphere data
```
1. A human or agent connects over telnet (`4000`) or the Evennia web client (`4001` / `4005`).
2. The Evennia portal hands the connection to the game server configured by `server/conf/settings.py`.
3. Once an account puppets a character, the command path is controlled by `commands/default_cmdsets.py`, which mounts the academy-specific commands from `commands/command.py`.
4. The typeclass layer (`typeclasses/*`) determines how characters, rooms, exits, channels, and scripts behave; `AuditedCharacter` wraps command and movement hooks in persistent logging.
5. The world layer (`world/*_wing.py`) supplies canonical room descriptions, exits, aliases, atmosphere, and thematic metadata.
6.`world/rebuild_world.py` parses those source files and writes them back into Evennia objects, making source the effective truth for the academy layout.
7.`tests/stress_test.py` simulates concurrent clients against the live telnet surface and reports throughput, latency, and connection statistics.
## Key Abstractions
### Typeclasses (the world model)
### 1. `AuditedCharacter`
File: `typeclasses/audited_character.py`
| Class | File | Purpose |
|-------|------|---------|
| `Character` | `typeclasses/characters.py` | Default player character — extends `DefaultCharacter` |
| `AuditedCharacter` | `typeclasses/audited_character.py` | Character with full audit logging — tracks movements, commands, playtime |
**Gardens Wing** — Enchanted Grove, Herb Gardens, Greenhouse, Sacred Grove, Gardens Entrance.
This is the world’s rehydration map. It hard-binds Evennia object IDs to source classes and wings. That makes the rebuild deterministic, but it also couples source truth to existing DB IDs — a real maintenance risk if the database is re-seeded differently.
Each room has rich `db.atmosphere` data: mood, lighting, sounds, smells, temperature.
### 6. Stress-test dataclasses and `MudClient`
File: `tests/stress_test.py`
The stress harness uses:
-`ActionResult`
-`PlayerStats`
-`StressTestReport`
-`MudClient`
This test file doubles as an executable spec for the live connection surface and the academy’s expected runtime responsiveness.
## API Surface
### Web API
### In-world commands
Defined in `commands/command.py` and registered in `commands/default_cmdsets.py`.
-`web/api/__init__.py` — Evennia REST API (Django REST Framework)
| Web client | `WEBSERVER_PORTS = [(4001, 4005)]` | bound on `0.0.0.0` |
| Django web stack | `web/urls.py` | includes website, webclient, admin, and Evennia defaults |
| Hermes bridge config | `hermes-agent/config.yaml` | configuration-only integration point; not an executable bridge implementation inside this repo |
### Hermes Bridge
## World Model
-`hermes-agent/config.yaml` — Configuration for AI agent connection
- Allows Hermes agents to connect as characters and interact with the world
The academy is modeled as a central hub plus four themed wings, matching the repo’s source files better than the older “five wings” phrasing in the stale genome artifact.
## Dependencies
| Zone | Source | Notes |
|------|--------|------|
| Central Hub / Limbo | `world/rebuild_world.py` | special-case hub description and routing nexus |
| Dormitory Wing | `world/dormitory_entrance.py` | residence/rest zone |
| Commons Wing | `world/commons_wing.py` | social and gathering zone |
| Workshop Wing | `world/workshop_wing.py` | crafting and alchemy zone |
| Gardens Wing | `world/gardens_wing.py` | nature and contemplative zone |
No `requirements.txt` or `pyproject.toml` found. Dependencies come from Evennia:
Grounded repo facts:
- README advertises `21 rooms, 43+ exits across 5 zones`
-`ROOM_CONFIG` in `world/rebuild_world.py` maps room IDs `3..22` for wing rooms, while Limbo/hub is treated separately
- atmosphere metadata is a first-class room feature, not cosmetic prose
- **evennia** — MUD framework (Django-based)
- **django** — Web framework (via Evennia)
- **twisted** — Async networking (via Evennia)
## Verification Performed
## Test Coverage Analysis
Target repo verification from a fresh clone at `/tmp/timmy-academy-verify`:
Only one test file exists: `tests/stress_test.py`. All 35 source modules are untested.
Observed runtime-adjacent facts:
- core modules compile as Python
- the stress harness advertises `--self-test` and `--json` modes
- target repo does **not** contain a checked-in `GENOME.md` at its own root
### Critical Untested Paths
## Test Coverage Gaps
1.**AuditedCharacter** — audit logging is the primary value-add. No tests verify movement tracking, command counting, or playtime calculation.
2.**Commands** — no tests for any of the 8 commands. The `@map` wing detection, `@who` session tracking, and atmosphere-based commands (`smell`, `listen`) are all untested.
3.**World rebuild** — `rebuild_world.py` and `fix_world.py` can destroy and recreate the entire world. No tests ensure they produce valid output.
4.**Typeclass hooks** — `at_pre_move`, `at_post_move`, `at_pre_cmd` etc. are never tested in isolation.
The repo still has only one test file: `tests/stress_test.py`.
Critical untested paths:
1.`typeclasses/audited_character.py`
- no direct tests for move logging, audit pruning, command counting, or session accounting
2.`commands/command.py`
- no command-level unit tests for `@status`, `@map`, `rooms`, `smell`, `listen`, or `@who`
3.`world/rebuild_world.py`
- no tests for parsing wing files, room ID mapping, exit verification, or idempotent rebuild behavior
4.`server/conf/settings.py`
- no configuration sanity checks for port exposure, logging handlers, or audit defaults
5.`web/urls.py`
- no tests confirming routing composition for website/webclient/admin
The existing stress harness is valuable, but it is not a substitute for unit or integration tests around the repo’s custom command/typeclass logic.
## Security Considerations
- ⚠️ Uses `eval()`/`exec()` — Evennia's inlinefuncs module uses eval for dynamic command evaluation. Risk level: inherent to MUD framework.
- ⚠️ References secrets/passwords — `settings.py` references `secret_settings.py` for sensitive config. Ensure this file is not committed.
-⚠️ Telnet on 0.0.0.0 — server accepts connections from any IP. Consider firewall rules.
- ⚠️ Web client on 0.0.0.0 — same exposure as telnet. Ensure authentication is enforced.
- ⚠️ Agent bridge (`hermes-agent/config.yaml`) — verify credentials are not hardcoded.
1. Network exposure
-`TELNET_INTERFACES = ['0.0.0.0']`
-`WEBSERVER_INTERFACES = ['0.0.0.0']`
These settings expose the academy to all interfaces. That may be intended on the VPS, but it shifts safety to firewall/reverse-proxy controls.
-`AuditedCharacter.at_pre_cmd()` excludes password commands from audit logging
-good safeguard, but the rest of the command stream is still intentionally retained and should be treated as sensitive behavioral telemetry
## What's Missing
4. Checked-in bridge environment file
- the repo contains `hermes-agent/.env`
- even if it is benign now, a checked-in `.env` path is a standing secret-handling risk and should be treated carefully
1.**Tests** — 0% coverage is a critical gap. Priority: AuditedCharacter hooks, command func() methods, world rebuild integrity.
2.**CI/CD** — No automated testing pipeline. No GitHub Actions or Gitea workflows.
3.**Documentation** — `world/BUILDER_GUIDE.md` exists but no developer onboarding docs.
4.**Monitoring** — No health checks, no metrics export, no alerting on server crashes.
5.**Backup** — No automated database backup for the Evennia SQLite/PostgreSQL database.
5.Framework-level dynamic evaluation risk
- Evennia’s config surface includes modules like `server/conf/inlinefuncs.py`
- this is inherited framework behavior, but still part of the runtime attack surface
## CI / Runtime Drift
This repo has meaningful operational drift and missing automation:
1. No checked-in CI workflows
- no `.gitea/workflows/*` or `.github/workflows/*` coverage surfaced in the fresh clone
- the academy relies on manual rebuild and manual stress testing
2. Target repo root lacks its own `GENOME.md`
- the genome issue lives in `timmy-home`
- the analyzed repo itself still does not carry an in-repo architecture artifact
3.`README.md` vs command docs wording drift
- README frames the academy as four thematic wings plus a hub/zone model
- older generated genome wording called these “five wings”
- the source-of-truth model is more accurately “central hub + four wings”
4. Bridge configuration drift
-`hermes-agent/config.yaml` still references `anthropic/claude-opus-4.6`
- this is a real integration snapshot inside the repo and should be treated as provider-policy drift if the surrounding stack has moved away from Anthropic
## Dependencies
No `requirements.txt`, `pyproject.toml`, or other dependency lockfile is checked in at the repo root.
Grounded dependency picture instead comes from source and README:
- Evennia 6.0.0
- Django (via Evennia)
- Twisted (via Evennia)
- Python 3.12.x
This means environment reproducibility currently depends on external operator knowledge rather than repo-local dependency locking.
## Deployment
README-documented rebuild path:
```bash
ssh root@167.99.126.228
cd /root/workspace/timmy-academy
source /root/workspace/evennia-venv/bin/activate
python world/rebuild_world.py
```
Operationally relevant deployment facts:
- target VPS in README: `167.99.126.228`
- telnet surface: `4000`
- web client surface: `4001`
- the repo assumes an Evennia virtualenv outside the repo itself
- world rebuild is source-driven and intended to be idempotent
6. target repo has no first-party `GENOME.md`, so architecture memory still lives mostly outside the repo
---
*Generated by Codebase Genome Pipeline. Review and update manually.*
This genome was refreshed against the live `timmy-academy` repository and verified with compile + stress-harness entrypoint checks, not just copied from the older auto-generated artifact.
@@ -10,12 +10,9 @@ This document records the first concrete house layout for Ezra and Bezalel.
- Role: repo / Gitea / architecture wizard house
### Bezalel host
- VPS: TestBed (DEPRECATED — original VPS at 67.205.155.108 unreachable since 2026-04-04)
- Public IP: `167.99.126.228` (shared with Allegro VPS)
- VPS: TestBed
- Public IP: `67.205.155.108`
- Role: forge / test / optimization wizard house
- Migration: Bezalel services colocated with Allegro after TestBed VPS failure
> Note: The original TestBed VPS (67.205.155.108) is dead. Bezalel was migrated to share the Allegro VPS (167.99.126.228) to restore CI testbed and wizard house functionality. See #506.
endpoint:http://167.99.126.228:8643 # Shared with Allegro after TestBed VPS death (was 67.205.155.108)
endpoint:http://67.205.155.108:8643
role:artificer
```
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
