[META] migrate all persistent storage to hero_db (replace direct redis usage)

mik-tf commented

2026-05-06 17:07:17 +00:00

Owner

Overview

hero_db is the canonical persistent store across the Hero stack — encrypted-at-rest KV / graph / vector / stream, the "AI memory store". Several services still talk to redis directly or roll their own sqlite. This META tracks the audit + per-service migration so every service that needs permanent storage uses hero_db.

Why

Meeting 2026-05-06: "_db everywhere we need permanent storage" / "hero_db is the _redis".

One persistence story across the stack — matches the "Per-context everything" design principle.
Encrypted at rest by default; redis is not.
Removes the cognitive load of "which store does this service use?" when debugging.

Existing concrete redis-leak: hero_skills#185 — service_livekit hardcodes redis port 6379.

Audit checklist (fill in per service)

hero_proc — uses hero_db for what?
hero_proxy
hero_collab
hero_biz
hero_archipelagos
hero_logic
hero_agent / hero_memory
hero_voice
hero_books
hero_indexer / hero_embedder
hero_router
livekit (via hero_skills)

For every NO, file a sub-issue Migrate persistent storage to hero_db in that repo and link here.

Acceptance

Audit complete (every service in the workspace ticked)
Sub-issues filed for every "no"
No direct redis-server dependency in any tracked repo
docs_hero page on using hero_db from a hero_* service

Skill: hero_db
hero_memory#1 — implement hero_memory (consumer)

Source: meeting notes 2026-05-06.

## Overview `hero_db` is the canonical persistent store across the Hero stack — encrypted-at-rest KV / graph / vector / stream, the "AI memory store". Several services still talk to redis directly or roll their own sqlite. This META tracks the audit + per-service migration so every service that needs permanent storage uses `hero_db`. ## Why Meeting 2026-05-06: "_db everywhere we need permanent storage" / "hero_db is the _redis". - One persistence story across the stack — matches the "Per-context everything" design principle. - Encrypted at rest by default; redis is not. - Removes the cognitive load of "which store does this service use?" when debugging. Existing concrete redis-leak: [hero_skills#185](https://forge.ourworld.tf/lhumina_code/hero_skills/issues/185) — service_livekit hardcodes redis port 6379. ## Audit checklist (fill in per service) - [ ] hero_proc — uses hero_db for what? - [ ] hero_proxy - [ ] hero_collab - [ ] hero_biz - [ ] hero_archipelagos - [ ] hero_logic - [ ] hero_agent / hero_memory - [ ] hero_voice - [ ] hero_books - [ ] hero_indexer / hero_embedder - [ ] hero_router - [ ] livekit (via hero_skills) For every NO, file a sub-issue `Migrate persistent storage to hero_db` in that repo and link here. ## Acceptance - [ ] Audit complete (every service in the workspace ticked) - [ ] Sub-issues filed for every "no" - [ ] No direct `redis-server` dependency in any tracked repo - [ ] `docs_hero` page on using `hero_db` from a hero_* service ## Related - Skill: `hero_db` - [hero_memory#1](https://forge.ourworld.tf/lhumina_code/hero_memory/issues/1) — implement hero_memory (consumer) Source: meeting notes 2026-05-06.