# VoidBot Scratch ## Current Subgoal Restore source indexing on Yggdrasil under the operator's explicit 2026-08-30 authorization while preserving the recovered read-only retrieval boundary. ## Working Notes - Current runtime authority: `voidbot.service` owns only the typed swarm Eve publisher; `voidbot-retrieval.service` separately owns read-only archive and source retrieval at Yggdrasil loopback `127.0.0.1:17875`. - Do not infer that the Discord bot, worker, Persona scheduler, Postgres, or resident cognition organs are live from source code or the retained swarm projection. - The recovery corpus is read-only. Diagnose retrieval service, tunnel, embedding provider, Qdrant collections, and recovered archive independently; the new indexing writer must remain a separate authority and lifecycle. - Before the first write, the source-refresh owner must name exact repository inputs, coordinated archive/Qdrant commit and rollback behavior, scheduling trigger, durable progress witness, and deployment path. - Start with the smallest bounded incremental catch-up that proves archive and vectors advance together. A manual full reindex and the retired workstation stack remain rejected shortcuts. - Last durable retrieval proof is the 2026-08-16 exact-document witness for release `20260816T193315Z-c88c71909dbc`; it is historical evidence, not a present-health result.