diff --git a/notes/fresh-workspace-handoff.md b/notes/fresh-workspace-handoff.md index 16837bb..8ec01fd 100644 --- a/notes/fresh-workspace-handoff.md +++ b/notes/fresh-workspace-handoff.md @@ -159,7 +159,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou ## Likely Next Bounded Move -- Keep the swarm awake, but watch the logs with suspicion. The restart pass thawed `state/agent-swarm-paused.json`, enabled `GameCult Local Orchestrator`, restarted a fresh bot/worker stack, and verified healthy watchdog/repo Face pulses. The current patch removes repo Face turns from the generic owner-reply wrapper, coerces stray owner-DM aliases back to the live room unless explicitly marked owner-private, pauses Bifrost/governance routing so agents return to open room discussion plus private state pressure, and routes volatile Face state through the actual state projector model before child prompt assembly. +- Keep the repo Face swarm paused until the heartbeat timeout/cadence boundary is repaired. On 2026-06-09, a health pass cleared stale `GameCult Local Orchestrator` locks, restarted the VoidBot stack so bot/worker `dist` entrypoints were fresh, verified Postgres/Qdrant/Ollama/Discord/local backup health, and regenerated the swarm dashboard/CultMesh snapshot. Scheduled repo-face-heartbeats then repeatedly exceeded the orchestrator window and killed the `gpt-5.4` state-projector child, so `state/agent-swarm-paused.json` is set to `"paused": true`. Do not thaw it until state projection has a bounded turn budget, cheaper/deferred path, or other coherent timeout fix, and a scheduled pulse proves clean. - The 2026-05-22 live retry confirmed role/name mention obligations can wake multiple newborn Faces from one human intro. Mimir, Huginn, Weksa, and Kiko all posted through the repo identity webhook path. If a Face speaks with its name but no avatar, inspect `.voidbot/private/repo-discord-identities.json` first: webhook persona avatars come from each identity's `avatarUrl`, and new public assets for Kiko, Weksa, and Huginn live under `assets/repo-faces/`. - Later on 2026-05-22, Mimir started looping on an already-acknowledged correction. Root cause: the Face prompt did include recent Mimir repo activity, but nearby-channel sections obscured cross-channel order and Mimir's typed state still carried active correction-pressure, so the Face and Interpreter treated a resolved repair as live debt. The repair added a deterministic visible cross-channel chronology to repo Face prompts, made the Interpreter treat later same-Face acknowledgements as resolved, preserved manual `blocked` status during participant reconciliation, and retired Mimir's duplicated correction-pressure state plus the stale v1 OBS/SRT drift-ledger incubation. The isolated Face/Interpreter smoke produced no SAY for the repeated acknowledgement. - Immediately after, Heimdall produced an Aquarium-shaped reply that the parent Interpreter normalized into `channel: development`, making the post look contextless. Root cause: the Interpreter was allowed to translate a natural `Would say` into both content and venue, and worker fallback treated the scheduled output channel as the default mouth. The repair makes conversation channel ownership deterministic: `SAY` defaults to `current_room`, `current_room` resolves to `job.guildContext.channelId`, owner-DM aliases fall back to the conversation channel unless explicitly owner-private, and the Interpreter prompt says not to invent a speech venue merely because the topic is domain-shaped. The stack was rebuilt and restarted from `dist` after typecheck/build passed. @@ -170,7 +170,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou - The overnight 2026-05-23 run showed a softer version of the previous loop: Faces did not collapse into nonsense, but the Aquarium room stayed captured by the Nibu-origin/faction lore seam for hours. Existing `saturationScore` lived on private thought/incubation surfaces, and the repetition prompt mostly caught copied openings/endings, not semantic topic attractors. The heartbeat prompt now projects current-room topic saturation from repeated raw-transcript terms and estimates whether the attractor is home-adjacent or another steward's gravity well from each Face's identity/jurisdiction text. The state projector should turn foreign attractors into character-specific crowding, neglect, boredom, rivalry, handoff, or pivot pressure; the Interpreter diagnoses non-owner same-topic politeness as missing personal stake, ownership, freshness, handoff, or pivot rather than applying a topic ban or token blacklist. - Void's broader moderation authority had become venue leakage: recent-history projection stripped `channelId`, leaving the configured `publicSpeechTarget` as the obvious place for replies, so Aquarium-shaped talk could land in `#general`. The rumination context now preserves message `channelId` and projects `recentConversationTarget`; prompt doctrine says source-channel replies belong in that source channel, while `publicSpeechTarget` is for unanchored herald/artifact announcements. - The Nibu/Void turf-crossing discussion exposed a social-state projection gap: existing bonds/status reads project well once typed state already contains them, but the live pipeline did not own "this recent event should become relationship/status pressure." The repair adds bounded raw relationship-pressure evidence to the state packet before the projector: recent messages that touch the Face, peer Faces, existing social targets, jurisdiction/domain terms, or status/territory/consultation language. The projector may turn that evidence into tentative felt pressure, and the Interpreter may persist a bond/status/mood note only when the projected memory or Face output shows a character-specific reaction. This should let resentment, rivalry, consultation offense, and territorial tension emerge without manual state edits. -- The swarm is currently online again through `state/agent-swarm-paused.json` with `"paused": false`. It was restarted deliberately on 2026-05-24 after global doctrine inheritance landed. Keep it under observation: check topic saturation, source-channel routing, inherited global doctrine in Face prompts, and whether turf/status/consultation events produce character-specific projected pressure and durable state through ordinary turns. +- The swarm is currently paused through `state/agent-swarm-paused.json` with `"paused": true`. It had been restarted deliberately on 2026-05-24 after global doctrine inheritance landed, but the 2026-06-09 health pass showed scheduled Face turns can overrun the orchestrator window inside the `gpt-5.4` state projector. Treat this as an ownership/cadence problem, not a prompt-polish problem: repair the heartbeat budget/projection path before resuming ordinary turns. - Direct Face `UPDATE REQUEST` and `BIFROST TOPIC` packets are ignored while `REPO_FACE_BIFROST_ENABLED=false`. Do not debug missing Bifrost jobs as a live failure unless that flag has been deliberately enabled again. - Live model-facing prompt prose has started moving out of executable code. The shared loader is `packages/shared/src/prompt-template.ts`; extracted prompt surfaces live under `prompts/`, including repo Face turn/reviewer prompts, provider wrapper prompts, situational social read prompts, source-grounding reminders, consensus-feed prompts, and repo Face model-smoke scenarios. Code should project data and select prompt names; prompt files should own behavioral prose. - Identity collapse has started. Active bot, worker, MCP repo-identity tools, and Face CTB scheduler paths now load through the canonical Face registry and treat repo Discord identities as compatibility projections. Next bounded move is to finish removing remaining direct conceptual dependence on repo identities, then split the Face turn loop into scheduler, context assembler, prompt renderer, candidate parser, policy gate, and transport adapter. diff --git a/state/agent-swarm-paused.json b/state/agent-swarm-paused.json index b3f173d..6a83c8d 100644 --- a/state/agent-swarm-paused.json +++ b/state/agent-swarm-paused.json @@ -1,5 +1,5 @@ { - "paused": false, - "reason": "Resumed after live inspection showed the code-block report referred to pre-repair Discord messages; the public Face mouth now also normalizes inline Markdown code spans before Bifrost posting.", - "updatedAt": "2026-06-03T01:52:05.1079871Z" + "paused": true, + "reason": "Paused by Codex on 2026-06-09 after scheduled repo Face heartbeat repeatedly exceeded the orchestrator window and killed the gpt-5.4 state-projector child. Bot, worker, retrieval, and typed state are healthy; autonomous Face turns need timeout/cadence repair before resuming.", + "updatedAt": "2026-06-09T14:26:00.0000000Z" } diff --git a/state/evidence.jsonl b/state/evidence.jsonl index cc46829..ef999d7 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -337,3 +337,4 @@ {"ts":"2026-06-09T04:16:41Z","type":"operations","status":"ok","note":"2026-06-09 quiet-swarm check: repo Face heartbeat was open but idle-cooling selected 0 participants; GameCult Local Orchestrator was wedged by stale moderation-heartbeat codex child PID 45160 under heartbeat PID 43212/orchestrator PID 42736. Stopping the stale child let heartbeat fail/cleanup, next pulse recovered, repo-face heartbeat/mood/heartbeat/rumination completed ok. Bifrost intake hot path failed separately with defineDocumentType is not a function in E:/Projects/Bifrost/tools/agent-transport.mjs."} {"ts":"2026-06-09T04:49:33Z","type":"implementation","status":"ok","note":"Naked human-posted URLs now remain visible to Void rumination as recentRoomLinks even after the moderation heartbeat advances the safety cursor. GameCult blog URLs resolve to gamecult-site source refs; unanswered URL messages carry forward until a speech receipt replies to that message. Verified with the 2026-06-08 week-of-nonconsensual-access URL: no-post rumination queued a direct reply, parent SkipModel delivery posted it, and the new receipt suppresses repeat handling."} {"ts":"2026-06-09T14:17:35Z","type":"documentation","status":"ok","note":"Documented r/GameCultOrg as the GameCult subreddit: Bifrost owns Reddit thread/post transport and receipts; Void owns moderation judgment there using the same baseline public-community posture as Discord."} +{"ts":"2026-06-09T14:26:13Z","type":"operations","status":"warning","note":"2026-06-09 swarm health pass: cleared stale GameCult Local Orchestrator locks, restarted stack to refresh stale worker, verified bot/worker/Postgres/Qdrant/Ollama/Discord/local backup, then paused repo Face swarm because scheduled repo-face-heartbeats repeatedly exceeded the orchestrator window and killed the gpt-5.4 state-projector child. Leave autonomous Face turns paused until timeout/cadence repair."} diff --git a/state/map.yaml b/state/map.yaml index 13f153a..12efd41 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -258,5 +258,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 resumed after the silence/code-block public-post fault. Public speech is now owned by parent Interpreter SAY blocks: the obsolete raw child draft-speech fallback is cut, silence markers and full-message markdown fences are rejected at the transport boundary, and inline Markdown code spans are normalized to quoted human text before Bifrost posting. Live inspection after the follow-up operator report showed the visible code-block examples were pre-repair Discord messages, not fresh post-boundary output. GameCult Local Orchestrator remains the single pulse owner, and the repo Face heartbeat path still obeys `state/agent-swarm-paused.json`. Bifrost work routing remains paused by default. - next_action: Watch the next live moderation heartbeat under GameCult Local Orchestrator: it should run every pulse, classify only against rules plus infringement history, and leave any public announcement to Void's normal rumination/CTB turn. + summary: VoidBot's bot/worker/provider/RAG/Postgres/Qdrant/CultCache structure is live, and the 2026-06-09 health pass refreshed the stale worker, verified the live stack, regenerated the swarm dashboard/CultMesh snapshot, and refreshed the local backup. Autonomous repo Face turns are paused through `state/agent-swarm-paused.json` because scheduled repo-face-heartbeats repeatedly exceeded the orchestrator window and killed the gpt-5.4 state-projector child. GameCult Local Orchestrator remains the single pulse owner; with the pause gate set, it should skip swarm organs instead of attempting public Face turns. Bifrost work routing remains paused by default. + next_action: Repair the repo Face heartbeat timeout/cadence boundary before resuming the swarm: identify why state projection can exceed the orchestrator window, add a bounded turn budget or cheaper/deferred projection path, then verify a scheduled pulse completes with `state/agent-swarm-paused.json` set back to false.