Stop repo Face swarm

This commit is contained in:
Meta Vens 2026-05-26 21:40:58 +01:00
commit 80099332df
3 changed files with 16 additions and 18 deletions

View file

@ -16,8 +16,8 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
## Current Shape
- Discord bot and worker are live, and the unattended repo Face / CTB swarm brake was lifted again on 2026-05-26 after the malformed parent-Mind retry fix was committed and pushed.
- The swarm had leaked owner-reply/Mind scaffolding into public Discord twice on 2026-05-26. The first failure wrapped parent Mind in the owner Discord reply prompt and let malformed plain Mind prose become public `SAY`. The second thaw attempt showed the deeper split: malformed parent Mind output caused the worker to ask the Face to revise, and that retry path turned owner-question boilerplate into Bifrost/Nibu `SAY`. The current worker retries malformed Mind output as Mind-owned interpretation, drops to diagnostic private summary instead of re-prompting the Face when Mind stays malformed, and never preserves raw dropped prose as the job summary. `scripts/inspect-model-output-logs.mjs` now flags repo-face parent interpreter records missing an `INTERPRETATION` decision. The post-fix thaw queued Bifrost, Fensalir, and Mimir through normal CTB heartbeats; all three posted through webhook, and live model-output inspection reported zero warnings. Keep watching the next unattended turns for parent-Mind shape and public speech leaks.
- The Discord bot listener is live, but the unattended swarm is down as of 2026-05-26: `state/agent-swarm-paused.json` is paused, the `GameCult Local Orchestrator` scheduled task is disabled, the worker process is stopped, and CTB active-load residue has been cleared.
- The swarm had leaked owner-reply/Mind scaffolding into public Discord twice on 2026-05-26. The first failure wrapped parent Mind in the owner Discord reply prompt and let malformed plain Mind prose become public `SAY`. The second thaw attempt showed the deeper split: malformed parent Mind output caused the worker to ask the Face to revise, and that retry path turned owner-question boilerplate into Bifrost/Nibu `SAY`. The current worker retries malformed Mind output as Mind-owned interpretation, drops to diagnostic private summary instead of re-prompting the Face when Mind stays malformed, and never preserves raw dropped prose as the job summary. `scripts/inspect-model-output-logs.mjs` now flags repo-face parent interpreter records missing an `INTERPRETATION` decision. A post-fix thaw queued multiple Face turns and live model-output inspection reported zero warnings, but the operator then explicitly ordered the swarm brought all the way down.
- The teardown authority remains `notes/agent-swarm-teardown-plan-2026-05-21.md`, but it is now a restart checklist and smell ledger rather than a stop sign. Keep using it when a Face/Bifrost/CTB boundary smells like prompt/parser/transport Jenga.
- The repo-controlled pause flag is `state/agent-swarm-paused.json`. While it is missing or has `"paused": false`, swarm runners may operate. While it has `"paused": true` or is malformed, the Face heartbeat runner skips and the orchestrator skips agent-swarm organs. This is the brake. Do not route around it.
- Postgres owns jobs, audit events, interaction memory, and rate-limit state.
@ -36,7 +36,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
- Prompt-facing rumination chronology is projected by `scripts/lib/void-rumination-context-projection.ps1`. Exact timestamps stay in typed state/status/cursors; the child context gets relative phrases like `5 minutes ago`, including recent Discord messages, repo activity, receipts, memory timestamps, and sleep/speech timing.
- `scripts/simulate-void-mood.mjs` owns typed sleep/speaking-pressure over `.voidbot/private/void-self-state.cc`. During sleep, it invokes typed memory maintenance once per nap unless that nap already completed a pass; use `--skip-memory-maintenance` for smoke runs that must not call Codex.
- `npm run moderation:memory-maintenance:sleep-fixture` now proves the non-skip sleep path without spending a live model call: it seeds a temporary `.cc`, forces mood drift through sleep maintenance, uses a fake Codex child to propose `apply_memory_distillation`, and verifies short-term residue is gone while the durable memory keeps subject, claim, tension, action implication, and anchor.
- The live local pulse is now one hidden scheduled task: `GameCult Local Orchestrator`. It invokes repo Face CTB heartbeats, repo Face memory maintenance, Void mood drift, Void moderation rumination, and the operations watchdog with one lock, one status surface, per-organ logs, and per-organ timeouts. The Bifrost dispatch organ remains wired but is skipped unless `BIFROST_DISPATCH_ENABLED=true`. The repo Face memory-maintenance organ is deliberately not blocked by `state/agent-swarm-paused.json`; pause silences public swarm mouths, but Life still cleans state. The old per-organ tasks are disabled and should remain disabled unless testing one organ in isolation.
- The local pulse owner is one hidden scheduled task: `GameCult Local Orchestrator`. It invokes repo Face CTB heartbeats, repo Face memory maintenance, Void mood drift, Void moderation rumination, and the operations watchdog with one lock, one status surface, per-organ logs, and per-organ timeouts when it is enabled. As of the explicit 2026-05-26 shutdown, that task is disabled and should not be re-enabled without operator approval. The Bifrost dispatch organ remains wired but is skipped unless `BIFROST_DISPATCH_ENABLED=true`. The repo Face memory-maintenance organ is deliberately not blocked by `state/agent-swarm-paused.json`; pause silences public swarm mouths, but Life still cleans state when the orchestrator is running. The old per-organ tasks are disabled and should remain disabled unless testing one organ in isolation.
- `scripts/start-voidbot-stack.ps1` now treats the local Bifrost container stack as a startup dependency. It reads `BIFROST_ROOT` and `BIFROST_HEALTH_URL`, runs `E:\Projects\Bifrost\compose.local.yaml` when the health endpoint is down, and records the result under `runtime-stack.json` as `bifrost`.
- `npm run moderation:rumination:fixture` proves the non-skip typed rumination branch without spending a live model call: it seeds a temporary `.cc`, routes the runner through a fake Codex child, and verifies short-term memory, incubation, agency pressure, and candidate intervention proposals are parent-applied typed operations with no exact timestamp leakage in the prompt-facing context.
- `npm run moderation:rumination:speech-fixture` proves queued speech has a parent-owned action loop: fake Codex queues one candidate with a delivery target, fake Discord send writes a receipt, and the parent runner marks the candidate spoken through typed state. The child prompt now forbids direct send-script calls.

