Pause swarm before reboot

This commit is contained in:
Meta Vens 2026-05-23 13:32:22 +01:00
commit 84d5b91469
3 changed files with 8 additions and 7 deletions

View file

@ -1,7 +1,7 @@
{
"paused": false,
"reason": "Resumed after adding repo Face room-topic saturation projection and Interpreter gating.",
"pausedAt": "2026-05-22T18:00:20.1264989Z",
"resumedAt": "2026-05-23T09:29:00.134Z",
"lastPausedAt": "2026-05-23T09:23:05.653Z"
"paused": true,
"reason": "Operator requested swarm shutdown before reboot; next repair should make social tension such as resentment emerge from projected relationships instead of manual injection.",
"pausedAt": "2026-05-23T12:31:04.330Z",
"resumedAt": null,
"lastPausedAt": "2026-05-23T12:31:04.330Z"
}

View file

@ -300,3 +300,4 @@
{"ts":"2026-05-22T23:30:18Z","type":"fix","status":"ok","note":"Refined the Huginn side-thread repair: older side-thread revival is allowed when it is reader-legible. Repo Face transcript rendering now includes message IDs, and Face/Interpreter prompts require a reply_to anchor, explicit context in the content, or a bridge to the live topic before routing an older-thread SAY."}
{"ts":"2026-05-23T09:27:47Z","type":"implementation","status":"ok","note":"Repo Face topic saturation now projects current-room repeated-topic pressure into Face prompts and Interpreter routing, so semantic loops can be advanced, closed, pivoted, or kept private instead of continuing as locally-valid variants."}
{"ts":"2026-05-23T10:09:54Z","type":"fix","status":"ok","note":"Void moderation rumination now preserves recent Discord message channel ids and projects a latest recentConversationTarget, so Aquarium-shaped replies can target the source channel instead of falling back to the configured public/general room."}
{"ts":"2026-05-23T12:31:47Z","type":"ops","status":"ok","note":"Repo Face swarm paused before operator reboot. Next repair should make social tension and resentment emerge from relationship/state projection and recent events, not require manual state injection after the fact."}

View file

@ -246,5 +246,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, and the repo Face swarm has been restarted after the 2026-05-21 teardown pass. `GameCult Local Orchestrator` is enabled as the single pulse owner; watchdog, mood, moderation, and repo Face CTB organs have all completed healthy post-restart pulses. Bifrost work routing is paused by default.
next_action: Keep the swarm awake under live observation, with special attention to whether the new current-room topic saturation signal breaks the overnight lore attractor without forbidding good worldbuilding, and whether Void now replies in the channel that supplied the conversation instead of defaulting Aquarium-shaped replies into general.
summary: VoidBot's bot/worker/provider/RAG/Postgres/Qdrant/CultCache structure is live, but the repo Face swarm is deliberately paused through `state/agent-swarm-paused.json` before the operator reboot. `GameCult Local Orchestrator` remains the single pulse owner; paused Face heartbeats should skip without queuing turns. Bifrost work routing is paused by default.
next_action: After reboot, do not simply wake the swarm by momentum. First repair the social-state projection gap exposed by Nibu/Void: resentment, rivalry, status offense, and territorial tension should emerge from recent events plus personality/state projection, not require manual typed-state injection after the fact. Then restart under observation and check that topic saturation, source-channel routing, and organic social tension all behave.