Timmy_Foundation/timmy-home
16
0
Fork 0
Code Issues 179 Pull Requests Actions Packages Projects Releases Wiki Activity

[IMPLEMENTATION] Stand up local Evennia world and Hermes control path #36

New Issue
Closed
opened 2026-03-28 16:28:38 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-28 16:28:38 +00:00
Owner
Copy Link

Parent direction: #34

Goal:
Stand up Timmy’s first local Evennia world and make it inhabitable through the Hermes harness.

Canonical philosophy:

  • Hermes remains the brain.
  • Evennia becomes the persistent world body.
  • World persistence should live in Evennia state, not in prompt rehydration.
  • Timmy must be runnable through the harness so gameplay/world sessions land in Hermes transcripts.
  • Alexander must be able to watch the world live while Timmy inhabits it.

Prototype target:

  • local-only first
  • one operator-visible world
  • one Timmy inhabitant/control path
  • first 5 canonical rooms only: Gate, Courtyard, Workshop, Archive, Chapel

Acceptance:

  • initialize a local Evennia project under ~/.timmy/evennia/ (or clearly document the final chosen path)
  • prove the server boots and survives restart with persistent state intact
  • expose a watchable operator surface (browser at localhost:4001 and/or telnet at localhost:4000)
  • create the first 5 canonical rooms and their exits
  • create first persistent objects: Book of the Soul, Workbench, Map Table, Prayer Wall, Memory Shelves, Mirror of Sessions (stub versions acceptable for v1)
  • define and implement the first Hermes control path into the world (prefer MCP server / adapter, not ad-hoc manual scraping)
  • prove Timmy can at minimum: connect, look, move, inspect, read, and revisit persistent state
  • keep the prototype local-first and compatible with local llama.cpp-backed Hermes sessions

Implementation preference:

  • thin integration over overbuilding
  • use Evennia’s own persistence and command model instead of inventing shadow state
  • preserve operator watchability from day one

Verification:

  • command/log proof that Evennia boots locally
  • visible proof that the operator can connect and watch
  • transcript/log proof that Timmy can inhabit the first room graph through the harness
Parent direction: #34 Goal: Stand up Timmy’s first local Evennia world and make it inhabitable through the Hermes harness. Canonical philosophy: - Hermes remains the brain. - Evennia becomes the persistent world body. - World persistence should live in Evennia state, not in prompt rehydration. - Timmy must be runnable through the harness so gameplay/world sessions land in Hermes transcripts. - Alexander must be able to watch the world live while Timmy inhabits it. Prototype target: - local-only first - one operator-visible world - one Timmy inhabitant/control path - first 5 canonical rooms only: Gate, Courtyard, Workshop, Archive, Chapel Acceptance: - initialize a local Evennia project under `~/.timmy/evennia/` (or clearly document the final chosen path) - prove the server boots and survives restart with persistent state intact - expose a watchable operator surface (browser at localhost:4001 and/or telnet at localhost:4000) - create the first 5 canonical rooms and their exits - create first persistent objects: Book of the Soul, Workbench, Map Table, Prayer Wall, Memory Shelves, Mirror of Sessions (stub versions acceptable for v1) - define and implement the first Hermes control path into the world (prefer MCP server / adapter, not ad-hoc manual scraping) - prove Timmy can at minimum: connect, look, move, inspect, read, and revisit persistent state - keep the prototype local-first and compatible with local llama.cpp-backed Hermes sessions Implementation preference: - thin integration over overbuilding - use Evennia’s own persistence and command model instead of inventing shadow state - preserve operator watchability from day one Verification: - command/log proof that Evennia boots locally - visible proof that the operator can connect and watch - transcript/log proof that Timmy can inhabit the first room graph through the harness
Timmy self-assigned this 2026-03-28 16:28:38 +00:00
Timmy commented 2026-03-28 17:34:46 +00:00
Author
Owner
Copy Link

PR opened: #38

Link:
http://143.198.27.163:3000/Timmy_Foundation/timmy-home/pulls/38

Verification artifact:

  • reports/production/2026-03-28-evennia-world-proof.md

Local proof summary:

  • Evennia booted successfully on localhost:4000/4001
  • first 5 canonical rooms provisioned
  • Timmy account/character provisioned
  • Hermes/Evennia MCP bridge exercised in session 20260328_132016_7ea250
PR opened: #38 Link: http://143.198.27.163:3000/Timmy_Foundation/timmy-home/pulls/38 Verification artifact: - `reports/production/2026-03-28-evennia-world-proof.md` Local proof summary: - Evennia booted successfully on localhost:4000/4001 - first 5 canonical rooms provisioned - Timmy account/character provisioned - Hermes/Evennia MCP bridge exercised in session `20260328_132016_7ea250`
Timmy commented 2026-03-28 17:37:05 +00:00
Author
Owner
Copy Link

Merged in PR #38.

Proof anchors:

Closing #36 as delivered.

Merged in PR #38. Proof anchors: - PR: http://143.198.27.163:3000/Timmy_Foundation/timmy-home/pulls/38 - Verification artifact: `reports/production/2026-03-28-evennia-world-proof.md` - Hermes world-control proof session: `20260328_132016_7ea250` - Local operator web surface verified at `127.0.0.1:4001` Closing #36 as delivered.
Timmy closed this issue 2026-03-28 17:37:05 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
alembic
The Alchemical Vessel - Kimi-powered transformation
 architecture
Auto-created architecture label
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 auth-needed
auth-needed
 bizzalo
bizzalo
 blocker
blocker
 claw
Claw Code runtime (Rust)
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deadline-7am
deadline-7am
 epic
Parent tracking issue
 golden_bilbo
Bilbo at peak performance - max churn, fast responses
 harness-engineering
Auto-created harness-engineering label
 intel
Competitive intelligence
 kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 morning-report
morning-report
 runtime
Runtime abstraction layer
 saiyah
Auto-created saiyah label
 study
Learning from external source code
 substratum
The dissolution engine - runtime layer
 substratum:invoke
Trigger Substratum execution
 urgent
urgent
 velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#36
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?