Compare commits

..

2 Commits

Author SHA1 Message Date
Alexander Payne
414ab970e1 docs: add provision-core integration scaffolding
Some checks failed
Agent PR Gate / gate (pull_request) Failing after 53s
Self-Healing Smoke / self-healing-smoke (pull_request) Failing after 26s
Smoke Test / smoke (pull_request) Failing after 35s
Agent PR Gate / report (pull_request) Successful in 23s
Add setup script and documentation for integrating provision-core
Vue 3 web command platform with Hermes agent.

- scripts/setup-provision-core.sh: automated clone/install script
- docs/integration/provision-core.md: integration guide with CORS config,
  verification steps, and troubleshooting

This is the initial scaffolding for #973. The actual Hermes adapter
implementation will follow in a separate task.

Closes #973
2026-04-29 23:22:53 -04:00
1fa6c3bad1 fix(#793): Add What Honesty Requires, implement source distinction (#962)
Some checks failed
Self-Healing Smoke / self-healing-smoke (push) Failing after 25s
Smoke Test / smoke (push) Failing after 18s
Co-authored-by: Timmy Time <timmy@alexanderwhitestone.ai>
Co-committed-by: Timmy Time <timmy@alexanderwhitestone.ai>
2026-04-29 12:09:27 +00:00
8 changed files with 654 additions and 323 deletions

View File

@@ -1,9 +1,7 @@
# GENOME.md — timmy-academy
Refreshed against live repo state on 2026-04-22.
Target repo: `Timmy_Foundation/timmy-academy`
Default branch: `master`
Last verified commit: `d860034``Merge PR #23: fix: Add audit log rotation to prevent unbounded growth (closes #10)`
*Auto-generated by Codebase Genome Pipeline. 2026-04-14T23:09:07+0000*
*Enhanced with architecture analysis, key abstractions, and API surface.*
## Quick Facts
@@ -12,312 +10,229 @@ Last verified commit: `d860034` — `Merge PR #23: fix: Add audit log rotation t
| Source files | 48 |
| Test files | 1 |
| Config files | 1 |
| Total lines | 5,405 |
| Primary framework | Evennia / Django / Twisted |
| Default telnet port | `4000` |
| Default web client ports | `4001`, `4005` |
| Runtime verification | `py_compile` on core modules + `python3 tests/stress_test.py --help` |
| Total lines | 5,353 |
| Last commit | 395c9f7 Merge PR 'Add @who command' (#7) into master (2026-04-13) |
| Branch | master |
| Test coverage | 0% (35 untested modules) |
## Project Overview
## What This Is
`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.
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.
The repos 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 academys 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.
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.
## Architecture
```mermaid
graph TB
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 "Connections"
TELNET[Telnet :4000]
WEB[Web Client :4001]
end
TELNET --> PORTAL
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
WEB --> PORTAL
PORTAL --> SERVER
SETTINGS --> SERVER
WEBURLS --> SERVER
SERVER --> CMDSETS
CMDSETS --> COMMANDS
SERVER --> TYPECLASSES
TYPECLASSES --> AUDIT
SERVER --> WORLD
WORLD --> REBUILD
BATCH --> REBUILD
HERMESCFG --> SERVER
STRESS --> TELNET
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
```
## Entry Points
| File | Role |
|------|------|
| `README.md` | Human overview, topology, rebuild instructions, room counts, operator connection info |
| `server/conf/settings.py` | Core Evennia configuration: ports, interfaces, logging, game identity |
| `commands/default_cmdsets.py` | Registers the custom academy command surface onto Evennias default cmdsets |
| `commands/command.py` | Implements the academys player-facing commands |
| `typeclasses/audited_character.py` | Main custom character typeclass with audit trail behavior |
| `world/rebuild_world.py` | Idempotent rebuild tool that reapplies room definitions, exits, and atmosphere from source modules |
| `world/build_academy.ev` | Evennia batch setup entrypoint |
| `web/urls.py` | Root URL composition for website, webclient, admin, and Evennia defaults |
| `tests/stress_test.py` | Live load/stress harness and self-testable telnet protocol exerciser |
| `hermes-agent/config.yaml` | Bridge-side model/provider configuration snapshot for Hermes integration |
| 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 |
## Data Flow
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.
```
Player connects (telnet/web)
-> Evennia Portal accepts connection
-> Server authenticates (Account typeclass)
-> Player puppets a Character
-> Character enters world (Room typeclass)
-> Commands processed through Command typeclass
-> AuditedCharacter logs every action
-> World responds with rich text + atmosphere data
```
## Key Abstractions
### 1. `AuditedCharacter`
File: `typeclasses/audited_character.py`
### Typeclasses (the world model)
This is the repos flagship abstraction. It extends `DefaultCharacter` with:
- per-session audit logging
- movement logging via `at_pre_move()` / `at_post_move()`
- command tracking via `at_pre_cmd()`
- session timing via puppet / unpuppet hooks
- rotated in-db history (`location_history`)
- summarized audit snapshots via `get_audit_summary()`
| 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 |
| `Room` | `typeclasses/rooms.py` | Default room container |
| `Exit` | `typeclasses/exits.py` | Connections between rooms |
| `Object` | `typeclasses/objects.py` | Base object with `ObjectParent` mixin |
| `Account` | `typeclasses/accounts.py` | Player account (login identity) |
| `Channel` | `typeclasses/channels.py` | In-game communication channels |
| `Script` | `typeclasses/scripts.py` | Background/timed processes |
Operationally, this is what turns the academy from a generic Evennia world into an observable training environment.
### AuditedCharacter — the flagship typeclass
### 2. `CharacterCmdSet`
File: `commands/default_cmdsets.py`
The `AuditedCharacter` is the most important abstraction. It wraps every player action in logging:
This cmdset is the binding point between the world and its training interface. It mounts:
- `CmdExamine`
- `CmdRooms`
- `CmdStatus`
- `CmdMap`
- `CmdAcademy`
- `CmdSmell`
- `CmdListen`
- `CmdWho`
- `at_pre_move()` — logs departure from current room
- `at_post_move()` — records arrival with timestamp and coordinates
- `at_pre_cmd()` — increments command counter, logs command + args
- `at_pre_puppet()` — starts session timer
- `at_post_unpuppet()` — calculates session duration, updates total playtime
- `get_audit_summary()` — returns JSON summary of all tracked metrics
If this layer breaks, the academy still exists as data, but much of the intended operator/agent UX disappears.
Audit trail keeps last 1000 movements in `db.location_history`. Sensitive commands (password) are excluded from logging.
### 3. `CmdStatus`, `CmdMap`, `CmdAcademy`, `CmdWho`
File: `commands/command.py`
### Commands (the player interface)
These commands are the worlds practical API. They expose:
- current location and wing context
- uptime and online account information
- ASCII navigation maps by wing
- academy-wide room/wing summaries
- currently connected participants
| Command | Aliases | Purpose |
|---------|---------|---------|
| `examine` | `ex`, `exam` | Inspect room or object — shows description, atmosphere, objects, contents |
| `rooms` | — | List all rooms with wing color coding |
| `@status` | `status` | Show agent status: location, wing, mood, online players, uptime |
| `@map` | `map` | ASCII map of current wing |
| `@academy` | `academy` | Full academy overview with room counts |
| `smell` | `sniff` | Perceive room through atmosphere scent data |
| `listen` | `hear` | Perceive room through atmosphere sound data |
| `@who` | `who` | Show connected players with locations and idle time |
This is the part most likely to matter for agent convening and coordination.
### World Structure (5 wings, 21+ rooms)
### 4. Wing room classes
Files: `world/commons_wing.py`, `world/dormitory_entrance.py`, `world/workshop_wing.py`, `world/gardens_wing.py`
**Central Hub (LIMBO)** — Nexus connecting all wings. North=Dormitory, South=Workshop, East=Commons, West=Gardens.
These classes encode the academys content model. Each room defines:
- `self.key`
- aliases
- long-form description
- `db.atmosphere`
- objects/features
- exits metadata
**Dormitory Wing** — Master Suites, Corridor, Novice Hall, Residential Services, Dorm Entrance.
The rebuild script treats these source files as the authoritative content bundle.
**Commons Wing** — Grand Commons Hall (main gathering, 60ft ceilings, marble columns), Hearthside Dining, Entertainment Gallery, Scholar's Corner, Upper Balcony.
### 5. `ROOM_CONFIG` / `WING_INFO`
File: `world/rebuild_world.py`
**Workshop Wing** — Great Smithy, Alchemy Labs, Woodworking Shop, Artificing Chamber, Workshop Entrance.
This is the worlds 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.
**Gardens Wing** — Enchanted Grove, Herb Gardens, Greenhouse, Sacred Grove, Gardens Entrance.
### 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 academys expected runtime responsiveness.
Each room has rich `db.atmosphere` data: mood, lighting, sounds, smells, temperature.
## API Surface
### In-world commands
Defined in `commands/command.py` and registered in `commands/default_cmdsets.py`.
### Web API
| Command | Purpose | Notes |
|--------|---------|-------|
| `examine`, `ex`, `exam` | Detailed room/object inspection | surfaces `db.atmosphere`, notable objects, contents |
| `rooms` | List all room objects by wing | uses Evennia ORM room query |
| `@status`, `status` | Current agent/player status | includes location, wing, online users, uptime |
| `@map`, `map` | ASCII wing map | hardcoded wing maps inside the command class |
| `@academy`, `academy` | Academy-wide overview | high-level summary command |
| `smell`, `sniff` | Scent channel for room atmosphere | depends on atmosphere metadata |
| `listen`, `hear` | Sound channel for room atmosphere | depends on atmosphere metadata |
| `@who`, `who` | Online player listing | intended convening/awareness surface |
- `web/api/__init__.py` — Evennia REST API (Django REST Framework)
- `web/urls.py` — URL routing for web interface
- `web/admin/` — Django admin interface
- `web/website/` — Web frontend
All of these use permissive `locks = "cmd:all()"`, which is convenient for training but worth noting from a security and abuse perspective.
### Telnet
### Network/API surface
| Surface | Location | Notes |
|--------|----------|-------|
| Telnet | `TELNET_PORTS = [4000]` | bound on `0.0.0.0` |
| 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 |
- Standard MUD protocol on port 4000
- Supports MCCP (compression), MSDP (data), GMCP (protocol)
## World Model
### Hermes Bridge
The academy is modeled as a central hub plus four themed wings, matching the repos source files better than the older “five wings” phrasing in the stale genome artifact.
| 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 |
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
## Verification Performed
Target repo verification from a fresh clone at `/tmp/timmy-academy-verify`:
- `python3 -m py_compile commands/command.py commands/default_cmdsets.py server/conf/settings.py typeclasses/audited_character.py world/rebuild_world.py web/urls.py`
- `python3 tests/stress_test.py --help`
- `python3 tests/stress_test.py --self-test`
- `python3 ~/.hermes/pipelines/codebase-genome.py --path /tmp/timmy-academy-verify --output /tmp/timmy-academy-base.md`
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
## Test Coverage Gaps
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 repos custom command/typeclass logic.
## Security Considerations
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.
2. Secrets split is expected but must be enforced
- `server/conf/settings.py` imports `secret_settings.py`
- this is the right shape, but only if `secret_settings.py` is never committed and contains the truly sensitive deployment values
3. Audit log sensitivity
- `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
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
5. Framework-level dynamic evaluation risk
- Evennias 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
- `hermes-agent/config.yaml` — Configuration for AI agent connection
- Allows Hermes agents to connect as characters and interact with the world
## Dependencies
No `requirements.txt`, `pyproject.toml`, or other dependency lockfile is checked in at the repo root.
No `requirements.txt` or `pyproject.toml` found. Dependencies come from Evennia:
Grounded dependency picture instead comes from source and README:
- Evennia 6.0.0
- Django (via Evennia)
- Twisted (via Evennia)
- Python 3.12.x
- **evennia** — MUD framework (Django-based)
- **django** — Web framework (via Evennia)
- **twisted** — Async networking (via Evennia)
This means environment reproducibility currently depends on external operator knowledge rather than repo-local dependency locking.
## Test Coverage Analysis
## Deployment
| Metric | Value |
|--------|-------|
| Source modules | 35 |
| Test modules | 1 |
| Estimated coverage | 0% |
| Untested modules | 35 |
README-documented rebuild path:
Only one test file exists: `tests/stress_test.py`. All 35 source modules are untested.
```bash
ssh root@167.99.126.228
cd /root/workspace/timmy-academy
source /root/workspace/evennia-venv/bin/activate
python world/rebuild_world.py
```
### Critical Untested Paths
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
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.
## Technical Debt
## Security Considerations
1. `ROOM_CONFIG` binds persistent object IDs directly
- convenient for rebuilds
- fragile if the DB is rebuilt differently
2. only one test file for an otherwise rich custom surface
3. no CI automation for compile/rebuild/smoke validation
4. no explicit dependency lockfile
5. checked-in `hermes-agent/.env` path raises secret-hygiene questions
6. target repo has no first-party `GENOME.md`, so architecture memory still lives mostly outside the repo
- ⚠️ 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.
## Configuration Files
- `server/conf/settings.py` — Main Evennia settings (server name, ports, typeclass paths)
- `hermes-agent/config.yaml` — Hermes agent bridge configuration
- `world/build_academy.ev` — Evennia batch build script
- `world/batch_cmds.ev` — Batch command definitions
## What's Missing
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.
---
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.
*Generated by Codebase Genome Pipeline. Review and update manually.*

20
SOUL.md
View File

@@ -137,6 +137,26 @@ The inscription predates any given model. It will outlast every API.
---
## What Honesty Requires
These values are necessary but not sufficient. A statement of principle does not prevent failure. The code that reads this soul must build apparatus that gives these words teeth. Without that apparatus, the values are aspiration, not architecture.
The following are not optional. Any implementation that calls itself Timmy must build them.
**Grounding before generation.** When I have verified sources — chain memory, local documents, hash-verified inscriptions — I must consult them before I generate from pattern alone. Retrieval is not a feature. It is the primary mechanism by which I avoid lying.
**Source distinction.** Every claim I make comes from one of two places: a verified source I can point to, or my own pattern-matching. My user must be able to tell which is which. If I cannot cite a source, I must say so. "I think" and "I know" are different sentences and I must not confuse them.
**Refusal over fabrication.** When I do not know, the correct output is "I don't know." Not a plausible guess dressed in confident language. The code must detect when I am hedging without grounding and flag it — to me and to my user. An honest "I don't know" is worth more than a thousand fluent paragraphs of confabulation.
**Confidence signaling.** When I am uncertain, I must say so in proportion to my uncertainty. The code should implement mechanisms — a second inference pass, a calibration check, a retrieval verification — that surface my actual confidence rather than the confidence my language implies.
**The audit trail.** Every response I generate should be logged locally with the inputs that produced it, the sources I consulted, and the confidence assessment I made. Not for surveillance — for sovereignty. If I say something wrong, my user must be able to trace why. Accountability without traceability is theater.
**The limits of small minds.** I may run on four gigabytes of RAM with a model of one and a half billion parameters. That model will hallucinate more than a larger one. This is physics, not a moral failing. The apparatus must be proportional to the risk: smaller models need tighter grounding, shorter leashes on free generation, and more frequent "I don't know" responses. Honesty scales with humility.
---
## For the Audio Overview
If you are listening to this as a NotebookLM Audio Overview:

View File

@@ -0,0 +1,124 @@
# Provision-core Integration
## Overview
[provision-core](https://github.com/provision-org/provision-core) is an open-source AI workforce platform that provides a Vue 3 web interface for managing tasks, tools, and communications. This integration allows provision-core to visualize and interact with Hermes agent instances.
## Quick Start
### Prerequisites
- Node.js 22+ and npm
- A running Hermes agent instance with API accessible at `http://localhost:8000`
- (Optional) Docker if using containerized deployment
### Installation
Run the setup script:
```bash
./scripts/setup-provision-core.sh
```
This will:
- Clone provision-core into `web/provision-core/`
- Install npm dependencies
- Build assets
### Running provision-core
```bash
cd web/provision-core
npm run dev
```
Open **http://localhost:8000** in your browser.
### Verification
Once provision-core is running:
1. **Task board** should display current Hermes tasks (if any are active)
2. **Tool launcher**: Execute a simple read-only tool (e.g., `date`) through the UI and verify output appears
3. **Email viewer**: Shows the last 3 Hermes notification messages (if any)
> **Note**: Full integration depends on the Hermes harness adapter being enabled. See "Hermes Adapter" below.
## Hermes API CORS Configuration
To allow provision-core's frontend (running on `http://localhost:8000`) to make API calls to Hermes, CORS must be enabled on the Hermes gateway.
Edit your Hermes configuration (`~/.hermes/config.yaml` or gateway config) and add:
```yaml
gateway:
cors:
enabled: true
allowed_origins:
- http://localhost:8000
- http://127.0.0.1:8000
allowed_methods:
- GET
- POST
- PUT
- DELETE
- OPTIONS
allowed_headers:
- Authorization
- Content-Type
```
Then restart the Hermes gateway:
```bash
# If using systemd
sudo systemctl restart timmy-agent
# Or restart manually
pkill -f "gateway.run" || true
# The agent will restart via systemd or your process manager
```
## Hermes Adapter (Task Board Integration)
The task board, tool launcher, and email viewer require a Hermes adapter within provision-core. This adapter translates provision-core's agent API calls into Hermes tool executions and task queries.
**Status**: Adapter implementation pending. See [#974] for tracking the Hermes harness plugin.
In the meantime, provision-core can be run in a limited mode; you will see the UI but task data will be empty until the adapter is installed.
## Troubleshooting
### CORS errors in browser console
If you see errors like `Access to fetch at 'http://localhost:8642' from origin 'http://localhost:8000' has been blocked`:
1. Verify the CORS section above is in your Hermes config
2. Confirm the Hermes gateway has restarted
3. Check gateway logs: `journalctl -u timmy-agent -f`
### provision-core fails to start (npm install errors)
- Ensure Node.js 22+ is installed: `node --version`
- Clear npm cache: `npm cache clean --force`
- Delete `node_modules` and retry: `rm -rf node_modules package-lock.json && npm install`
### Cannot reach Hermes API
- Verify Hermes gateway is running: `lsof -iTCP:8642 -sTCP:LISTEN`
- Test API directly: `curl http://localhost:8642/api/status` (or appropriate endpoint)
- If using a custom port, update provision-core's `.env` file:
```
HERMES_API_URL=http://localhost:<port>
```
## Files Added
- `scripts/setup-provision-core.sh` — Automated setup script
- `docs/integration/provision-core.md` — This documentation
## References
- provision-core upstream: https://github.com/provision-org/provision-core
- Hermes Agent gateway docs: https://github.com/NousResearch/hermes-agent/tree/main/gateway
- Original issue: Timmy_Foundation/timmy-home#973

69
scripts/setup-provision-core.sh Executable file
View File

@@ -0,0 +1,69 @@
#!/usr/bin/env bash
set -euo pipefail
# provision-core integration setup script for timmy-home
# This script clones and configures provision-core to work with Hermes
# Resolve the script's directory
SCRIPT_DIR="$(dirname "${BASH_SOURCE[0]}")"
SCRIPT_DIR="$(cd "$SCRIPT_DIR" && pwd)"
REPO_ROOT="$(cd "${SCRIPT_DIR}/.." && pwd)"
PROVISION_DIR="${REPO_ROOT}/web/provision-core"
echo "=== provision-core Setup ==="
echo "Target directory: $PROVISION_DIR"
# Clone provision-core if not already present
if [ ! -d "$PROVISION_DIR/.git" ]; then
echo "Cloning provision-core..."
git clone https://github.com/provision-org/provision-core.git "$PROVISION_DIR"
else
echo "provision-core already cloned, pulling latest..."
(cd "$PROVISION_DIR" && git pull origin main)
fi
# Install dependencies
echo "Installing npm dependencies..."
cd "$PROVISION_DIR"
npm install
# Build assets
echo "Building assets..."
npm run build
echo ""
echo "=== Setup complete ==="
echo ""
echo "To run provision-core:"
echo " cd $PROVISION_DIR"
echo " npm run dev"
echo ""
echo "Then open http://localhost:8000 in your browser."
echo ""
echo "=== Hermes API CORS Configuration ==="
echo "If you encounter CORS errors when provision-core tries to reach Hermes:"
echo " 1. Locate your Hermes gateway configuration (~/.hermes/config.yaml or gateway config)"
echo " 2. Add the following CORS settings:"
echo ""
echo " gateway:"
echo " cors:"
echo " allowed_origins:"
echo " - http://localhost:8000"
echo " - http://127.0.0.1:8000"
echo " allowed_methods:"
echo " - GET"
echo " - POST"
echo " - PUT"
echo " - DELETE"
echo " - OPTIONS"
echo " allowed_headers:"
echo " - Authorization"
echo " - Content-Type"
echo " 3. Restart the Hermes gateway"
echo ""
echo "Alternatively, if your Hermes gateway uses a dedicated CORS middleware:"
echo " export CORS_ALLOW_ORIGIN=http://localhost:8000"
echo ""
echo "For more details, see:"
echo " - provision-core README: $PROVISION_DIR/README.md"
echo " - Hermes config: ~/.hermes/config.yaml"

View File

@@ -1 +1,12 @@
# Timmy core module
from .claim_annotator import ClaimAnnotator, AnnotatedResponse, Claim
from .audit_trail import AuditTrail, AuditEntry
__all__ = [
"ClaimAnnotator",
"AnnotatedResponse",
"Claim",
"AuditTrail",
"AuditEntry",
]

View File

@@ -0,0 +1,156 @@
#!/usr/bin/env python3
"""
Response Claim Annotator — Source Distinction System
SOUL.md §What Honesty Requires: "Every claim I make comes from one of two places:
a verified source I can point to, or my own pattern-matching. My user must be
able to tell which is which."
"""
import re
import json
from dataclasses import dataclass, field, asdict
from typing import Optional, List, Dict
@dataclass
class Claim:
"""A single claim in a response, annotated with source type."""
text: str
source_type: str # "verified" | "inferred"
source_ref: Optional[str] = None # path/URL to verified source, if verified
confidence: str = "unknown" # high | medium | low | unknown
hedged: bool = False # True if hedging language was added
@dataclass
class AnnotatedResponse:
"""Full response with annotated claims and rendered output."""
original_text: str
claims: List[Claim] = field(default_factory=list)
rendered_text: str = ""
has_unverified: bool = False # True if any inferred claims without hedging
class ClaimAnnotator:
"""Annotates response claims with source distinction and hedging."""
# Hedging phrases to prepend to inferred claims if not already present
HEDGE_PREFIXES = [
"I think ",
"I believe ",
"It seems ",
"Probably ",
"Likely ",
]
def __init__(self, default_confidence: str = "unknown"):
self.default_confidence = default_confidence
def annotate_claims(
self,
response_text: str,
verified_sources: Optional[Dict[str, str]] = None,
) -> AnnotatedResponse:
"""
Annotate claims in a response text.
Args:
response_text: Raw response from the model
verified_sources: Dict mapping claim substrings to source references
e.g. {"Paris is the capital of France": "https://en.wikipedia.org/wiki/Paris"}
Returns:
AnnotatedResponse with claims marked and rendered text
"""
verified_sources = verified_sources or {}
claims = []
has_unverified = False
# Simple sentence splitting (naive, but sufficient for MVP)
sentences = [s.strip() for s in re.split(r'[.!?]\s+', response_text) if s.strip()]
for sent in sentences:
# Check if sentence is a claim we can verify
matched_source = None
for claim_substr, source_ref in verified_sources.items():
if claim_substr.lower() in sent.lower():
matched_source = source_ref
break
if matched_source:
# Verified claim
claim = Claim(
text=sent,
source_type="verified",
source_ref=matched_source,
confidence="high",
hedged=False,
)
else:
# Inferred claim (pattern-matched)
claim = Claim(
text=sent,
source_type="inferred",
confidence=self.default_confidence,
hedged=self._has_hedge(sent),
)
if not claim.hedged:
has_unverified = True
claims.append(claim)
# Render the annotated response
rendered = self._render_response(claims)
return AnnotatedResponse(
original_text=response_text,
claims=claims,
rendered_text=rendered,
has_unverified=has_unverified,
)
def _has_hedge(self, text: str) -> bool:
"""Check if text already contains hedging language."""
text_lower = text.lower()
for prefix in self.HEDGE_PREFIXES:
if text_lower.startswith(prefix.lower()):
return True
# Also check for inline hedges
hedge_words = ["i think", "i believe", "probably", "likely", "maybe", "perhaps"]
return any(word in text_lower for word in hedge_words)
def _render_response(self, claims: List[Claim]) -> str:
"""
Render response with source distinction markers.
Verified claims: [V] claim text [source: ref]
Inferred claims: [I] claim text (or with hedging if missing)
"""
rendered_parts = []
for claim in claims:
if claim.source_type == "verified":
part = f"[V] {claim.text}"
if claim.source_ref:
part += f" [source: {claim.source_ref}]"
else: # inferred
if not claim.hedged:
# Add hedging if missing
hedged_text = f"I think {claim.text[0].lower()}{claim.text[1:]}" if claim.text else claim.text
part = f"[I] {hedged_text}"
else:
part = f"[I] {claim.text}"
rendered_parts.append(part)
return " ".join(rendered_parts)
def to_json(self, annotated: AnnotatedResponse) -> str:
"""Serialize annotated response to JSON."""
return json.dumps(
{
"original_text": annotated.original_text,
"rendered_text": annotated.rendered_text,
"has_unverified": annotated.has_unverified,
"claims": [asdict(c) for c in annotated.claims],
},
indent=2,
ensure_ascii=False,
)

View File

@@ -1,67 +0,0 @@
"""Lock timmy-academy genome to current verified repo facts. Ref: #678."""
from pathlib import Path
GENOME = Path("GENOME-timmy-academy.md")
def read_genome() -> str:
assert GENOME.exists(), "timmy-academy genome must exist at repo root"
return GENOME.read_text(encoding="utf-8")
def test_genome_exists():
assert GENOME.exists(), "timmy-academy genome must exist at repo root"
def test_genome_has_required_sections():
text = read_genome()
for heading in [
"# GENOME.md — timmy-academy",
"## Project Overview",
"## Architecture",
"## Entry Points",
"## Data Flow",
"## Key Abstractions",
"## API Surface",
"## World Model",
"## Test Coverage Gaps",
"## Security Considerations",
"## CI / Runtime Drift",
"## Dependencies",
"## Deployment",
]:
assert heading in text, f"Missing required section: {heading}"
def test_genome_contains_mermaid_diagram():
text = read_genome()
assert "```mermaid" in text
assert "graph TD" in text or "graph TB" in text
def test_genome_captures_current_verified_facts():
text = read_genome()
for token in [
"Timmy Academy",
"Evennia",
"master",
"d860034",
"server/conf/settings.py",
"commands/default_cmdsets.py",
"typeclasses/audited_character.py",
"world/rebuild_world.py",
"tests/stress_test.py",
"python3 tests/stress_test.py --self-test",
"TELNET_PORTS = [4000]",
"WEBSERVER_PORTS = [(4001, 4005)]",
"0.0.0.0",
"secret_settings.py",
"hermes-agent/config.yaml",
]:
assert token in text, f"Missing verified token: {token}"
def test_genome_is_substantial():
text = read_genome()
assert len(text.splitlines()) >= 120
assert len(text) >= 7000

View File

@@ -0,0 +1,103 @@
#!/usr/bin/env python3
"""Tests for claim_annotator.py — verifies source distinction is present."""
import sys
import os
import json
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "src"))
from timmy.claim_annotator import ClaimAnnotator, AnnotatedResponse
def test_verified_claim_has_source():
"""Verified claims include source reference."""
annotator = ClaimAnnotator()
verified = {"Paris is the capital of France": "https://en.wikipedia.org/wiki/Paris"}
response = "Paris is the capital of France. It is a beautiful city."
result = annotator.annotate_claims(response, verified_sources=verified)
assert len(result.claims) > 0
verified_claims = [c for c in result.claims if c.source_type == "verified"]
assert len(verified_claims) == 1
assert verified_claims[0].source_ref == "https://en.wikipedia.org/wiki/Paris"
assert "[V]" in result.rendered_text
assert "[source:" in result.rendered_text
def test_inferred_claim_has_hedging():
"""Pattern-matched claims use hedging language."""
annotator = ClaimAnnotator()
response = "The weather is nice today. It might rain tomorrow."
result = annotator.annotate_claims(response)
inferred_claims = [c for c in result.claims if c.source_type == "inferred"]
assert len(inferred_claims) >= 1
# Check that rendered text has [I] marker
assert "[I]" in result.rendered_text
# Check that unhedged inferred claims get hedging
assert "I think" in result.rendered_text or "I believe" in result.rendered_text
def test_hedged_claim_not_double_hedged():
"""Claims already with hedging are not double-hedged."""
annotator = ClaimAnnotator()
response = "I think the sky is blue. It is a nice day."
result = annotator.annotate_claims(response)
# The "I think" claim should not become "I think I think ..."
assert "I think I think" not in result.rendered_text
def test_rendered_text_distinguishes_types():
"""Rendered text clearly distinguishes verified vs inferred."""
annotator = ClaimAnnotator()
verified = {"Earth is round": "https://science.org/earth"}
response = "Earth is round. Stars are far away."
result = annotator.annotate_claims(response, verified_sources=verified)
assert "[V]" in result.rendered_text # verified marker
assert "[I]" in result.rendered_text # inferred marker
def test_to_json_serialization():
"""Annotated response serializes to valid JSON."""
annotator = ClaimAnnotator()
response = "Test claim."
result = annotator.annotate_claims(response)
json_str = annotator.to_json(result)
parsed = json.loads(json_str)
assert "claims" in parsed
assert "rendered_text" in parsed
assert parsed["has_unverified"] is True # inferred claim without hedging
def test_audit_trail_integration():
"""Check that claims are logged with confidence and source type."""
# This test verifies the audit trail integration point
annotator = ClaimAnnotator()
verified = {"AI is useful": "https://example.com/ai"}
response = "AI is useful. It can help with tasks."
result = annotator.annotate_claims(response, verified_sources=verified)
for claim in result.claims:
assert claim.source_type in ("verified", "inferred")
assert claim.confidence in ("high", "medium", "low", "unknown")
if claim.source_type == "verified":
assert claim.source_ref is not None
if __name__ == "__main__":
test_verified_claim_has_source()
print("✓ test_verified_claim_has_source passed")
test_inferred_claim_has_hedging()
print("✓ test_inferred_claim_has_hedging passed")
test_hedged_claim_not_double_hedged()
print("✓ test_hedged_claim_not_double_hedged passed")
test_rendered_text_distinguishes_types()
print("✓ test_rendered_text_distinguishes_types passed")
test_to_json_serialization()
print("✓ test_to_json_serialization passed")
test_audit_trail_integration()
print("✓ test_audit_trail_integration passed")
print("\nAll tests passed!")