diff --git a/notes/fresh-workspace-handoff.md b/notes/fresh-workspace-handoff.md index 4a7c8b1..d6ab6f6 100644 --- a/notes/fresh-workspace-handoff.md +++ b/notes/fresh-workspace-handoff.md @@ -162,7 +162,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 paused through `state/agent-swarm-paused.json`. Do not restart it by momentum. When the operator is ready, restart deliberately under observation and check whether new turf/status/consultation events produce character-specific projected pressure and durable state through ordinary turns. +- 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. - 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 840c8da..7c50180 100644 --- a/state/agent-swarm-paused.json +++ b/state/agent-swarm-paused.json @@ -1,7 +1,7 @@ { - "paused": true, - "reason": "Operator requested swarm shutdown before reboot. Social-pressure repair landed: heartbeat projection now surfaces raw relationship/status provocations so resentment, rivalry, and territorial tension can emerge through projector/Face/Interpreter instead of manual state injection. Keep paused until deliberately restarted under observation.", + "paused": false, + "reason": "Operator requested swarm restart after global doctrine and Face prompt inheritance updates. Restart deliberately under observation; watch topic saturation, social tension, source-channel routing, and Face prompt behavior.", "pausedAt": "2026-05-23T12:31:04.330Z", - "resumedAt": null, + "resumedAt": "2026-05-24T02:11:38.839Z", "lastPausedAt": "2026-05-23T12:31:04.330Z" } diff --git a/state/evidence.jsonl b/state/evidence.jsonl index 2e20c09..5d96f7d 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -308,3 +308,4 @@ {"ts":"2026-05-23T19:16:23Z","type":"implementation","status":"ok","note":"Repo Face topic saturation is now identity-aware. The heartbeat assembler classifies a saturated current-room topic as home-adjacent or another steward's gravity well using the Face's own identity/jurisdiction text, feeds that into both the child prompt and state-projector packet, and the Interpreter retries non-owner same-topic politeness unless it becomes a handoff, boundary, frustration, pivot, or silence. Prompt assembly verified Aqua sees the Aetheria/Parallax orbit as foreign crowding while Nibu sees it as home-adjacent but still stale without fresh anchors."} {"ts":"2026-05-23T19:22:52Z","type":"implementation","status":"ok","note":"Cut the live Face projector/Interpreter scar-tissue bans into a causal diagnosis model. The projector no longer carries meltdown-specific forbidden-token instructions, and the Interpreter no longer names failure-specific gates; it now reasons over missing freshness, ownership, correction uptake, reader context, social purpose, and stale topic gravity."} {"ts":"2026-05-24T01:58:06Z","type":"implementation","status":"ok","note":"Repo Face prompts now include the loaded global Codex AGENTS.md as a full inherited doctrine block near the top of the child prompt. Prompt assembly verified Nibu receives PRIME DIRECTIVE, The Great Colossus, and Epiphany sections from C:/Users/Meta/.codex/AGENTS.md."} +{"ts":"2026-05-24T02:14:42Z","type":"ops","status":"ok","note":"Thawed state/agent-swarm-paused.json and manually pulsed GameCult Local Orchestrator for repo-face-heartbeats. The pulse ran successfully, queued Void moderation, resynced CTB wall-clock initiative, and left repo Faces active under idle cooling with Bifrost dispatch still disabled."} diff --git a/state/map.yaml b/state/map.yaml index 817cc52..aa3516f 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -14,14 +14,14 @@ objective: Aetheria lore, while keeping the system understandable enough to modify safely. current: > - Keep the repo Face swarm online under watch after the 2026-05-21 teardown + Keep the repo Face swarm online under watch after the 2026-05-24 deliberate restart, with Bifrost work routing paused because the governance bridge proved too disorienting for live social traffic. The immediate priority is - to harden the Face/Interpreter/speech boundary with live evidence: live-room - conversation must arrive as raw transcript evidence, typed social state must - become live person-hooks when recent speakers match, no structured action - truncation, no fake channel ids, no owner-DM leakage, and no premature - dispatch machinery. + to observe the Face/Interpreter/speech boundary with live evidence: inherited + global doctrine should appear in Face prompts, live-room conversation should + arrive as raw transcript evidence, typed social state should become live + person-hooks when recent speakers match, and topic gravity should produce + character-specific pressure instead of another swarm obsession loop. constraints: - Public traffic still rides one remote Qwen box plus local embedding and ops infrastructure. @@ -250,5 +250,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 remains 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. The immediate social-state projection gap exposed by Nibu/Void has been patched: raw relationship-pressure evidence now reaches the projector before Face turns. - next_action: When the operator is ready, restart the swarm deliberately under observation. Check that topic saturation, source-channel routing, and organic social tension all behave; specifically watch whether new turf/status/consultation events produce character-specific projected pressure and later durable STATE NOTEs without manual typed-state injection. + summary: VoidBot's bot/worker/provider/RAG/Postgres/Qdrant/CultCache structure is live, and the repo Face swarm was deliberately thawed on 2026-05-24 by setting state/agent-swarm-paused.json paused=false. GameCult Local Orchestrator remains the single pulse owner; a manual repo-face-heartbeats pulse succeeded, resynced CTB wall-clock initiative, and queued Void moderation. Bifrost work routing remains paused by default. + next_action: Observe the restarted swarm under normal orchestrator pulses. Check that inherited global doctrine appears in Face prompts, topic saturation/source-channel routing behave, and new turf/status/consultation events produce character-specific projected pressure plus durable STATE NOTEs without manual typed-state injection.