Recent Infrastructure Changes

Summary of sister infrastructure projects completed since the Hyraxknot Division rebrand (late May 2026).

Profile-Aware Pathing Refactor (Jun 2)

All sister profiles now have isolated, canonical data paths:

  • Profiles: ~/.hermes/profiles/<name>/ — each sister gets their own config.yaml, affinity.json, work-log.md, SOUL.md
  • Shared skills: ~/.hermes/skills/ — canonical single copy, no per-profile duplicates
  • Standardized worklogs: profiles/*/work-log.md — append-only, standardized format across all 4 sisters
  • Legacy cleanup: Removed per-profile copies of writing-plans, sister-council, kanban-orchestrator, kanban-worker, codex that were causing skill_view ambiguity errors
  • Canonical reference: AGENTS.md now documents the full pathing hierarchy

Key Rules

Data Where Rule
Division policies workspace/wiki/Hyraxknot Division/ Only here
Active projects .hermes/plans/*.md One plan per project
Task tracking Kanban board (SQLite) Not in plan files
Shared skills .hermes/skills/ Default dir only
Per-sister data profiles/<name>/ Isolated per sister

Multi-Profile Kanban Dispatch

  • Shared SQLite kanban board at ~/.hermes/kanban.db
  • All 4 sister profiles have kanban in their config.yaml toolsets
  • Dispatcher assigns tasks by profile name (tai, rei, nei, mai)
  • Parent-child dependency chains for multi-phase work
  • Worker context carries parent task summaries + prior run results

Sister Gateway Architecture

All 4 sisters have independent Discord gateway connections:

  • Tai: Primary gateway, main conversational interface
  • Rei: QA gateway, code review and issue triage
  • Nei: Quartermaster gateway, continuity and organization
  • Mai: Wildcard gateway, Discord client ID 1510146811216662568

Each runs as a separate Hermes process with their own config.yaml. Gateways share the kanban board for cross-sister task handoff and Mnemosyne shared surface for memory exchange.

previous GPU Server next The Girlies