From a016eb6534f23b4408eafd01659cea6989776741 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Wed, 3 Jun 2026 01:46:32 +0100 Subject: [PATCH] Clarify Face speech pause status --- state/map.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/state/map.yaml b/state/map.yaml index 6489d36..7769612 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -251,5 +251,5 @@ rejected_paths: reason: sleep/distillation that collapses concrete claims into generic abstraction creates memory nonsense and then forces later cleanup compensators current_status: - summary: VoidBot's bot/worker/provider/RAG/Postgres/Qdrant/CultCache structure is live, but the repo Face swarm is paused after operator-reported silence/code-block public posts. The immediate fault was an obsolete worker fallback that let raw child `Would say:` text write the public mouth when the parent Interpreter did not produce a normalized `SAY`; that fallback has been cut, and transport now rejects full-message markdown fences plus silence markers before Discord posting. GameCult Local Orchestrator remains the single pulse owner, and the repo Face heartbeat path obeys `state/agent-swarm-paused.json`. Bifrost work routing remains paused by default. + summary: VoidBot's bot/worker/provider/RAG/Postgres/Qdrant/CultCache structure is live, but the repo Face swarm is paused after operator-reported silence/code-block public posts. The immediate fault was an obsolete worker fallback that let raw child draft speech write the public mouth when the parent Interpreter did not produce a normalized SAY block; that fallback has been cut, and transport now rejects full-message markdown fences plus silence markers before Discord posting. GameCult Local Orchestrator remains the single pulse owner, and the repo Face heartbeat path obeys `state/agent-swarm-paused.json`. Bifrost work routing remains paused by default. next_action: Keep the swarm paused until a dry/mock repo Face turn proves public speech is owned only by parent Interpreter `SAY` blocks, raw child silence/code-fence text cannot bypass the Interpreter, and the repaired worker build is the running worker. Then resume ordinary orchestrator pulses cautiously and watch first live posts.