View file

@ -1,5 +1,5 @@
{
"paused": false,
"reason": "Operator explicitly thawed the repo Face swarm after malformed parent Mind retry routing was fixed, verified, committed, and pushed.",
"updatedAt": "2026-05-26T20:23:33.250Z"
"paused": true,
"reason": "Operator explicitly stopped the repo Face swarm after live thaw.",
"updatedAt": "2026-05-26T20:37:19.387Z"
}

View file

@ -14,19 +14,17 @@ objective:
Aetheria lore, while keeping the system understandable enough to modify
safely.
current: >
Keep the repo Face swarm live but under close watch after the 2026-05-26
Mind/owner-reply leaks. The second thaw attempt proved malformed parent Mind
Keep the unattended swarm down after the 2026-05-26 Mind/owner-reply leaks
and the subsequent live thaw. The repo Face pause flag is active, the
GameCult Local Orchestrator scheduled task is disabled, the worker process is
stopped, and CTB active-load residue has been cleared; the Discord bot
listener remains up. The second thaw attempt proved malformed parent Mind
output was being treated as a Face retry, allowing owner-question boilerplate
to become public Bifrost/Nibu SAY. The worker now treats malformed Mind
output as Mind-owned retry/drop and the model-output inspector flags
interpreter records missing INTERPRETATION decisions. After the fix was
committed and pushed, a live thaw queued Bifrost, Fensalir, and Mimir through
normal CTB heartbeats; all three posted through webhook and live
model-output inspection reported zero warnings. Bifrost work routing remains
paused because the governance bridge proved too disorienting for live social
traffic. Parent Mind has a slimmer semantic prompt with a hard DSL contract:
interpret natural Face thought, decide route/retry/drop, and emit only
explicit STATE NOTE, ARTICLE, or SAY blocks for side effects.
interpreter records missing INTERPRETATION decisions, but the swarm should
not be restarted without an explicit operator order and a controlled live
verification plan.
constraints:
- Public traffic still rides one remote Qwen box plus local embedding and ops infrastructure.
@ -63,10 +61,10 @@ data_flow:
- keep persistent state lean enough that re-entry sharpens the next turn instead of drowning it
active_subgoals:
- Treat `notes/agent-swarm-teardown-plan-2026-05-21.md` as the historical teardown authority and the restart checklist. The repo Face swarm is live again after the 2026-05-26 owner-reply/Mind leaks, including the second thaw failure where malformed parent Mind output was converted into public owner-question SAY. Keep watching for controlled evidence that the scheduler, prompt, model-output logs, parent Mind retry/drop ownership, and worker side-effect rails still have explicit observable boundaries before adding new swarm features.
- Treat `notes/agent-swarm-teardown-plan-2026-05-21.md` as the historical teardown authority and the restart checklist. The repo Face swarm is currently down after the 2026-05-26 owner-reply/Mind leaks and live-thaw flood: pause flag active, orchestrator disabled, worker stopped, bot listener still up. Restart only by explicit operator order with controlled evidence that the scheduler, prompt, model-output logs, parent Mind retry/drop ownership, and worker side-effect rails still have explicit observable boundaries.
- Make the new project-state surfaces the default continuity path for nontrivial VoidBot work.
- Keep the rebuilt moderation/self-state foundation on canonical CultCache `.cc` typed operations, never an editable JSON working projection.
- Keep the typed moderation, mood, repo Face, and watchdog organs behind the single `GameCult Local Orchestrator` scheduled pulse; the per-organ scheduled tasks are legacy installer surfaces and should stay disabled unless a deliberate isolation test needs one. Bifrost dispatch is disabled by default behind `BIFROST_DISPATCH_ENABLED=false` until the governance bridge is rebuilt cleanly. As of the 2026-05-21 restart, the orchestrator task is enabled and is the live swarm pulse owner.
- Keep the typed moderation, mood, repo Face, and watchdog organs behind the single `GameCult Local Orchestrator` scheduled pulse when the swarm is deliberately running; the per-organ scheduled tasks are legacy installer surfaces and should stay disabled unless a deliberate isolation test needs one. Bifrost dispatch is disabled by default behind `BIFROST_DISPATCH_ENABLED=false` until the governance bridge is rebuilt cleanly. As of the explicit 2026-05-26 shutdown, the orchestrator task is disabled and must not be re-enabled without operator approval.
- Keep legacy moderation mirrors, whole-state projection commits, and deleted memory-organ compensators from re-entering the active path before adding more moderation, mood, agency, or public-lane behavior.
- Keep public-lane limits, moderation, and provider behavior constrained enough that one 4060 Ti box does not get flayed for sport.
- Preserve boring observability and startup discipline around Postgres, Qdrant, Ollama, Docker, backups, scheduled tasks, watchdogs, and any private local fire-signal extensions.