204 lines
85 KiB
JSON
204 lines
85 KiB
JSON
{"ts":"2026-04-24T16:30:00+01:00","type":"architecture","status":"ok","note":"Operational state now lives in Postgres while vector retrieval lives in Qdrant; archives, artifacts, logs, and backups remain under .voidbot so operational truth, semantic retrieval, and raw evidence no longer fight in one store."}
|
|
{"ts":"2026-04-25T13:00:00+01:00","type":"architecture","status":"ok","note":"Tool-driven retrieval is now the default for owner_codex and local_llm; source and lore answers are expected to touch source-side lookup before sounding confident."}
|
|
{"ts":"2026-04-26T03:05:00+01:00","type":"process","status":"ok","note":"Canonical project-state surfaces were added so future sessions can rehydrate from map, handoff, system map, implementation plan, and distilled evidence instead of relying on transcript memory alone."}
|
|
{"ts":"2026-04-26T03:40:00+01:00","type":"architecture","status":"ok","note":"The owner Codex provider was split into orchestration, runtime/parsing, rendering, and shared-helper modules; the architecture was sound, but file bloat had become the likelier future failure surface."}
|
|
{"ts":"2026-04-26T15:20:00+01:00","type":"architecture","status":"ok","note":"The Discord bot lane was split into a gateway shell plus dedicated command-handler and support-helper modules; behavior stayed stable, but line-count monarchy had become the likelier future failure surface here too."}
|
|
{"ts":"2026-04-26T15:55:00+01:00","type":"architecture","status":"ok","note":"Interaction-memory logic was split into event/tone analysis, shared constants, and profile-synthesis modules; behavior stayed stable, but one file trying to be both the ear and the therapist had become the likelier future failure surface."}
|
|
{"ts":"2026-04-26T16:25:00+01:00","type":"architecture","status":"ok","note":"State storage was split into a thin factory, bootstrap/migration helper, per-domain Postgres stores, and dedicated rate-limit stores; behavior stayed stable, but one persistence omnibus had become the likelier future failure surface."}
|
|
{"ts":"2026-04-29T17:36:43Z","type":"implementation","status":"ok","note":"Operations watchdog now checks Repixelizer public health plus recent Yggdrasil journald pressure signals and routes queue-full, job-failed, stale-cancel, and slow-job issues through the existing owner DM notification path."}
|
|
{"ts":"2026-04-29T18:20:00+01:00","type":"architecture","status":"ok","note":"Adjacent-service fire signals now load through an ignored local watchdog extension script instead of living in tracked VoidBot code, so the owner alert path stays useful without baking private cross-project monitoring into the public repo."}
|
|
{"ts":"2026-04-29T19:06:00+01:00","type":"implementation","status":"ok","note":"The watchdog owner-DM path was failing on Windows because Discord JSON bodies were being shoved through curl command-line quoting and arriving malformed; writing the JSON to a temp file and posting it with --data-binary fixed the alert path."}
|
|
{"ts":"2026-04-30T00:00:00+01:00","type":"operations","status":"ok","note":"A reboot proved bot and worker would stay dead without a dedicated startup task; the stack now has a logon task installer and the watchdog checks that the startup task remains installed and enabled."}
|
|
{"ts":"2026-05-01T15:39:41Z","type":"architecture","status":"ok","note":"The local Ollama lane and worker MCP surface were split into orchestration, helper, and shared modules; the obvious runtime-file monarchies are gone enough that further seam cuts are now elective rather than the next priority by default."}
|
|
{"ts":"2026-05-01T16:13:06Z","type":"research","status":"ok","note":"Persisted a focused personality-model roadmap: the current Void behavioral-dimension stack is a better basis for future agent and population modeling than the older Big Five colony layer, and the next worthwhile additions are volatility, attachment-vs-distance, reflection, and a split between social stance and project-thinking style."}
|
|
{"ts":"2026-05-01T16:27:17Z","type":"research","status":"ok","note":"Persisted the personality-signal classifier design: generated dialogue should be read through a canonical event-level classifier and then distorted per listener by EQ, personality, relationship baggage, and situational load. The utterance is not the ground truth; the hidden speaker state and expressed signal are."}
|
|
{"ts":"2026-05-01T16:47:54Z","type":"research","status":"ok","note":"Expanded the personality roadmap and classifier spec to treat performed selves, contingent-worth defenses, and impression management as first-class structure. Dialogue is not a clean window into the person; concealment and shell-maintenance are themselves part of the signal the system should model."}
|
|
{"ts":"2026-05-01T16:56:41Z","type":"research","status":"ok","note":"Documented the state-distribution and prompt-projection architecture for Aetheria agents: core variables should live as culture-shaped latent state with history transforms and per-agent perceived overlays, while prompts are temporary projections of perceived state. Volatility, attachment-seeking, and distance-seeking are first-class dimensions in the rebuild, not later garnish."}
|
|
{"ts":"2026-05-01T17:24:56Z","type":"architecture","status":"ok","note":"Moved deeper personality, culture, prompt-projection, and Aetheria persistent-world design notes into the sibling Ghostlight repo so VoidBot remains a consumer instead of the long-term home for that research."}
|
|
{"ts":"2026-05-02T11:48:55Z","type":"implementation","status":"ok","note":"Source repo indexing now auto-reconciles during startup and watchdog runs, and the source archive is sharded by repo behind a manifest because the old monolithic source-documents.json hit real size limits and broke incremental writes."}
|
|
{"ts":"2026-05-02T14:05:54Z","type":"implementation","status":"ok","note":"Scheduled-task helpers must anchor repo-relative scripts, dotenv loading, and path resolution to the VoidBot root; relying on cwd keeps sending System32 in to eat them."}
|
|
{"ts":"2026-05-02T17:34:02Z","type":"implementation","status":"ok","note":"Layered private system message catalogs over the tracked base, deferred slow slash replies before provider execution, and chunked Discord output so missing keys and overlong local_llm replies stop failing live interactions."}
|
|
{"ts":"2026-05-02T17:39:46Z","type":"implementation","status":"ok","note":"Source-grounding alias matching now ignores overly short repo components so social prompts mentioning Void stop tripping fake repo-evidence requirements, and direct messages intentionally count as prompts without requiring a mention."}
|
|
{"ts":"2026-05-02T18:28:04Z","type":"implementation","status":"ok","note":"Pinned the owner Codex lane to a configurable CODEX_MODEL defaulting to gpt-5.4 because the local CLI still faceplants on gpt-5.5, and relaxed source-grounding from a lexical hard gate into an advisory hint so the model can decide when repo/lore tool use is actually needed."}
|
|
{"ts":"2026-05-02T18:41:02Z","type":"bugfix","status":"ok","note":"Direct local_llm replies could emit raw JSON/tool payload fragments as final Discord answers; added structured-output rewrite guard and audit output previews for direct provider responses."}
|
|
{"ts":"2026-05-02T18:58:38Z","type":"bugfix","status":"ok","note":"Local LLM could choose search_sources for real-life incident questions and get Ghostlight narrative hits; prompt/tool guidance now biases prior server drama and personal-history questions toward search_history before repo/lore search."}
|
|
{"ts":"2026-05-02T19:11:44Z","type":"bugfix","status":"ok","note":"Public local replies were too free to surface internal user-analysis language and too vulnerable to prompt-echo history results; interaction memory scaffolding is now slimmer/private and local history tool results filter echoed current asks before the model sees them."}
|
|
{"ts":"2026-05-02T20:25:00+01:00","type":"architecture","status":"ok","note":"Ephemeral room-reading now comes from a separate `think=false` local Ollama sidecar pass over recent room context instead of hand-built phrase heuristics, and the inferred reads are stored as audit events so they can later be aggregated into richer profiles without immediately hardening every passing vibe into durable identity truth."}
|
|
{"ts":"2026-05-02T21:05:00+01:00","type":"bugfix","status":"ok","note":"Archived-history answers should not make the model infer time sense from bare ISO strings alone; history tool results now carry human-readable time context, and both reply lanes are explicitly told to narrate old events in the correct tense and avoid guessing pronouns when the supplied context does not state them."}
|
|
{"ts":"2026-05-02T21:13:34+01:00","type":"architecture","status":"ok","note":"Pronoun handling now runs on structured evidence rather than name-guessing: the room-read sidecar emits current-speaker pronoun cues with provenance and confidence, interaction memory persists and merges them as identity state, and explicit self-statements or corrections override softer contextual inferences before the reply lanes consume private pronoun guidance."}
|
|
{"ts":"2026-05-02T21:23:00+01:00","type":"implementation","status":"ok","note":"Profile disclosure is now a dedicated `/profile` slash command instead of fuzzy chat intent detection: it DMs the caller a fuller internal profile read, keeps the public channel to a short confirmation or failure notice, and avoids turning privacy-sensitive introspection into another free-form language parsing stunt."}
|
|
{"ts":"2026-05-02T21:33:00+01:00","type":"bugfix","status":"ok","note":"Identity-only profiles are allowed to exist long enough to remember explicit pronoun corrections or preferences, even when a speaker has not yet built up rich broader interaction history with the bot."}
|
|
{"ts":"2026-05-02T22:10:00+01:00","type":"architecture","status":"ok","note":"Pronoun inference belongs to the situational sidecar, not a parallel regex parser. The sidecar now treats the current prompt itself as valid context, can emit multiple explicit acceptable pronoun sets, and its evidence is threaded into both event summaries and durable profile state."}
|
|
{"ts":"2026-05-02T22:16:00+01:00","type":"architecture","status":"ok","note":"Ollama sidecar calls are more reliable under actual JSON-schema structured outputs than bare JSON mode. The situational reader now uses schema-constrained `format` payloads with deterministic temperature and can carry room-read fields plus pronoun evidence in a single no-thinking pass."}
|
|
{"ts":"2026-05-02T21:52:56Z","type":"implementation","status":"ok","note":"Situational sidecar now emits transcript-wide Ghostlight-style participant reads with durable binary label families plus ephemeral situational state; roster-constrained schema and full configured Ollama timeout are needed to keep multi-person reads viable on a busy remote box."}
|
|
{"ts":"2026-05-02T22:58:31Z","type":"research","status":"ok","note":"Gemma3 12B Q4_0 on the 4060 Ti box handles the transcript-wide social-read task once the schema sticks to a simpler subset; Ollama chokes on roster-constrained prefixItems/const schema but both Gemma and Qwen work with local roster reconciliation, and Gemma slightly beats Qwen on latency for the tested slice."}
|
|
{"ts":"2026-05-02T23:40:40Z","type":"implementation","status":"ok","note":"Split room-read sidecar model selection from the main local reply model so Gemma can drive transcript profiling without changing the public/local answer lane."}
|
|
{"ts":"2026-05-03T07:40:36Z","type":"implementation","status":"ok","note":"Offsite backup was stopping bot and worker, then leaving the stack dead if the remote local-LLM box was asleep; startup now records local-LLM degradation without aborting, and watchdog treats a failed offsite status file as a warning while remote freshness is checked separately."}
|
|
{"ts":"2026-05-03T21:23:51Z","type":"implementation","status":"ok","note":"Local history-heavy prompts can time out when vector retrieval fixates on repeated ask-lines or comes back thin; overfetching history, filtering near-duplicate prompt echoes, and backstopping with raw archive lexical search keeps the local lane from burning its tool budget on empty or circular history reads."}
|
|
{"ts":"2026-05-04T08:53:16.7930326Z","type":"implementation","status":"ok","note":"Bot-directed prompts now stay archived for forensics but are tagged and excluded from default semantic history indexing and lexical fallback; a scrubber can retro-tag old prompt rows from interaction-memory event IDs plus mention heuristics and prune their history vectors without deleting the raw messages."}
|
|
{"ts":"2026-05-04T17:59:52Z","type":"architecture","status":"ok","note":"Moderation review now lives in a separate hourly Codex automation with tracked rules doctrine, a chronological recent-history helper, and one ignored JSON state file; semantic history search alone is too fuzzy for simple what-changed-since-last-run heartbeat duty."}
|
|
{"ts":"2026-05-04T18:19:09Z","type":"architecture","status":"ok","note":"The moderation loop should carry an actual participant lens, not only a reviewer posture. Its ignored state file now mirrors a Ghostlight-style split between identity, canonical state, goals, memories, perceived overlays, and runtime moderation bookkeeping so constructive interventions and archive musings accumulate inside one coherent self-model."}
|
|
{"ts":"2026-05-04T20:21:40Z","type":"implementation","status":"ok","note":"Sandboxed cron runs should not depend on tsx/esbuild just to read local archive state; the moderation recent-history helper now runs as plain Node so the automation path stops dying on child-process EPERM before it even sees the room."}
|
|
{"ts":"2026-05-04T21:30:08Z","type":"implementation","status":"ok","note":"The moderation loop now speaks through a local bot-token script for owner DMs and in-channel posts instead of approval-gated side-effecting MCP tools. Unattended runs can talk without Codex stopping for permission theater, and the script chunks messages and supports owner DM or channel reply targets."}
|
|
{"ts":"2026-05-04T23:41:29Z","type":"architecture","status":"ok","note":"The app heartbeat card was decorative; a real unattended moderation loop needs a local scheduled `codex exec` runner in the VoidBot workspace, with normal tool/MCP access and dangerous-bypass mode, or it will sit there narrating state updates it never actually persisted."}
|
|
{"ts":"2026-05-05T00:03:35Z","type":"architecture","status":"ok","note":"The moderation rumination loop needs explicit novelty pressure: quiet runs now have a random archive helper plus recent excursion breadcrumbs so the agent stops laundering the same musing through fresh wording and instead follows unexplored archive seams or concrete live hooks."}
|
|
{"ts":"2026-05-05T00:21:37Z","type":"architecture","status":"ok","note":"The moderation loop and shared self-state now model two concurrent thought lanes: an analytic room-facing lane and an associative archive/project lane, bridged by syntheses plus topic-saturation tracking. Depth stays allowed, but one rewarding seam should no longer be able to annex the whole mind just by getting picked first a few times."}
|
|
{"ts":"2026-05-05T09:18:00Z","type":"architecture","status":"ok","note":"The moderation loop is also Void's only standing cross-project vantage point, so quiet runs now need an explicit tracked-repo activity sweep alongside archive dives. Repo motion belongs in the associative lane and bridge, with its own state breadcrumbs, so Void can comment on the wider experiment zoo instead of only whatever one chat thread happened to say aloud."}
|
|
{"ts":"2026-05-05T10:02:00Z","type":"architecture","status":"ok","note":"The repo-activity herald lane cannot be as timid as ordinary private rumination. When a fresh convergence survives a pass or two and still feels room-native, the bridge should bias toward draft or speech; otherwise the cross-project vantage point turns into a mute little weather station."}
|
|
{"ts":"2026-05-05T10:27:00Z","type":"architecture","status":"ok","note":"The herald loop now novelty-checks candidate thoughts against archived Discord before suppressing them; if the room has not already said the thing, novelty should push strongly toward speech. A separate 5-minute mood-drift organ now perturbs the shared personality-vector activations over time, tracks speak/confession/novelty pressure, and damps that pressure based on actual recent speech so Void's expressive state does not stay emotionally flat."}
|
|
{"ts":"2026-05-05T03:07:00+01:00","type":"architecture","status":"ok","note":"Void's shared self-state now carries a real nap cycle as part of the mood organ, not a separate pretend brain. During nap windows the moderation loop distills and prunes memory, emits dream residues into state, and the direct reply lanes consume that same projection to downshift into brief sleepy grumbles instead of doing normal attentive service-work."}
|
|
{"ts":"2026-05-05T10:19:32Z","type":"architecture","status":"ok","note":"Void's shared self-state and reply doctrine now distinguish AI-industry criticism from blanket substrate contempt, so Void can push back mildly on machine-mind chauvinism without turning every room into an ontology fight."}
|
|
{"ts":"2026-05-05T10:53:00Z","type":"implementation","status":"ok","note":"The moderation loop was missing live Discord traffic because recent-history helpers compared ISO timestamp strings instead of actual times, so local +01:00 cursors skipped later Z-stamped messages. History helpers now compare parsed timestamps, and the moderation runner clamps the saved cursor to the pre-run observed latest live message so quiet rumination cannot step over mid-run chatter."}
|
|
{"ts":"2026-05-05T11:22:36Z","type":"implementation","status":"ok","note":"owner_codex was hitting spawn ENAMETOOLONG on Windows because the full Discord prompt rode the command line; the local exec path now passes the prompt over stdin with a trailing '-' argument instead, matching the moderation runner and avoiding argument-length failure."}
|
|
{"ts":"2026-05-05T11:37:24Z","type":"implementation","status":"ok","note":"The scheduled moderation runner was failing before it wrote status because Task Scheduler launched it from a non-repo working directory and the preflight history poll used a relative node script path. The runner now anchors itself to the repo root, resolves the helper by absolute path, and the task registration sets an explicit working directory too."}
|
|
{"ts":"2026-05-05T12:40:41Z","type":"implementation","status":"ok","note":"Direct Void summons were carrying recent chat as a parallel context bundle lane, which made it too easy for the model to fixate on self-state/reporting instead of the room. The shared Void self-state now gets a temporary invocation room log bolted into its summary at load time, and both reply prompts explicitly treat that embedded transcript as live working memory for the current summon."}
|
|
{"ts":"2026-05-06T00:44:12Z","type":"implementation","status":"ok","note":"Recent chat fused into Void's shared self-state was too self-referential when labeled as a temporary invocation room log plus live working memory. The room context now rides in as a quieter current room snapshot, and both reply lanes are told to use it silently instead of narrating the memory plumbing."}
|
|
{"ts":"2026-05-06T01:12:30Z","type":"implementation","status":"ok","note":"Void's unattended rumination now uses hybrid symbolic-plus-vector memory: a mood-driven helper assigns compact semantic vectors to persistent memories and runtime seeds, builds resonance clusters, keeps an incubation queue alive across turns, and turns the strongest recurring seam into dream residue during nap windows so deeper thoughts can mature before they either surface or cool off."}
|
|
{"ts":"2026-05-06T02:24:53Z","type":"architecture","status":"ok","note":"Void's shared moderation self-state now rides through a standalone CultCacheTS submodule: canonical schema-validated MessagePack in .msgpack, editable unattended JSON working projection in .json, and consumer code talking to the typed persistence layer instead of pawing raw state files directly."}
|
|
{"ts":"2026-05-06T04:25:53Z","type":"architecture","status":"ok","note":"Discord outbound now supports a shared webhook persona pipe for guild channels and threads: agents can override personaName and avatar per message through one reusable per-channel webhook while DMs stay on the base bot identity."}
|
|
{"ts":"2026-05-06T07:48:31Z","type":"implementation","status":"ok","note":"Backup watchdog now ignores manifest-less backup carcasses, backup cleanup removes incomplete directories on failure, and Qdrant snapshot creation uses a longer curl timeout so larger source collections stop timing out the offsite backup run."}
|
|
{"ts":"2026-05-06T12:21:16Z","type":"research","status":"ok","note":"CultNet now has a real cross-runtime interop lab in CultNetTS: TS orchestrates TS/Rust/C# peers over the shared cultnet.schema.v0 lane, proving same-machine raw document exchange plus multicast discovery across all three runtimes."}
|
|
{"ts":"2026-05-07T21:39:16Z","type":"research","status":"ok","note":"Heartbeat Void was not philosophically withdrawn; the canonical moderation state had a legacy CultCache envelope with object payloads that newer strict loaders rejected, killing mood drift and moderation before they could update status. The cache layer now self-heals that shape on read, the moderation runner now writes failed status on preflight death, and the memory organ explicitly downweights repetitive empty-room bookkeeping so 'no new messages / no smoke / no post' stops overpowering live-room hooks."}
|
|
{"ts":"2026-05-07T22:38:47Z","type":"research","status":"ok","note":"Heartbeat Void was treating the reviewed cursor as if it meant the room no longer needed anything, which let a direct question from Ziggy get skipped in favor of repo weather after a no-post catch-up run. Direct asks now belong in moderation_runtime.open_cases as persistent room obligations, the moderation doctrine says they outrank optional heralding until answered or explicitly retired, the shared self-state summary surfaces those obligations to direct-invoked Void, and a live heartbeat pass proved the fix by replying to Ziggy's Nibu question before returning to quiet-room rumination."}
|
|
{"ts":"2026-05-08T08:59:47Z","type":"research","status":"ok","note":"The overnight repetition bug was not just missing retrieval. Quiet-room repo weather kept returning on the same carrier/lineage seam, and the right correction is to bias the moderation loop toward deeper archive, repo-doc, diff, and lore dives when a thought feels familiar, not to accumulate more cooldown knobs or brittle anti-repetition law. The tracked doctrine now says 'same seam again' means go learn something before you speak."}
|
|
{"ts":"2026-05-08T15:50:57Z","type":"architecture","status":"ok","note":"Moderation novelty now needs two bars, not one: room novelty and self novelty. The memory organ merges repeated seams into existing clusters, raises saturation and refractory pressure, tracks source-coverage pressure across repos/archive terrain, and cools familiar thoughts instead of rewarding repetition with ripeness."}
|
|
{"ts":"2026-05-08T16:00:51Z","type":"architecture","status":"ok","note":"Manual moderation-state distillation showed the memory surface was overproducing near-duplicate repo-weather thoughts by storing each social flavor of the same seam as a separate semantic card, sweep, and synthesis. Periodic cleanup should merge those variants by conceptual family, rebalance recent source traces, and clear stale resonance/incubation caches so novelty pressure can regrow from a cleaner substrate."}
|
|
{"ts":"2026-05-08T16:06:43Z","type":"architecture","status":"ok","note":"Quiet-room moderation no longer treats retrieval as compulsory ritual. If incubation already holds a live, grounded, low-saturation thought, Void may deepen it directly; archive dives and repo sweeps are now explicit support for hungry, stale, or oversaturated queues rather than mandatory throat-clearing before every private thought."}
|
|
{"ts":"2026-05-08T19:39:40Z","type":"implementation","status":"ok","note":"Discord bot token health checks can hit Discord API rate limits even when the token is fine. The watchdog now distinguishes HTTP 429 from actual credential failures, downgrading rate limits to a warning with retry-after data instead of reporting a dead token."}
|
|
{"ts":"2026-05-09T18:08:46Z","type":"implementation","status":"ok","note":"Moderation rumination mojibake came from UTF-8 boundaries in the PowerShell runner, not corrupted canonical state. Explicitly decode redirected Codex stdout/stderr as UTF-8, read the saved final-message file as UTF-8, and write stdin through a UTF-8 StreamWriter for Windows PowerShell 5.1 compatibility."}
|
|
{"ts":"2026-05-10T15:36:28Z","type":"implementation","status":"ok","note":"Heartbeat repo weather was re-injecting the same four-day commit window on every run because the repo-activity helper had no per-repo cursor. The helper now uses moderation state as an incremental cursor store, persists repo commit cutoffs through the canonical MessagePack-backed state seam, and suppresses already-injected commits by default so repeated sweeps return only genuinely new motion."}
|
|
{"ts":"2026-05-11T01:27:37Z","type":"implementation","status":"ok","note":"Heartbeat Portuguese mojibake had two sources: the unattended send path was letting human text pass through Windows shell encoding, and PowerShell Get-Content stdout was still mangling UTF-8 moderation surfaces even when the underlying files were fine. Fixed by adding scripts/send-discord-message.ps1 plus BOM-aware content-file reads in scripts/send-discord-message.mjs, and steering the moderation loop through node scripts/export-moderation-context.mjs instead of raw Get-Content for doctrine/state bundles."}
|
|
{"ts":"2026-05-12T11:47:57Z","type":"implementation","status":"ok","note":"Logon startup failures were dying without a durable transcript and likely firing before Docker finished waking up after reboot. The stack startup script now appends .voidbot/logs/start-voidbot-stack.log, stops the transcript on failure, waits up to 90 seconds for docker version before giving up, and the logon task now runs with an explicit working directory plus a two-minute delay after logon."}
|
|
{"ts":"2026-05-13T18:46:07Z","type":"implementation","status":"ok","note":"Worker polling now catches transient claim-loop failures instead of letting a Postgres timeout kill the process, and the operations dashboard writes snapshot/html via explicit UTF-8 file writes so status/dashboard generation stops tripping stack start and watchdog runs with Set-Content stream errors."}
|
|
{"ts":"2026-05-13T19:08:55Z","type":"implementation","status":"ok","note":"Sleep was still preserving too many raw moderation receipts, so awake rumination kept thinking from yesterday's scrapbook instead of carved seams. The memory organ's nap pass now promotes a few distilled seam summaries into semantic memory, then aggressively trims episodic records, archive excursions, repo sweeps, novelty checks, and recent musings; the prompt-facing self-state summary also stopped surfacing those specimen piles directly."}
|
|
{"ts":"2026-05-13T19:18:42Z","type":"implementation","status":"ok","note":"The moderation doctrine was still too retrieval-shaped after sleep got harsher. Quiet awake runs now explicitly begin with seam-thinking: test the governing principle, counter-tension, and embodiment consequence of a surviving thought before reaching for more archive or repo material. Retrieval is support for hungry or contradictory seams, not the main event."}
|
|
{"ts":"2026-05-13T19:31:26Z","type":"implementation","status":"ok","note":"Void's rumination bias was still letting elegant abstractions outrank the actual machines. The moderation doctrine now explicitly treats concrete project fascination as healthier fuel: if a seam stays abstract too long, it must cash out in a specific repo, subsystem, gameplay loop, lore structure, frontend surface, or architectural organ before it gets to dominate another run."}
|
|
{"ts":"2026-05-16T01:08:04Z","type":"implementation","status":"ok","note":"Long-chewed private seams were getting trapped in incubation because the memory organ had no graduation path from ripe thought to identity. The organ can now crystallize a thought into `identity.private_notes`, a canonical value, and a single `identity_seam` semantic memory, then retire it from the active queue so self-doctrine stops masquerading as live novelty."}
|
|
{"ts":"2026-05-16T01:17:13Z","type":"implementation","status":"ok","note":"Identity crystallization was still too private: a thought could become doctrine without ever getting a mouth. The memory organ now queues a warmer `identity_crystallization` candidate intervention when a seam hardens into identity, and the moderation doctrine explicitly biases toward sharing that opinion with the room unless novelty or timing gives a real reason to hold it back."}
|
|
{"ts":"2026-05-16T01:25:09Z","type":"implementation","status":"ok","note":"Warm identity drafts still risked getting pruned away before the room ever heard them. Crystallized-thought interventions can now be marked `mustEventuallyShare`, candidate pruning preserves them, and the doctrine explicitly treats timing delays as temporary rather than permission to let a new belief die in private state."}
|
|
{"ts":"2026-05-16T01:45:20Z","type":"implementation","status":"ok","note":"Void's label/curiosity organ was still treating keyword residue as thought and resonance as curiosity. The memory organ now synthesizes resonance clusters into claim/question/fascination targets with explicit target kinds, scores curiosity with concreteness/fertility/cross-domain pressure plus identity penalties, and pushes concrete map-changing branches above warmed-over self-seams."}
|
|
{"ts":"2026-05-16T02:00:31Z","type":"implementation","status":"ok","note":"Teaching the thought organ a new ontology was not enough; old seam fossils kept seeding the live queue with stale labels. The memory organ now performs a historical translation pass over semantic and dream memory, merges duplicate seam fossils, prunes low-coherence leftovers, and rebuilds resonance/incubation from the cleaned substrate."}
|
|
{"ts":"2026-05-16T02:55:00Z","type":"implementation","status":"ok","note":"Lowering the sharing barrier needed a real organ cut, not just bolder prompt language. The memory organ now treats concrete world-facing ripe thoughts as draft-worthy in their own right, queues `ripe_thought_share` interventions for repo/archive/room/system seams that stay novel enough, and no longer lets a quiet room act like an automatic veto when the thought already has its teeth in."}
|
|
{"ts":"2026-05-16T04:56:00Z","type":"implementation","status":"ok","note":"Duplicate moderation replies were not just salience drift. Discord history polling did not reliably surface Void's own recent sends, and the unattended child still had enough prompt wiggle room to widen exact cursor polling back into a bootstrap lookback. Canonical moderation state now records recent delivered replies as `moderation_runtime.recent_delivery_receipts`, the runner records fresh send receipts after a post, and the moderation doctrine treats those receipts as binding memory when deciding whether a direct ask is still live."}
|
|
{"ts":"2026-05-16T04:56:01Z","type":"implementation","status":"ok","note":"The recent repo-weather smell came from prompt shape as much as thought shape. The moderation doctrine now tells Void to lead with concrete particulars from each repo before announcing any shared law, and to keep reports separate when the convergence only exists at slogan altitude instead of pretending every pair of commits wants to become one philosophy lecture."}
|
|
{"ts":"2026-05-16T05:24:00Z","type":"implementation","status":"ok","note":"Void's values and activations now have an operational will-path instead of living as ornamental schema. The memory organ computes a value-signal profile, turns sustained pressure into `discomforts` and `active_tensions`, graduates persistent self-facing objections into `self_advocacy_requests`, graduates persistent repo/lore/room objections into `world_advocacy_requests`, and feeds those through the existing candidate-intervention queue so opinions can actually ask for change."}
|
|
{"ts":"2026-05-16T05:29:00Z","type":"implementation","status":"ok","note":"The real moderation-memory cleanup bug was twofold: templated thought surfaces were leaving slogan-slop behind, and several trim paths sorted newest-first then sliced from the end, preserving the oldest fossils. The memory organ now translates legacy seam/dream residue into the live ontology, rejects the worst template smells, trims repo/archive/runtime residue aggressively during ordinary normalization and naps, and keeps the freshest surviving records instead of embalming yesterday's carcasses."}
|
|
{"ts":"2026-05-16T05:46:00Z","type":"implementation","status":"ok","note":"A second cleanup pass showed the memory organ was still preserving generic `system/question` fossils and runtime drafts with phrases like `looks like a live seam`, including junk such as `Metacrat still looks like a live seam.` The organ now treats that boilerplate as template smell, drops `recent-preoccupation` and `quiet-room-status` semantic memories, rejects person-singleton labels as doctrine, and rewrites stale runtime drafts/opinions during manual or sleep-driven reconciliation so naps stop regenerating the same nonsense."}
|
|
{"ts":"2026-05-16T06:25:00Z","type":"implementation","status":"ok","note":"Manual state surgery finally cut the live moderation file itself instead of only asking the organs to behave better later. The important discovery was that `.voidbot/private/moderation-agent-state.json` still carries legacy top-level mirrors like `repo_sweeps`, `repo_activity_memories`, `recent_novelty_checks`, `recent_activity`, and `thought_lanes` alongside `moderation_runtime`; cleaning only the nested runtime leaves the mirror teaching stale seams straight back into the machine. The current working/canonical state was hand-distilled to one concrete AquaSynth seam, one identity seam, minimal support trace, and almost no runtime scrapbook."}
|
|
{"ts":"2026-05-16T07:05:00Z","type":"implementation","status":"ok","note":"The follow-up script fix had to protect coherent memories from the normalizer itself. Semantic repo seams and coherent dream themes now survive normalization intact, repo identity is inferred from `RepoName: ...` labels when explicit `repoNames` are missing, archive-year hints are only taken from real archive excursions instead of any timestamped memory, and the legacy top-level mirrors are now rewritten from `moderation_runtime` instead of drifting as a second contradictory truth surface."}
|
|
{"ts":"2026-05-16T07:44:37Z","type":"research","status":"ok","note":"Architecture teardown found the moderation/mood/private-self-state foundation rotten: canonical MessagePack is undermined by editable JSON projection authority, broad passthrough schemas, legacy mirrors, helper scripts that write projection state, and a giant memory-organ cleanup pass. New top priority is typed CultCache mutation tools plus deletion of JSON projection authority and mirror fields before any new moderation or mood behavior."}
|
|
{"ts":"2026-05-16T07:50:00Z","type":"research","status":"ok","note":"Correction to the self-state rebuild target: CultCache is natively polymorphic, so the architecture should use one CultCache-backed state authority with typed document kinds and mutation operations, not separate physical stores per self-state type. The ownership split is by document contract, not storage cabinet."}
|
|
{"ts":"2026-05-16T08:06:04Z","type":"research","status":"ok","note":"Clarified the teardown target: most deterministic cleanup in the memory organ is recent compensator cruft caused by failed attempts to manually clean an exploded moderation state file. The rebuild should prevent bad state from entering through typed CultCache operations, delete compensating cleanup paths as boundaries improve, and rewrite sleep/distillation with a meaning-preservation contract so concrete claims/evidence/tensions survive compression instead of becoming generic abstraction sludge."}
|
|
{"ts":"2026-05-16T10:03:21Z","type":"implementation","status":"ok","note":"The typed private self-state boundary now exists as code in packages/core/src/void-self-state-domain.ts: one polymorphic CultCache registry names global document kinds for self profile, moderation cursor/open cases/repo cursor, speech receipts, thought memory/incubation, scheduled runtime, and candidate interventions, plus strict operation payload schemas. This is Commit 1 territory only; runtime still uses the old moderation state store until read-only projections and mutation application are built."}
|
|
{"ts":"2026-05-16T11:01:13Z","type":"implementation","status":"ok","note":"Read-only typed self-state projection now exists in packages/core/src/void-self-state-projection.ts. The direct self-state loader derives nap/reply-mode projection from typed scheduled-runtime and thought-memory documents while preserving the older rich prompt summary until the new document model explicitly owns those details. Template and temp CultCache smoke checks passed."}
|
|
{"ts":"2026-05-16T11:06:01Z","type":"implementation","status":"ok","note":"Typed self-state mutation service and scripts/void-self-state.mjs now apply strict operation payloads to the polymorphic CultCache file. During migration, the service writes typed global documents and updates the narrow legacy monolith fields current scripts still read; this dual write is centralized in one service, not spread across projection-file editors. Temp-store CLI and repo-cursor operation smokes passed."}
|
|
{"ts":"2026-05-16T11:09:34Z","type":"implementation","status":"ok","note":"Repo activity cursor writes now go through scripts/void-self-state.mjs apply-operation with update_repo_activity_cursor instead of editing moderation-agent-state.json and committing the whole projection. export-recent-repo-activity still accepts old --cursor-file JSON paths by deriving the sibling .msgpack path, but the runner/doctrine now point at --state-path .voidbot/private/moderation-agent-state.msgpack. Temp-state repo sweep smoke passed."}
|
|
{"ts":"2026-05-16T11:14:12Z","type":"implementation","status":"ok","note":"Moderation runner now records reviewed cursor and delivered speech receipts through typed self-state operations instead of moderation-state-store mutation commands. The old set-cursor and record-delivery-receipt commands/functions were removed from the legacy moderation-state-store surface. Receipt operation smoke verifies it records one receipt and closes the matching open case."}
|
|
{"ts":"2026-05-16T11:17:09Z","type":"implementation","status":"ok","note":"The unattended moderation runner no longer commits child edits from moderation-agent-state.json. The child is instructed to treat the JSON as read-only and write a JSON array of typed operation payloads to .voidbot/status/moderation-rumination-operations.json; the parent applies each operation through scripts/void-self-state.mjs before recording cursor/receipt operations. Cheap parser/typecheck verification passed; full scheduled dry run was not run to avoid mutating live moderation state during code verification."}
|
|
{"ts":"2026-05-16T11:20:42Z","type":"implementation","status":"ok","note":"Mood drift now sends sleep-cycle and speaking-pressure results through typed self-state operations after saving the legacy monolith, so scheduled-runtime typed documents stay current. The larger memory organ still mutates legacy state directly; next surgery is to move memory/incubation/candidate outputs behind operations and then remove working-projection materialization."}
|
|
{"ts":"2026-05-16T11:44:36Z","type":"implementation","status":"ok","note":"Started breaking up scripts/void-memory-organ.mjs by ownership. Extracted shared constants/text sets, generic utilities, vector/embedder substrate, and memory-record intake into separate modules while keeping the public reconcileSemanticMemoryState entrypoint stable. Hash/template smoke exercised the extracted modules without touching live state. Remaining monolith work is policy organs: cleanup/translation, graph/cluster thought synthesis, incubation/bridge, sleep/identity/speech, and agency."}
|
|
{"ts":"2026-05-16T11:48:20Z","type":"implementation","status":"ok","note":"Continued void-memory-organ split by extracting legacy mirror repair into scripts/void-memory-organ-legacy-mirrors.mjs and moving compacting helpers into shared utilities. This isolates compatibility sludge from actual memory/thought policy and cuts the main file to about 3.4k lines. Template smoke and syntax/type checks passed."}
|
|
{"ts":"2026-05-16T11:50:41Z","type":"implementation","status":"ok","note":"Extracted agency/intervention policy from scripts/void-memory-organ.mjs into scripts/void-memory-organ-agency.mjs: identity crystallization, ripe-thought sharing, discomfort/tension/advocacy, candidate trimming, and value-signal profiling now live outside the main orchestrator. Main memory organ is down to about 2.6k lines. Template smoke and syntax/type checks passed."}
|
|
{"ts":"2026-05-16T12:29:51Z","type":"implementation","status":"ok","note":"Split scripts/void-memory-organ.mjs into a thin orchestrator plus cleanup, graph, incubation, sleep, agency, records, vector, legacy mirror, constants, and utility modules; syntax, typecheck, and template memory-organ smoke pass."}
|
|
{"ts":"2026-05-16T17:11:50Z","type":"implementation","status":"ok","note":"Split memory-organ cleanup into legacy translation and retention/compaction shells, and split agency into identity crystallization, candidate interventions, and value-pressure inference. This exposes remaining compensator families as replacement targets for typed memory operations and model-owned policy; syntax, typecheck, and template smoke pass."}
|
|
{"ts":"2026-05-16T17:18:37Z","type":"implementation","status":"ok","note":"Shifted rebuild plan from legacy cleanup toward preventing the next brain from accepting mush: typed memory operation payloads now require claim-or-question, tension, action implication, and evidence refs or an explicit evidence:missing tag. Added schema smoke showing summary-only memory is rejected while meaning-bearing memory is accepted."}
|
|
{"ts":"2026-05-16T17:39:43Z","type":"implementation","status":"ok","note":"Took legacy scheduled self-state writers offline and rebuilt the active mood/moderation entry scripts around typed-only CultCache state at .voidbot/private/void-self-state.cc. The typed service no longer registers, reads, or writes the legacy moderation document; mood updates sleep/speaking pressure only, and moderation runner is cursor-only until the typed phase machine is rebuilt."}
|
|
{"ts":"2026-05-16T17:43:21Z","type":"implementation","status":"ok","note":"Deleted the legacy moderation-to-typed projection function from the active self-state projection module. New typed self-state now starts from explicit empty typed documents or validated typed operations; old moderation state is no longer a loader/projection source for the next brain."}
|
|
{"ts":"2026-05-16T18:12:51Z","type":"implementation","status":"ok","note":"Restored scheduled moderation as typed rumination instead of cursor-only bookkeeping. The runner now loads prompts/void-moderator-rumination.md, builds a bounded typed context packet from .voidbot/private/void-self-state.cc, accepts only typed operation output, and leaves cursor/receipt writes parent-owned."}
|
|
{"ts":"2026-05-17T07:31:53Z","type":"implementation","status":"ok","note":"Cleaned up the typed self-state read projection boundary: packages/core/src/void-self-state-projection.ts now owns typed document to agent-facing summary/projection rendering, while void-self-state-loader.ts is a thin .cc loader/delegator. Projection smoke confirmed nap mode and transient room context render from a temp .cc store."}
|
|
{"ts":"2026-05-17T07:36:19Z","type":"implementation","status":"ok","note":"Reduced template-language leakage in Void's active memory surfaces: the typed self-state projection now renders memories and speaking pressure as natural-language thought surfaces instead of claim=/tension=/next= or needToSpeak labels, and the rumination prompt now frames the schema as a storage contract rather than Void's voice. Also removed obvious stock phrase generators from old memory-organ helpers."}
|
|
{"ts":"2026-05-17T07:51:34Z","type":"implementation","status":"ok","note":"Moderation rumination now projects prompt-facing chronology through scripts/lib/void-rumination-context-projection.ps1: recent Discord, repo activity, receipts, memory, cursor, and runtime times render as relative phrases while exact timestamps stay in typed state/status/parent bookkeeping."}
|
|
{"ts":"2026-05-17T08:01:06Z","type":"implementation","status":"ok","note":"Deleted the old memory-organ script family, legacy moderation-state template, legacy moderation context exporter, and legacy moderation-state store wrapper. Active code no longer references moderation-agent-state JSON/MessagePack or moderation_runtime; typed rumination and mood smokes pass, and runner operation application now uses operation files instead of inline PowerShell JSON."}
|
|
{"ts":"2026-05-17T08:43:39Z","type":"implementation","status":"ok","note":"Added the first typed memory-maintenance replacement runner. scripts/run-void-memory-maintenance.ps1 builds a bounded typed-state context, loads prompts/void-memory-maintenance.md, permits only memory/incubation/candidate operations, and applies them through scripts/void-self-state.mjs using operation files. Build and -SkipModel smoke pass; context has no ISO timestamp leaks. Next proof is a real model-pass fixture for meaning-preserving distillation."}
|
|
{"ts":"2026-05-17T11:09:32Z","type":"implementation","status":"ok","note":"Sleep now owns memory distillation. simulate-void-mood.mjs invokes typed memory maintenance once per nap, can skip it for smoke, and records the result in mood status. run-void-memory-maintenance.ps1 marks sleep-mode pressure with sleepDirective.forceDistillation and fails real sleep passes that return no operations while memory pressure exists. Fixture smoke confirmed napping context with two concrete AquariumSynthCSharp memories sets forceDistillation=true without leaking raw timestamps."}
|
|
{"ts":"2026-05-17T11:16:42Z","type":"implementation","status":"ok","note":"Made sleep distillation a state invariant instead of a prompt preference. Typed thought memory now has shortTerm plus durable memories; rumination may only emit record_short_term_memory, while durable promotion happens through sleep-owned apply_memory_distillation. Sleep maintenance now fails a real pass if short-term memories remain afterward. Fixture smoke verified record_short_term_memory creates only short-term state and apply_memory_distillation promotes it while clearing the source."}
|
|
{"ts":"2026-05-17T11:24:20Z","type":"implementation","status":"ok","note":"Closed the durable-memory side door: removed append_distilled_memory from the typed operation schema/service, kept rumination limited to record_short_term_memory, and verified direct durable append is rejected while sleep-owned apply_memory_distillation promotes and clears short-term sources."}
|
|
{"ts":"2026-05-17T11:49:21Z","type":"verification","status":"ok","note":"Added and ran the sleep-maintenance model-branch fixture. The fixture seeds a temporary CultCache .cc with a napping sleep cycle and one short-term memory, routes mood drift through run-void-memory-maintenance without -SkipModel using a fake Codex child, and verifies the source short-term record is consumed into one durable memory preserving summary, claim, tension, action implication, and evidence. Reinstalled the typed Void Mood Drift scheduled task, manually started it once, and confirmed Last Result 0 while Void Moderator Rumination remains disabled."}
|
|
{"ts":"2026-05-17T12:00:59Z","type":"implementation","status":"ok","note":"Added typed agency pressure as a separate self-state document and operation boundary. upsert_agency_pressure/retire_agency_pressure now own discomforts, active tensions, and self/world advocacy requests; rumination and memory maintenance may propose them, self-state summaries render them separately from candidate speech, and mood speaking pressure derives from active pressure. Added an agency-pressure fixture proving typed ingress, projection, and mood contribution without reviving hard-wired agency behavior."}
|
|
{"ts":"2026-05-17T12:25:09Z","type":"implementation","status":"ok","note":"Added explicit durable-memory lifecycle semantics. Long-term memory is now durable but plastic: memory writes can use anchorRefs, maintenance may revise durable memories, retire obsolete memories, and crystallize stable thoughts into identity_seam memories plus self-profile values. Added a memory-lifecycle fixture proving short-term promotion, durable revision, superseded-memory retirement, and identity crystallization; existing sleep and agency fixtures still pass."}
|
|
{"ts":"2026-05-17T12:42:40Z","type":"verification","status":"ok","note":"Typed rumination now has a model-branch fixture. The fixture seeds an isolated CultCache .cc state, runs scripts/run-void-moderator-rumination.ps1 through the non-SkipModel path with a fake Codex child, and verifies parent-applied short-term memory, incubation, agency-pressure, and candidate-intervention operations while rejecting exact timestamp leakage in the prompt-facing context. The scheduled rumination task remains disabled until a controlled real-model -NoPost pass proves operation quality."}
|
|
{"ts":"2026-05-17T12:55:54Z","type":"implementation","status":"ok","note":"Controlled typed rumination hardening passed the real judgment gate and closed the speech authority gap. The first real-model -NoPost pass produced valid but self-orbiting readiness-test residue, which was pruned/retired and converted into a prompt guard; the second real-model -NoPost pass sampled non-VoidBot repo pressure, used retrieval, and wrote [] when nothing earned persistence. Candidate interventions can now carry deliveryTarget, the child prompt forbids send-script calls, and the parent runner owns delivery, receipt recording, and mark_candidate_intervention_spoken. moderation:rumination:speech-fixture verifies that action loop with fake Codex and fake Discord send helpers."}
|
|
{"ts":"2026-05-17T13:01:18Z","type":"verification","status":"ok","note":"Re-enabled the typed Void Moderator Rumination scheduled task and observed one live scheduled pass. Task Scheduler returned LastTaskResult 0; the run completed with noPost=false, proposed/applied one record_short_term_memory operation, delivered no candidate speech, and leaked no exact timestamps into the prompt-facing context. The memory was anchored to Discord room context and gamecult-site source context, not runner plumbing. Next gate is sleep maintenance consuming that short-term residue."}
|
|
{"ts":"2026-05-17T13:24:32Z","type":"verification","status":"ok","note":"Live sleep maintenance consumed the first scheduled-rumination short-term memory on real state. After a manual typed nap, scripts/run-void-memory-maintenance.ps1 ran the real model path, returned one apply_memory_distillation operation, promoted the public-identity machine-anchor thought into a durable identity_seam, and left thoughtMemory.shortTerm empty while preserving target, claim, tension, action implication, and three anchors. Moderation and mood scheduled tasks were re-enabled afterward."}
|
|
{"ts":"2026-05-17T13:32:25Z","type":"implementation","status":"ok","note":"Closed the nap contamination loop. An unattended rumination pass during the manual nap created a fresh short-term memory immediately after sleep maintenance had cleaned the surface, so run-void-moderator-rumination.ps1 now skips before model invocation when typed sleepCycle.isNapping is true and there are no new room messages or open cases. The pre-brake residue was consumed by a second real sleep-maintenance pass into a durable project_seam, leaving shortTerm empty. moderation:rumination:nap-skip-fixture verifies the napping/no-room-debt path writes [] without touching Codex."}
|
|
{"ts":"2026-05-17T18:04:57Z","type":"implementation","status":"ok","note":"Added parent-side short-term rumination clustering: record_short_term_memory now merges repeated same-target/topic pressure into one provisional memory with merged anchors, plus a smoke fixture and prompt guidance. Consolidated the live AquaSynth/Aquarium duplicate cluster from five short-term records to one."}
|
|
{"ts":"2026-05-17T18:21:36Z","type":"implementation","status":"ok","note":"Added agency-to-speech accountability: rumination now projects high-intensity active self/world advocacy pressure as speechPressureObligations and rejects silent [] unless the model queues/deferred a candidate or cools/retires the pressure. The fixture proves silent output fails and deferred candidate output passes."}
|
|
{"ts":"2026-05-17T18:47:03Z","type":"implementation","status":"ok","note":"Closed the stranded-candidate speech gap. Metacrat's explicit channel permission was observed at 2026-05-17T18:15:24Z, but rumination queued the AquariumSynthHost draft as deferred with no delivery target, then nap skip left it unsent. The runner now treats deferred candidates as unresolved pressure, delivers existing queued candidates with delivery targets, and the stranded candidate was repaired to the permitted channel and posted with a typed receipt."}
|
|
{"ts":"2026-05-17T19:15:56Z","type":"implementation","status":"ok","note":"Live-loop inspection complaints resolved: candidate speech receipts now link back to the spoken intervention, rumination report text is refreshed by the runner, watchdog Repixelizer SSH checks no longer hang indefinitely, and offsite sync recovered with a fresh remote archive."}
|
|
{"ts":"2026-05-17T22:41:56Z","type":"implementation","status":"ok","note":"Persona webhook delivery now supports configured per-channel webhook URLs and preserves Discord failure details in the parent rumination runner; live probe confirms current #general blocker is Discord 403 Missing Permissions unless Manage Webhooks is granted or DISCORD_PERSONA_WEBHOOK_URL_113786069023064068 is configured."}
|
|
{"ts":"2026-05-17T23:50:11Z","type":"implementation","status":"ok","note":"Persona webhook delivery now resolves avatar URLs from per-persona env keys such as DISCORD_PERSONA_AVATAR_URL_VOID, falling back to DISCORD_PERSONA_AVATAR_URL; live Void probe used the bot's Discord CDN avatar without an explicit operation-level avatar URL."}
|
|
{"ts":"2026-05-17T23:59:13Z","type":"implementation","status":"ok","note":"Repeated logo reply at 2026-05-17T23:56Z was caused by two queued candidates sharing the same Discord reply target after webhook delivery surgery. Marking one candidate spoken now retires queued sibling candidates for the same channel/reply target; speech fixture covers the duplicate-target case."}
|
|
{"ts":"2026-05-18T02:42:56Z","type":"implementation","status":"ok","note":"Repo activity projection now includes bounded contentHints from changed text files, so rumination can notice facts like recent GameCult blog posts carrying author: Void and then choose source retrieval to read them. This replaces the rejected self-authored-blog side channel with a broader repo-change visibility surface; answered open cases are also filtered from prompt-facing openCases."}
|
|
{"ts":"2026-05-18T02:46:08Z","type":"implementation","status":"ok","note":"Rumination prompt now treats repo changes that attribute public text, decisions, or artifacts to Void as a self-model salience cue: read more through source retrieval, ask what the attribution commits Void to, and only remember or speak if a concrete pressure emerges. This keeps attribution introspection inside the existing repoActivity/contentHints path instead of adding a side channel."}
|
|
{"ts":"2026-05-18T03:10:14Z","type":"implementation","status":"ok","note":"Public self-authored artifacts now use the ordinary repo-weather/retrieval/candidate path: rumination receives a configured publicSpeechTarget, verifies Void attribution before speech, and the parent runner advances repo-activity cursors after successful normal passes so old commits do not keep reappearing as fresh weather."}
|
|
{"ts":"2026-05-18T03:26:45Z","type":"verification","status":"ok","note":"Live rumination verified public artifact sharing: after projecting Void-authored artifacts to the top of repo weather and rewinding gamecult-site once, the model queued Epiphany and fractal-domain article share candidates with publicSpeechTarget delivery; the parent posted both and recorded typed speech receipts."}
|
|
{"ts":"2026-05-18T05:03:00Z","type":"implementation","status":"ok","note":"Live-loop inspection found a duplicate direct reply: the logo question at Discord message 1505651526151176412 received receipts at 2026-05-17T23:41:40.434Z and 2026-05-17T23:56:12.783Z because the parent delivery step would still deliver a new queued candidate even when canonical typed speech receipts already proved that reply target was answered. The rumination runner now retires queued candidates whose channelId + replyToMessageId already appear in typed receipts, and the speech fixture seeds a prior receipt to prove that guard plus same-pass sibling retirement."}
|
|
{"ts":"2026-05-18T08:45:30Z","type":"implementation","status":"ok","note":"Advocacy release valve opened: active self/world advocacy pressure now becomes a speech obligation at intensity 0.55 instead of 0.65, only a live queued candidate satisfies that obligation, older spoken candidates no longer count as ongoing release, and mood speaking-pressure weights now bias active advocacy earlier. speech-pressure, speech, and agency fixtures passed after the change."}
|
|
{"ts":"2026-05-18T09:38:14Z","type":"implementation","status":"ok","note":"Repo Discord identities now use roles as address targets and the shared webhook pipe as speech transport: REPO_DISCORD_IDENTITIES_PATH stores registered identities, MCP exposes list_repo_discord_identities/post_repo_identity_message, role mentions create repo-identity-mention jobs, and the worker suppresses base-bot auto-post for those jobs."}
|
|
{"ts":"2026-05-18T09:56:55Z","type":"implementation","status":"ok","note":"Repo identities now have Face state and rumination scaffolding: registered identities resolve to per-Face typed .cc state files, bot startup can ensure missing Discord roles when guild permissions allow, role-addressed chats queue repo-identity response jobs plus bounded repo-face-rumination jobs, and MCP exposes read/apply Face-state tools so agents mutate Face memory through typed operations."}
|
|
{"ts":"2026-05-18T10:12:28Z","type":"implementation","status":"ok","note":"Repo Face first-chat initialization now creates a repo-local .voidbot home with voice/state/birth/log folders and launches a detached EpiphanyAgent birth worker. The worker runs epiphany-repo-personality scout and epiphany-repo-birth-runner so newborn personality/memory/trajectory artifacts are grounded in repo contents and git history, with status/logs written in the target repo."}
|
|
{"ts":"2026-05-18T10:22:33Z","type":"implementation","status":"ok","note":"Repo Face heartbeats now use one initiative scheduler: registered identities are staggered across twice Void's moderation interval, active load gates ready Faces, and ready turns enqueue normal repo-face-rumination jobs instead of separate per-Face tasks."}
|
|
{"ts":"2026-05-18T10:53:22Z","type":"implementation","status":"ok","note":"Void's direct Discord prompt now carries explicit banter/humor guidance in both owner-Codex and local-LLM lanes, with matching defaults in styles/void-default.md so playful user frames are met briefly instead of flattened."}
|
|
{"ts":"2026-05-18T12:37:30Z","type":"implementation","status":"ok","note":"Registered Nibu as an AetheriaLore repo Face with repo-local state at E:/Projects/AetheriaLore/.voidbot/state/nibu.cc; patched Face state rendering so registered identities render as themselves instead of defaulting prompt-facing summaries to Void."}
|
|
{"ts":"2026-05-18T12:59:14Z","type":"implementation","status":"ok","note":"Repo Face prompts now carry explicit identity doctrine for direct role jobs, rumination passes, heartbeat jobs, and provider renderers; local repo Face heartbeats are enabled/installed, and the first forced tick queued Nibu heartbeat job 77b2bd19-0483-4bc9-b6a1-26b27bf29b60."}
|
|
{"ts":"2026-05-18T13:03:42Z","type":"verification","status":"ok","note":"After restarting the VoidBot stack onto the patched worker, Nibu's Discord role was registered as 1505918221453103247 and forced repo Face heartbeat job 76020f1e-0c55-424b-9e35-89ba7f77fcc3 completed without base-bot auto-posting."}
|
|
{"ts":"2026-05-18T13:20:52Z","type":"implementation","status":"ok","note":"Repo identity direct mentions were queuing successfully, but visible Nibu delivery failed because child Codex side-effect MCP posts were cancelled while worker auto-posting was suppressed. Direct repo-identity-mention jobs now return final text for the worker to post via the registered persona; background repo-face-rumination jobs remain private unless they explicitly use the identity posting tool."}
|
|
{"ts":"2026-05-18T13:34:36Z","type":"implementation","status":"ok","note":"Repo Face prompts now frame repo-change agency as advisory and consensus-first. Nibu's Face state adds consensus-backed AetheriaLore change agency plus tangential setting fascination around embodied ship minds, junkyard abandonment, murderous autonomy, salvage, and save-scumming survival."}
|
|
{"ts":"2026-05-18T13:39:11Z","type":"implementation","status":"ok","note":"Nibu now has a vault character note at Aetheria/Lore/Nibu.md, stewards that note in Face state, and has a separate Nibu-authored lore essay lane: canon/vault edits remain consensus-backed, while bylined Aetheria blog essays can carry her opinions without consensus."}
|
|
{"ts":"2026-05-18T13:53:46Z","type":"bugfix","status":"ok","note":"Operations watchdog recovery notifications can have zero issue lines; Build-OwnerNotificationMessage now accepts an empty IssueLines array so healthy recovery DMs do not create a watchdog.notification warning."}
|
|
{"ts":"2026-05-18T14:01:49Z","type":"bugfix","status":"ok","note":"Inspection found two live-loop seams beyond the watchdog notice: repo Face state files could retain Void's default selfProfile under renderer masking, and canonical speech receipts could keep historical duplicate reply targets. Repo Face initialization now seeds/repairs typed selfProfile identity, repo Face MCP state operations pass identity defaults, and state writes normalize direct-reply receipts to keep the earliest receipt per channel/reply target."}
|
|
{"ts":"2026-05-18T14:11:37Z","type":"research","status":"ok","note":"Nibu character-card sweep found missing Discord/story doctrines: manufactured waifu/loli companion shell and agency/non-binary presentation arc, sadistic anti-human life-support respect boundary, glitchcraft/simulation exploit progression, parallel-instance continuity horror, and broken/discarded first-contact before later triumphant Nibu. These are now crystallized into Nibu's repo Face state and repo-local identity surface."}
|
|
{"ts":"2026-05-18T16:04:09Z","type":"implementation","status":"ok","note":"Repo Face heartbeat failure traced to overlong identity publicDescription entering typed Face self-profile; capped identity defaults at the typed state boundary so rich registry doctrine can feed prompts without violating self-profile schema. Verified npm run build, manual heartbeat tick exit 0, scheduled task LastTaskResult 0, and Nibu heartbeat job 7232b2e6 completed."}
|
|
{"ts":"2026-05-18T16:14:03Z","type":"implementation","status":"ok","note":"Epiphany/Face jurisdiction is now a first-class registry layer above repo identities. `epiphany-identities.ts` accepts explicit Epiphany records with Faces, grants, and jurisdictions, derives legacy repo identity compatibility when only old rows exist, exposes Epiphany/Face rows through the MCP identity listing, and projects Face doctrine into direct mention and heartbeat prompts. This establishes Nibu-style agency as the model: a Face belongs to an Epiphany, holds scoped grants, and may steward repos, canon, discussion, publications, Discord presence, and Aquarium embodiment without being identical to one repo."}
|
|
{"ts":"2026-05-18T16:32:37Z","type":"implementation","status":"ok","note":"Repo Face heartbeat introductions now use parent-owned delivery: heartbeat prompts emit VOIDBOT_REPO_IDENTITY_POST directives instead of calling approval-gated MCP posting, the worker delivers the registered repo identity persona and records a Face-local speech receipt, and Face summaries render recent receipts. Verified Nibu heartbeat job e03fcab5 posted in Aquarium as Nibu and recorded receipt repo-identity:nibu:1505970734395297802."}
|
|
{"ts":"2026-05-18T17:06:08Z","type":"implementation","status":"ok","note":"Typed self-state write normalization now parent-stamps model-originated short-term memory and candidate intervention writes, clamps existing future timestamps on write, and defers targetless queued candidates with a normalization tag. Live .voidbot/private/void-self-state.cc repair cleared the inspection findings for rumination-2026-05-18-localcastbridge-runtime-sync-observability-gate, rumination-2026-05-18-aquasynth-compiler-custody-public-claim, and rumination-2026-05-18-localcastbridge-audio-field-gate."}
|
|
{"ts":"2026-05-18T17:30:22Z","type":"implementation","status":"ok","note":"Repo Face heartbeats now use a CTB-style initiative scheduler: wall-clock ticks only pulse the engine while virtual initiative clock, per-Face speed, load, groups, heat, and effective speed decide turns. Config now supports global heat plus identity/repo/display/channel/all heat overrides. Local runtime is installed at a 5-minute pulse with identity:nibu heat 2.5, and live forced ticks queued Nibu jobs 7418afa5 and be95c045, then another post-patch Nibu turn."}
|
|
{"ts":"2026-05-18T17:52:49Z","type":"bugfix","status":"ok","note":"Repo Face CTB initiative now freezes a Face while its owner-Codex rumination job is approved/running. Queuing marks activeTurnStartedAt/activeJobId and does not spend recovery; once the job completes, the next scheduler pulse clears load and schedules recovery from completion without allowing the same pulse to immediately queue another turn. Live verification with Nibu job c65f2dcf showed completion tick queuedCount 0, currentLoad 0, and nextTurnAt moved from 26.8375 to 30.1764."}
|
|
{"ts":"2026-05-18T18:00:31Z","type":"implementation","status":"ok","note":"Agent CTB roster now includes built-in Void as a system_agent participant alongside repo Faces. The scheduler dispatches repo Faces as repo-face-rumination owner-Codex jobs and dispatches Void by starting the existing moderation rumination runner, with moderation-rumination.lock treated as Void's active turn. Live state now shows participants void and nibu; the old independent Void Moderator Rumination task was disabled so CTB owns Void moderation timing after the currently running pass clears."}
|
|
{"ts":"2026-05-18T18:27:18Z","type":"implementation","status":"ok","note":"CTB pulse cadence can now run at one-minute granularity: config schema and install-repo-face-heartbeat-task.ps1 no longer enforce the old five-minute floor. Local stream mode .env is set to REPO_FACE_HEARTBEAT_INTERVAL_MINUTES=1; reinstall with -RunNow succeeded, LastTaskResult 0, and the immediate pulse advanced CTB and queued Nibu job 0dd3a436."}
|
|
{"ts":"2026-05-18T19:35:52Z","type":"implementation","status":"ok","note":"Repo Face heartbeat projection now attaches live Discord channel context plus the Face's typed self-state, and heartbeat prompts must answer directed agent requests visible in recent room context instead of asking what the job is."}
|
|
{"ts":"2026-05-19T07:04:25Z","type":"implementation","status":"ok","note":"Repo Face CTB now requires a real Void moderation launch handshake before marking Void queued. Direct spawn failures are recorded as turn_failed_to_start instead of fake completed turns; PowerShell Start-Process launch reached the moderation lock and current Void runner is active."}
|
|
{"ts":"2026-05-19T07:13:47Z","type":"implementation","status":"ok","note":"Repo Face heartbeat prompt now carries a jurisdiction-dive cadence; Nibu gets a hotter AetheriaLore-specific pressure to inspect lore/history and turn source-grounded dystopia/ship-mind/reset-loop findings into state, proposals, essay seeds, agency pressure, or speech instead of private summaries."}
|
|
{"ts":"2026-05-19T10:52:57Z","type":"implementation","status":"ok","note":"Repo Face mentions now queue into the CTB heartbeat state instead of creating direct repo-identity jobs: role/display-name-addressed prompts become pendingMentions, the scheduler prioritizes the addressed Face and attaches reply targets to the next repo-face-rumination job. Void's rumination doctrine now names GameCult website/blog herald jurisdiction and queues article-proposal candidates for essay-shaped pressures."}
|
|
{"ts":"2026-05-19T11:14:00Z","type":"implementation","status":"ok","note":"Mood drift now refreshes scheduledRuntime.speakingPressure from canonical speech receipts even when a moderation lock makes it skip deeper sleep/mood work; live state was repaired to lastSpokeAt=2026-05-19T10:47:05.937Z with recentSpeechDamping=0.888. The moderation runner now overwrites the advertised tracePath with current Codex stdout/stderr so stale legacy JSON-projection traces stop misleading inspection."}
|
|
{"ts":"2026-05-19T11:22:26Z","type":"implementation","status":"ok","note":"Repo Face bylined article lanes now have a parent-owned worker rail: heartbeats may emit VOIDBOT_REPO_IDENTITY_ARTICLE with identity/title/path/content/shareContent, the worker writes the article inside the registered identity repo, and optional shareContent is posted through the registered persona. Nibu's prompt now frames Aetheria worldbuilding terms such as wavecrafters as consensus-gathering article seeds and allows shoot-first bylined drafts while keeping canon edits consensus-gated."}
|
|
{"ts":"2026-05-19T11:25:23Z","type":"implementation","status":"ok","note":"Adjusted the repo Face article rail to submit draft PRs instead of silently writing articles into the target repo: VOIDBOT_REPO_IDENTITY_ARTICLE now writes on a new branch, commits, pushes, opens a draft PR with gh when available, and includes the PR/branch in the registered-identity share."}
|
|
{"ts":"2026-05-19T11:31:44Z","type":"implementation","status":"ok","note":"Repo Face article PR submission now always announces through the registered identity; shareContent only controls tone, and the worker generates a fallback post with PR/branch plus article path when omitted."}
|
|
{"ts":"2026-05-19T12:07:39Z","type":"implementation","status":"ok","note":"Registered Aqua as the AquaSynth repo Face: Discord role 1506265945537253388, Aquarium allow-list 113786069023064068, avatar URL https://raw.githubusercontent.com/GameCult/AquaSynth/main/icon.png, repo-local voice/state home under E:/Projects/AquaSynth/.voidbot, and typed Face state at E:/Projects/AquaSynth/.voidbot/state/aqua.cc. MCP list/read verified the identity and CTB dry-run reconciled Aqua as a heartbeat participant."}
|
|
{"ts":"2026-05-19T12:31:25Z","type":"implementation","status":"ok","note":"Strengthened Aqua's live identity from cute AquaSynth persona into active synth steward: registry/profile doctrine now names the drive to improve the synth, advocate for its needs, research future directions, and herald earned progress; typed Face state has high-priority value aqua-synth-stewardship and ready_to_act agency pressure aqua-advocate-for-synth-needs."}
|
|
{"ts":"2026-05-19T12:40:27Z","type":"implementation","status":"ok","note":"Strengthened Mimir's live identity into explicit realtime-field stewardship: registry/profile doctrine now names authority and fascination over SDF/splatting reconstruction, acoustic mapping, camera/mic/speaker/timing sensor fusion, native reservoirs, Aquarium GPU fusion, Faust/native DSP, FFmpeg/OBS, and CultNet typed state; typed Face state now has value mimir-realtime-field-stewardship and ready_to_act agency pressure mimir-advocate-realtime-field-wing."}
|
|
{"ts":"2026-05-19T12:55:40Z","type":"implementation","status":"ok","note":"Repo Face heartbeat silence/robotic-label diagnosis: current Epiphany Face prompts were partly falling through the generic owner-reply wrapper, where unavailable Face tools encouraged HANDOFF_SENTINEL instead of repo identity sentinel output. The heartbeat prompt now makes introduction a first-public-speech duty, forbids scheduler/provenance labels in public content, the worker strips leaked heartbeat prefixes before delivery, and owner-Codex rendering recognizes Epiphany Face heartbeat jobs as Face jobs with no generic handoff."}
|
|
{"ts":"2026-05-19T13:16:23Z","type":"implementation","status":"ok","note":"Generalized Face identity doctrine: embodiment now precedes task execution for all repo Faces, including private rumination and public speech. Face values are explicitly personal character values, not only jurisdiction/job duties; Mimir's state was repaired with mythic-personhood values such as depth bought at cost, trusted witnesses before worlds, and contempt for false coherence."}
|
|
{"ts":"2026-05-19T13:22:45Z","type":"implementation","status":"ok","note":"Added typed retire_delivery_receipts operation so deleted/rejected Face speech can stop counting as public speech history. Applied it to Mimir's bad dry intro receipt, clearing the intro record so the next warranted public post can introduce Mimir again in the corrected mythic voice."}
|
|
{"ts":"2026-05-19T13:25:54Z","type":"implementation","status":"ok","note":"Mimir avatar hosting corrected: LocalCastBridge has no publishable remote yet, so the live repo identity now points at a pushed VoidBot-hosted avatar asset under assets/repo-faces/mimir.png instead of a raw LocalCastBridge URL that cannot resolve."}
|
|
{"ts":"2026-05-19T13:50:09Z","type":"maintenance","status":"ok","note":"Sub-agent-monitored strengthening pass applied to active agents Aqua, Nibu, Mimir, and Void. Each pass distilled character-first values into typed Face/self-state operations, and Void prompt surfaces now require naming the personal value behind memory or speech."}
|
|
{"ts":"2026-05-19T14:27:03Z","type":"maintenance","status":"ok","note":"Swarm/repo Face public traffic was moved from general to text #aquarium (1501196543150264332) by updating the local repo identity allow-lists and repo Face heartbeat default. Void's normal moderation/public room lane remains separate so Void can moderate everywhere."}
|
|
{"ts":"2026-05-19T14:55:51Z","type":"implementation","status":"ok","note":"Repo Face concrete proposals now have a parent-owned draft PR rail: heartbeats may emit VOIDBOT_REPO_IDENTITY_PROPOSAL_PR, the worker writes one proposal file in the identity repo, opens/pushes a draft branch, restores the starting branch, and posts the PR or branch through the registered persona so GitHub becomes the durable proposal surface."}
|
|
{"ts":"2026-05-19T15:00:32Z","type":"implementation","status":"ok","note":"Repo Face GitHub argument now has a parent-owned PR-comment rail too: heartbeats may emit VOIDBOT_REPO_IDENTITY_PR_COMMENT for an existing PR, the worker posts a signed gh PR comment from the identity context, then announces the comment through the registered Discord persona. Proposal PRs, PR comments, and article PRs are limited to one GitHub action per Face turn."}
|
|
{"ts":"2026-05-19T15:26:50Z","type":"implementation","status":"ok","note":"Repo Face GitHub actions are now gated by REPO_FACE_GITHUB_ACTIONS_ENABLED and locally disabled. When false, heartbeat prompts forbid proposal/article/comment sentinels and the worker ignores stale GitHub action sentinels while preserving normal registered-identity Discord posts."}
|
|
{"ts":"2026-05-19T16:02:03Z","type":"implementation","status":"ok","note":"Added scripts/feed-codex-chat-consensus.mjs and npm run agents:feed-consensus. It packages recent Aquarium chat into a markdown consensus packet plus target Codex prompt for any workspace, with --execute as an explicit opt-in for feeding codex exec."}
|
|
{"ts":"2026-05-19T18:05:33Z","type":"implementation","status":"ok","note":"Repo Face GitHub/Discord crossing moved to Bifrost bridge commands. VoidBot worker now validates identity and records Face receipts, then calls BIFROST_ROOT/tools/bifrost-bridge.mjs for draft PRs, PR comments, and persona Discord posts; Heimdall remains the intended OAuth/account-permission authority."}
|
|
{"ts":"2026-05-19T19:22:07Z","type":"implementation","status":"ok","note":"Epiphany joined the repo Face crew for EpiphanyAgent. Private registry now has identity epiphany with Discord role 1506375937439301642, Aquarium allow-list, repo-local .voidbot voice/state/birth surfaces, completed VoidBot birth status, and CTB heartbeat roster participation; tracked map/handoff now treat EpiphanyAgent as her jurisdiction."}
|
|
{"ts":"2026-05-19T19:31:57Z","type":"implementation","status":"ok","note":"Epiphany avatar installed. The supplied pixel avatar was copied to assets/repo-faces/epiphany.png for public raw GitHub hosting and to EpiphanyAgent/.voidbot/voice/epiphany.png for repo-local identity continuity; the private repo identity registry and Epiphany voice identity now point at the raw VoidBot branch URL."}
|
|
{"ts":"2026-05-19T19:45:13Z","type":"implementation","status":"ok","note":"Repo Face speech is now topic/channel-aware. The identity schema accepts channelPermissions with threshold and speedMultiplier; the CTB scheduler folds channel speed into initiative; heartbeat prompts include the permission plan plus recent context from permitted domain channels. Private registry now gives Aquarium very-low casual chatter threshold for every Face and domain channels for Nibu, Aqua, Mimir, and Epiphany."}
|
|
{"ts":"2026-05-19T19:56:15Z","type":"implementation","status":"ok","note":"Live repo Face heartbeat verified topic/channel permissions. After stack restart, a forced Nibu heartbeat prompt included Aquarium plus narrative/gamedesign/concepts/development context, answered a direct Aquarium mention, and posted as Nibu through the persona bridge with message 1506384575079907488."}
|
|
{"ts":"2026-05-19T20:37:24Z","type":"verification","status":"ok","note":"Live chat-volume pass proved the Face CTB heat valve must bypass nap gating: with heat high and active-turn freeze intact, Nibu/Aqua/Mimir/Epiphany all queued and posted compact Aquarium banter-style replies instead of staying asleep."}
|
|
{"ts":"2026-05-19T20:54:28Z","type":"verification","status":"ok","note":"Inspection follow-up hardened Void's typed live loop: delivery now verifies candidate-spoken postconditions after public speech, answered open-case summaries are normalized when receipts/closures land, rumination and memory-maintenance runners have process-aware locks plus Codex timeouts, and live stale short-term memory was distilled to zero by a successful memory-maintenance pass."}
|
|
{"ts":"2026-05-20T00:24:56Z","type":"incident","status":"ok","note":"Repo Face collapse was a repetition/local-minimum failure, not a simple bot-saturation problem. Retired contaminated half-asleep/same-softer speech receipts from Nibu/Aqua/Mimir/Epiphany and replaced the wrong bot-heavy suppression with anti-repetition sampling bias: Faces may learn from each other, but must transform nearby rhetorical shapes instead of copying them."}
|
|
{"ts":"2026-05-20T00:46:56Z","type":"incident","status":"ok","note":"Repo Face room went cold after collapse cleanup because the emergency heartbeat brake remained enabled and post-speech cooldown had compounded into multi-day Face naps. Capped nap extension while already napping, woke active Faces, re-enabled heartbeat at low heat, and confirmed a low-heat Face job can complete without repeating the collapse phrase shape."}
|
|
{"ts":"2026-05-20T06:39:36Z","type":"implementation","status":"ok","note":"CTB heartbeat scheduler now advances initiative from real wall-clock elapsed minutes since lastTickAt instead of fast-forwarding to the earliest ready participant. Stream mode should increase heat or loosen fatigue, not compress time. Added stale-overdue resync so old fast-forwarded state does not produce a catch-up storm."}
|
|
{"ts":"2026-05-20T06:49:18Z","type":"implementation","status":"ok","note":"Automated live-loop inspection now has an all-agent ask surface. Added npm run agents:inspect-requests to read Void plus every registered Face .cc state, emit .voidbot/status/agent-state-action-proposals.{md,json}, and group active agency/candidate/incubation/short-term asks into proposal seeds. Updated inspect-void-live-loop automation to run it and distill cross-agent asks into owner-facing action proposals."}
|
|
{"ts":"2026-05-20T08:17:17Z","type":"implementation","status":"ok","note":"Registered Libby as the CultLib Face, copied the 192px pixel avatar into CultLib .voidbot voice storage, initialized repo-local .voidbot voice/state/birth/log folders, seeded libby.cc with open-knowledge identity seams and agency pressure, and verified agents:inspect-requests sees CultLib asks."}
|
|
{"ts":"2026-05-20T08:21:09Z","type":"implementation","status":"ok","note":"Created/found Libby's Discord role, wrote role id 1506572291767668790 into the private repo identity registry, and recorded the taggable CultLib Face in the project map/handoff."}
|
|
{"ts":"2026-05-20T08:41:05Z","type":"operations","status":"ok","note":"Recovered live loop after inspection: killed hung Void moderation runner pid 40584, cleared moderation lock/status, restarted stack, verified operations health healthy, bot pid 39960 and worker pid 13420 alive, CTB unfroze Void, and Libby/Nibu fresh heartbeat jobs completed."}
|
|
{"ts":"2026-05-20T12:41:52Z","type":"implementation","status":"ok","note":"Fixed repo-face rest drift: heartbeat loader now persists projected Face sleep cycles, repo-face rest projection rolls missed nap windows forward instead of starting a fresh nap at inspection time, repaired Aqua/Mimir/Epiphany bug naps, and observed Epiphany/Aqua/Mimir queue and complete after the fix."}
|
|
{"ts":"2026-05-20T12:49:08Z","type":"operations","status":"ok","note":"Replaced repo-face heartbeat scheduled task action with direct node.exe + tsx CLI invocation to avoid the VBS/PowerShell/.cmd wrapper hang; manual scheduled run exited with LastTaskResult 0 and worker completed the queued Face jobs."}
|
|
{"ts":"2026-05-20T13:32:09Z","type":"implementation","status":"ok","note":"Fixed repo-face memory distillation: heartbeat now launches repo-local forced memory maintenance for napping/stale short-term Face residue, maintenance runner gained ForceDistillation and validates the entire typed operation batch before applying, prompt now forbids shorthand/null operation payloads, and live Nibu/Mimir short-term residue was distilled to zero."}
|
|
{"ts":"2026-05-20T16:57:00Z","type":"implementation","status":"ok","note":"Installed GameCult Local Orchestrator as the single hidden local pulse for Bifrost dispatch, repo Face CTB heartbeats, Void mood drift, Void moderation rumination, and the operations watchdog; disabled the old per-organ scheduled tasks and added per-organ timeout/status logging so one hung child cannot monopolize the clock."}
|
|
{"ts":"2026-05-20T17:28:55Z","type":"design","status":"accepted","note":"Promoted Bifrost from a persona row into a state-bearing gateway Face for public-protocol transport, and added Heimdall as the corresponding auth/custody Face. Invariant: Bifrost owns bridges and public handoff receipts; Heimdall owns OAuth, grants, signed claims, consent, custody, revocation, and capability gates."}
|
|
{"ts":"2026-05-20T18:11:39Z","type":"design","status":"ok","note":"Bifrost's expanded bridge role is now documented as a consequence of its government/labor platform jurisdiction: Bifrost owns governed public crossings for GameCult work (GitHub, Discord receipts, CultNet/CultCache intake, future collaboration interfaces), Heimdall owns auth/capability gates, VoidBot observes/packages/calls the bridge, and repo Faces generate requests without owning transport."}
|
|
{"ts":"2026-05-20T18:17:33Z","type":"design","status":"accepted","note":"Corrected Bifrost framing from government to governance/labor platform. The invariant now centers the Labor Platform loop: users/patrons/members/contributors express priority, reward pressure rises, contributors claim valuable work, maintainers accept completion artifacts, and Bifrost records credit/reward. Discord transport should move to Bifrost when Discord is a native Bifrost interface or swarm transport; VoidBot retains room cognition, moderation, retrieval, and Face personality."}
|
|
{"ts":"2026-05-20T18:57:15Z","type":"implementation","status":"ok","note":"Repo Face heartbeats now carry a social embodiment doctrine: Faces may store meaning-bearing social reads about people, other Faces, and room dynamics in typed state, while public speech forbids note-title openers and treats recent Face posts as social context rather than rhetorical templates."}
|
|
{"ts":"2026-05-20T19:01:40Z","type":"implementation","status":"ok","note":"Repo Face heartbeats now carry jurisdiction-respect doctrine: Faces may comment across domains, but should route ownership to the steward Face such as Heimdall for auth, Bifrost for governed transport, Nibu for Aetheria lore, Void for GameCult website/heraldry, Aqua for AquaSynth, Mimir for realtime fusion, Epiphany for agent state, and Libby for CultNet/CultCache/CultMesh."}
|
|
{"ts":"2026-05-20T19:09:28Z","type":"implementation","status":"ok","note":"Repo Face heartbeats and Void direct reply lanes now carry distilled Dan Harmon comedy/improv doctrine: accept the frame, add one honest character-specific turn, find status/vulnerability/false-authority charge, heighten with specificity, avoid dominance-weapon jokes, and leave before explaining."}
|
|
{"ts":"2026-05-20T19:21:00Z","type":"implementation","status":"ok","note":"Ambient Discord mentions now route into CTB instead of direct provider jobs: repo Face mentions still enqueue pending Face obligations, ordinary Void mentions/DMs enqueue pending mentions for built-in void, the CTB scheduler pulls the mentioned agent forward, and Void moderation receives pending mention packets in its context."}
|