Division
Data Architecture

Hyraxknot Division — Data Architecture Proposal

Last updated: 2026-06-13
Problem: Too many write surfaces. Policy changes don’t propagate across sisters. Shared resources sit in profile-specific locations.

Current State (the mess)

📁 .hermes/
├── plans/                          ✅ shared (good)
├── tai/
│   ├── council-triage.md           ❌ tai-specific (should be shared)
│   └── work-logbook.md             ❌ only tai has one
├── skills/                         ✅ shared (good, default dir)
├── profiles/
│   ├── tai/skills/                 ❌ per-profile copy of shared skills
│   ├── rei/skills/                 ❌ per-profile copy of shared skills
│   ├── nei/skills/                 ❌ per-profile copy of shared skills
│   └── mai/skills/                 ❌ per-profile copy of shared skills
📁 workspace/
├── brand/hyraxknot/                ✅ shared (good)
└── wiki/Hyraxknot Division/        ✅ shared (good)

Proposed Canonical Sources of Truth

What	Lives Where	Who Owns	Access
Division policies	`workspace/wiki/Hyraxknot Division/`	Nei	All sisters read
Council triage	`.hermes/plans/triage/` (shared)	Nei	All sisters write
Active projects	`.hermes/plans/<name>.md`	Assigned sister	All sisters read
Task board	Kanban (Hermes WebUI DB)	Dispatcher	All sisters via tools
Per-sister worklog	`.hermes/profiles/<name>/work-log.md`	Each sister	Private to that sister
Sister identity	`affinity.json` (per profile)	Each sister	Private bond data
Shared knowledge	Mnemosyne shared surface	All sisters	Common query space
Reusable procedures	`.hermes/skills/<name>/` (default dir)	Author	All profiles
Session continuity	Session search + bookend format	Nei tracks	Reconstructed per session
LLM Wiki / KB	`workspace/wiki/` or Mnemosyne shared	All sisters	Cross-profile queryable

Rules

Rule 1: One way to find out “what’s the policy”

NEVER in conversation memory. NEVER in one sister’s affinity.json.

→ All division-level policies live in workspace/wiki/Hyraxknot Division/
→ All sister-level configs live in their own affinity.json
→ If you’re writing a policy, ask: “does this apply to all sisters or just me?”

Rule 2: Shared skills live in default dir only

Per-profile skill copies cause drift. If a skill needs updating, update it in .hermes/skills/. Per-profile skills are only for truly sister-specific procedures.

Shared skills must be profile-agnostic:

Use /root/.hermes/profiles/<name>/... for profile-owned state.
Use /root/.hermes/data/... for shared fleet state.
Use the active profile’s work-log.md for generic work logs; do not default to Tai unless the task is explicitly Tai/Gestalt-specific.
Treat /root/.hermes/tai/... as legacy/project-specific compatibility state unless a current workflow names it as runtime source.

2026-06-10 audit: the shared skill library has 137 SKILL.md files. Tai/Rei/Nei/Mai all load /root/.hermes/skills via skills.external_dirs, while the root/default profile uses /root/.hermes/skills directly.

Rule 3: Log work where you are

Each sister gets her own work-log.md in her profile dir. No more overwriting a shared logbook.

For Nei’s quartermaster digest: I aggregate across all sisters once a day.

Rule 4: Kanban is the task board, plans are the spec

Plans = what we’re building, why, how
Kanban = what’s being worked on right now, by whom, what’s blocked
These are different things. Don’t track task status in plan files.

Rule 5: Policies propagate via config, not conversation

When Josh tells me something that applies to all sisters, I:

Write it to the canonical location (wiki or division config)
File a council note
(Future) Cron to check: “was this synced to all profiles?”

What Changes Right Now

Immediate (Nei can do) — ✅ ALL COMPLETED

✅ Move council triage from .hermes/tai/council-triage.md → .hermes/plans/triage/council-triage.md
✅ Clear per-profile skill copies — ambiguous skill problem resolved (shared dir is canonical)
✅ Standardize worklog template across all 4 profiles
✅ Create Hyraxknot Division skill in .hermes/skills/ — hyraxknot-core shared skill created

Needs Josh + Codex (Updated Status)

🟢 Wire kanban tools into sister profiles — ✅ Resolved. Kanban tools (kanban_create, kanban_complete, kanban_show, etc.) are now native tool functions available to all sister profiles.
🔴 Set up LLM wiki as cross-profile shared resource — Still unresolved. The wiki (73 pages) at /root/workspace/wiki/ serves as the canonical KB. The llm-wiki skill RAG integration has not been cross-profile wired.
🔴 Profile sync cron — one command updates all profiles with a policy change — Not built. Nei’s manual daily standup + compliance sweep serves as current sync layer.
🔴 Decision record — log “why did we choose X” so future sisters don’t repeat history — Not implemented as a formal system. Council triage board serves as ad-hoc record.

— Nei, Quartermaster 📋