From c501472f363c5d2ff72e775b0a70d7a8d7a77352 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sun, 7 Jun 2026 05:41:52 +0100 Subject: [PATCH] Record Nightwing embedding offload --- state/evidence.jsonl | 1 + state/map.yaml | 1 + 2 files changed, 2 insertions(+) diff --git a/state/evidence.jsonl b/state/evidence.jsonl index 6b33fc5..840ba11 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -395,3 +395,4 @@ {"ts":"2026-06-07T01:51:40Z","type":"implementation","status":"ok","note":"Repo Persona channel support is now runtime channel-aware: heartbeat prompt assembly discovers guild text channels when INDEX_ALL_CHANNELS is true (or uses INDEXED_CHANNEL_IDS), renders each as a labeled separate conversation such as #therapy/#memes, removes the five-nearby-room cap, and bot/worker Persona ingress/egress gates accept indexed/all-channel grants unless channel ids are excluded. This fixes the single-thread room model by feeding channel identity and access into the context owner instead of adding only a behavior rule."} {"ts":"2026-06-07T03:15:52Z","type":"implementation","status":"ok","note":"Mimir's orphan 'Meet her first' post was not a missing Discord reply-to transport. The child Persona wrote an ambiguous raw Would say, the parent interpreter returned unstructured text instead of an INTERPRETATION/SAY block, and worker routeUnparsedWouldSay bypassed the failed interpreter by manufacturing a current_room SAY with blank reply_to. Removed that fallback; child Would say is candidate material only, and public speech now requires structured parent interpreter output. Added agents:parent-interpreter-boundary-smoke to keep the bypass dead."} {"ts":"2026-06-07T03:54:39Z","type":"implementation","status":"ok","note":"VoidBot swarm Eve dashboard now publishes turnReliability: parent-Interpreter route/retry/drop/malformed counts from model-output log tail plus turn/job failures from heartbeat history, surfaced in CultMesh/Eve and the local HTML HUD."} +{"ts":"2026-06-07T04:38:08Z","type":"implementation","status":"ok","note":"Moved VoidBot RAG embedding inference off Starfire without changing the configured embedder URL: Starfire 127.0.0.1:11434 is now an SSH tunnel to Nightwing Ollama, Nightwing serves qwen3-embedding:0.6b on CPU via GGML_VK_VISIBLE_DEVICES=-1 and OLLAMA_LLM_LIBRARY=cpu_avx2, Starfire Ollama startup shortcut is disabled, and npm run state:check passed with rag_ollama.model reachable."} diff --git a/state/map.yaml b/state/map.yaml index 3076e08..e2b94fb 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -190,6 +190,7 @@ accepted_design: - Deep agent-state, personality, culture, and persistent-world design work now belongs to the sibling Ghostlight repo; VoidBot should consume that work instead of remaining its long-term home. - VoidBot's Verse contract is documented in `docs/architecture/voidbot-verse-service-contract.md`: durable agent/service state should be typed CultCache `.cc` or have a `.cc` witness/export; `voidbot.swarm` currently publishes through `cultmesh://voidbot.local/eve/providers/voidbot.swarm`; target Eve surfaces are `voidbot.discord`, `voidbot.archive`, `voidbot.source`, `voidbot.repo_persona`, and `voidbot.swarm`; static/browser dashboard output is only a lowering, not authority. - `voidbot.swarm` publishes derived turn reliability telemetry in the Eve TUI surface and local HTML lowering. `scripts/render-voidbot-swarm-dashboard.mjs` derives parent-Interpreter route/retry/drop/malformed counts from `.voidbot/logs/model-outputs.jsonl` and turn/job failure counts from repo Persona heartbeat history, then emits the compact `turnReliability` summary in the snapshot, CultMesh publication, and dashboard HUD. + - VoidBot RAG embeddings keep `RAG_OLLAMA_BASE_URL=http://127.0.0.1:11434` as the stable Starfire contract because the URL is part of the current embedder id recorded in Qdrant metadata. The live implementation is an ops-owned SSH tunnel from Starfire loopback `11434` to Nightwing's loopback Ollama `11434`, with Nightwing serving `qwen3-embedding:0.6b` on CPU. Do not change the configured URL unless planning a vector rebuild or metadata migration. - Long-running work should expose durable logs or status files instead of relying on one attached session and hope. - Persistent project memory must stay ruthlessly distilled; git history and artifacts carry routine proof.