Refocus self-state rebuild on prevention
This commit is contained in:
parent
65aa701594
commit
03b90d009b
5 changed files with 35 additions and 15 deletions
|
|
@ -24,6 +24,8 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
|
|||
- The ordinary bot/worker/provider/RAG/Postgres/Qdrant foundation still deserves to survive.
|
||||
- The moderation/mood/private-self-state foundation does not. Treat it as the top architectural risk until JSON projection mutation and legacy mirrors are gone.
|
||||
- The smallest coherent target is one polymorphic CultCache-backed state authority with typed document kinds plus typed mutation tools: agents propose small operations, and the state service validates/applies them. Whole-state JSON editing is rejected as a durable mutation path.
|
||||
- Most of the deterministic cleanup in `scripts/void-memory-organ.mjs` is recent compensator cruft from failed attempts to manually clean an exploded state file. Do not preserve it as an earned organ. Architect the state boundary so that cleanup pile is unnecessary.
|
||||
- Sleep/distillation must be rewritten with a meaning-preservation contract: concrete subject, claim/question, evidence refs, live tension, and future-action implication survive compression. Bulk can die. Meaning does not get put through the office shredder and called a dream.
|
||||
- The owner Codex lane is no longer one swollen file; orchestration, runtime/parsing, rendering, and shared helpers are split under `packages/providers/src/owner-codex-*.ts`.
|
||||
- The local Ollama lane is no longer one swollen file; orchestration stays in `packages/providers/src/local-llm-provider.ts` while prompt/rendering, tool-loop helpers, and shared types/constants live under `packages/providers/src/local-llm-*.ts`.
|
||||
- The Discord bot lane is no longer one swollen entrypoint; gateway wiring remains in `apps/bot/src/discord-bot.ts` while command/prompt handlers and Discord-shape support helpers now live under `apps/bot/src/discord-bot-*.ts`.
|
||||
|
|
@ -57,7 +59,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
|
|||
- The memory organ now treats repeated empty-room bookkeeping as low-signal. Refrains like `no new messages / no smoke / no post` should be merged or cooled off instead of becoming the dominant incubating seam and teaching Void that silence is the only virtue.
|
||||
- Quiet-room exploration should now prefer underworked terrain when the usual seam is saturated. `bridge.source_coverage` and `bridge.refractory_topics` exist to push the next pass toward less-chewed repo families, archive years, or channels instead of rewarding repetition with another supposedly ripe synthesis.
|
||||
- During naps, the moderation loop is supposed to turn inward: distill/prune memories against the active goals, record dream residue in `memories.dreams`, refresh `moderation_runtime.sleep_cycle`, and only break the nap for real smoke or an unusually novel thought worth muttering into the room.
|
||||
- Sleep is now meant to be lossy. The nap pass in `scripts/void-memory-organ.mjs` promotes a few stronger seam summaries into semantic memory, then cuts raw episodic receipts, repo sweeps, archive excursions, novelty checks, and recent musings back down so awake rumination has to think from the seam instead of rereading yesterday's scrapbook.
|
||||
- Sleep is meant to be lossy about bulk, not about meaning. The current nap pass in `scripts/void-memory-organ.mjs` cuts raw residue, but the next architecture pass must rewrite sleep/distillation so concrete repo-bound or room-bound meanings do not collapse into abstraction sludge.
|
||||
- Awake rumination is now supposed to do the actual philosophy from those surviving seams. The moderation doctrine tells quiet runs to begin with seam-thinking when incubation is live: ask what principle the seam is circling, what tension keeps it honest, and what embodiment consequence would cash it out before reaching for more retrieval.
|
||||
- There is now an identity crystallization path for over-chewed private seams. If a thought survives enough passes to stop being meaningfully novel, the memory organ can retire it from `incubation.active_thoughts`, promote it into `identity.private_notes`, add a matching canonical value, and keep one `identity_seam` semantic memory instead of letting the same thought pace forever in the active queue.
|
||||
- Crystallization is not meant to be mute. The memory organ can now queue an `identity_crystallization` candidate intervention with a first-person draft, and the moderation doctrine treats that kind of draft as warmer than ordinary private wallpaper: if the room has not already heard the opinion in roughly that shape, Void should usually share it.
|
||||
|
|
@ -81,7 +83,8 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
|
|||
|
||||
- Stop feature work on moderation, mood, agency, and public-lane behavior until the private-state boundary is rebuilt.
|
||||
- First bounded move: define typed CultCache document ownership and mutation operations for cursor/open cases, delivery receipts, candidate interventions, sleep/speaking runtime, and distilled memory. CultCache is natively polymorphic; do not create separate stores just to make the type names feel architectural.
|
||||
- Next cuts should delete unstable foundations early: move repo-activity cursor updates behind the typed store, replace whole-state agent JSON edits with operation output, remove `legacyJsonPath`/working-projection authority, then cut top-level mirror fields.
|
||||
- Next cuts should delete unstable foundations early: move repo-activity cursor updates behind the typed store, replace whole-state agent JSON edits with operation output, remove `legacyJsonPath`/working-projection authority, then cut top-level mirror fields and cleanup code that only compensated for those broken boundaries.
|
||||
- Rebuild sleep/distillation before trusting it again. Fixture check: a memory like `AquariumSynthCSharp: Workflow cannot own the body` must survive sleep with its concrete subject, claim, evidence, tension, and implication intact.
|
||||
- Do not build adapters around the JSON projection. That is how the heap learned to stand upright and ask for snacks.
|
||||
|
||||
## Important Paths
|
||||
|
|
|
|||
|
|
@ -4,9 +4,9 @@ This is the current forward plan for the next larger organs. It is not a changel
|
|||
|
||||
## Current Aim
|
||||
|
||||
Stop feature work on moderation, mood, and self-state until the state boundary is rebuilt. The live product goal still stands: Void should answer Discord, remember useful social/project context, retrieve GameCult history/source/lore, and run an unattended moderation/participation loop. The current implementation reaches that goal through JSON projection edits, legacy mirrors, and a swollen memory organ. That is architectural debt wearing a little paper crown.
|
||||
Stop feature work on moderation, mood, and self-state until the state boundary is rebuilt. The live product goal still stands: Void should answer Discord, remember useful social/project context, retrieve GameCult history/source/lore, and run an unattended moderation/participation loop. The current implementation reaches that goal through JSON projection edits, legacy mirrors, and a swollen memory organ. Most of the deterministic cleanup code is recent compensator cruft: it accumulated because the live state had exploded into nonsense, and repeated "clean this file" passes preserved the mess by adding machinery around it.
|
||||
|
||||
The next priority is to remove JSON from the mutation loop entirely. Agents and scheduled workers should mutate typed CultCache-backed state through explicit tools/APIs, not by editing a whole-state JSON working copy.
|
||||
The next priority is to remove JSON from the mutation loop entirely and rebuild the state model so the compensator pile is unnecessary. Agents and scheduled workers should mutate typed CultCache-backed state through explicit tools/APIs, not by editing a whole-state JSON working copy. Sleep and memory distillation must also be redesigned from first principles so they preserve meaning-bearing claims/evidence/tensions instead of collapsing them into generic slogan paste.
|
||||
|
||||
## Smallest Coherent Architecture
|
||||
|
||||
|
|
@ -75,6 +75,8 @@ Runtime context dies at the end of the pass unless an explicit typed mutation pr
|
|||
- `retire_candidate_intervention`
|
||||
- `update_sleep_cycle`
|
||||
- `update_speaking_pressure`
|
||||
- `propose_memory_distillation`
|
||||
- `apply_memory_distillation`
|
||||
- Model/agent output crosses the boundary as proposed operations, not as rewritten state.
|
||||
- The state service validates, normalizes, dedupes, and writes.
|
||||
|
||||
|
|
@ -122,6 +124,7 @@ The runner can hand these to a CLI/MCP tool. The store decides what survives.
|
|||
- Any helper that mutates the JSON projection and commits it back.
|
||||
- Prompt doctrine that tells the child agent how to manually preserve state shape.
|
||||
- Regex/template police that try to repair semantic sludge after the store allowed sludge to become durable.
|
||||
- Deterministic cleanup passes whose real job is compensating for whole-state JSON edits, permissive schemas, or sleep distillation that destroyed meaning.
|
||||
|
||||
### Impossible By Construction
|
||||
|
||||
|
|
@ -143,7 +146,9 @@ The runner can hand these to a CLI/MCP tool. The store decides what survives.
|
|||
- helpers mutate projection files and then commit whole-state changes
|
||||
- legacy mirrors keep reintroducing stale truth surfaces
|
||||
- `scripts/void-memory-organ.mjs` owns storage cleanup, semantic interpretation, vectors, incubation, sleep consolidation, identity crystallization, agency, and speech candidates in one file
|
||||
- the scheduled moderation runner owns lifecycle through a huge prompt instead of a typed runner contract
|
||||
- the scheduled moderation runner owns lifecycle through a huge prompt instead of a typed runner contract
|
||||
- deterministic cleanup is mostly recent scar tissue from failed manual cleanup passes; it should be deleted as the new state boundary makes it unnecessary
|
||||
- sleep/distillation currently lacks a hard meaning-preservation contract, so it can compress a concrete repo-bound thought into generic abstraction sludge
|
||||
|
||||
Verdict: stop feature work and rebuild this foundation. The rest of the machine can keep running, but moderation/mood/self-state work should cut toward typed state tools before adding new behavior.
|
||||
|
||||
|
|
@ -195,12 +200,18 @@ Verdict: stop feature work and rebuild this foundation. The rest of the machine
|
|||
- Delete mirror fields from canonical state.
|
||||
- Verification: projection summaries still contain required information; no code references mirror keys.
|
||||
|
||||
### Commit 8: Split The Memory Organ
|
||||
### Commit 8: Replace Compensating Cleanup With Meaning-Preserving Sleep
|
||||
|
||||
- Split deterministic cleanup from semantic interpretation.
|
||||
- Keep vector/resonance/incubation maintenance behind typed state operations.
|
||||
- Move speech-candidate queuing into a candidate intervention service.
|
||||
- Verification: existing fixture state produces bounded, typed operations and no whole-state rewrite.
|
||||
- Delete cleanup paths whose only job was repairing JSON projection edits, legacy mirrors, keyword sludge, or overgrown runtime residue.
|
||||
- Redesign sleep/distillation around an explicit contract:
|
||||
- preserve the claim/question/fascination target
|
||||
- preserve the concrete subject, such as repo, room, lore seam, person, or system
|
||||
- preserve evidence refs or admit when evidence is missing
|
||||
- preserve the live tension/counterweight
|
||||
- preserve why the memory should affect future action
|
||||
- never replace a concrete thought with a prettier generic principle unless the operation records what was lost and why that loss is acceptable
|
||||
- Make distillation emit typed candidate memories first; the state service applies only candidates that satisfy the contract.
|
||||
- Verification: fixture memories such as `AquariumSynthCSharp: Workflow cannot own the body` survive sleep with their subject, claim, evidence, and tension intact.
|
||||
|
||||
### Commit 9: Rebuild Scheduled Runner As A Phase Machine
|
||||
|
||||
|
|
|
|||
|
|
@ -88,3 +88,4 @@
|
|||
{"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."}
|
||||
|
|
|
|||
|
|
@ -68,6 +68,7 @@ accepted_design:
|
|||
- Private Void self-state should live behind one polymorphic CultCache-backed authority with typed document kinds for self profile, moderation cursor/open obligations, speech receipts, thought memory/incubation, scheduled runtime, and candidate interventions. Do not mistake typed document ownership for separate physical stores.
|
||||
- Agents and scheduled runners should cross the private-state boundary with small typed mutation operations such as cursor updates, open-case upserts, receipt records, memory appends, incubation merges, and candidate-intervention changes.
|
||||
- JSON may be used for operation payloads or debug exports, but not as an editable working projection of canonical self-state.
|
||||
- Deterministic cleanup code should not become a permanent organ just because recent manual cleanup requests accidentally produced compensators. The desired architecture prevents bad state from entering, then uses narrow migrations for historical debris.
|
||||
- `owner_codex` and `local_llm` remain distinct lanes with different tool-execution and safety posture.
|
||||
- Ephemeral room-reading should come from an explicit local-LLM sidecar inference pass plus raw recent-message evidence, not from a rules bucket pretending to understand natural language.
|
||||
- The VoidBot MCP server is the preferred search plane for archived Discord, indexed GameCult repos, Aetheria lore, and owner notifications.
|
||||
|
|
@ -92,7 +93,7 @@ accepted_design:
|
|||
- Void's rumination state now needs to behave like hybrid symbolic-plus-vector memory rather than a pile of prose scraps. Persistent memories should stay inspectable, but naps and quiet runs should also maintain compact semantic vectors, resonance clusters, and a multi-run incubation queue so deeper thoughts can mature before they either surface or die.
|
||||
- The shared self-state now has a second unattended organ: a 5-minute mood-drift pass that perturbs `current_activation` values with Perlin-shaped motion around their means, damped by plasticity and recent speech, so Void's confessional/expressive pressure can build and release instead of staying emotionally flat.
|
||||
- That same shared self-state now carries a scheduled nap cycle. Naps are for maintenance, not vacancy: the moderation loop should distill memory, prune clutter, and leave behind dream memories plus active dream themes that the direct reply lanes can mumble through later.
|
||||
- Sleep should be lossy rather than archival. The nap pass should promote a few stronger seam summaries into semantic memory, then cut raw episodic receipts, repo sweeps, archive excursions, novelty checks, and recent musings back down so awake rumination philosophizes from carved seams instead of rereading yesterday's notes.
|
||||
- Sleep should be lossy about bulk, not about meaning. The nap/distillation path must preserve concrete claims, subjects, evidence refs, tensions, and action implications; if it turns a repo-bound thought into generic abstraction sludge, the sleep machinery is wrong.
|
||||
- Awake rumination should start from those carved seams before it goes spelunking again. Retrieval is support for hungry, stale, contradictory, or under-evidenced thoughts, not a mandatory ritual every quiet pass.
|
||||
- Quiet rumination should prefer concrete project fascination over free-floating engineering aphorisms. If a seam cannot cash out in a real repo, subsystem, gameplay loop, lore structure, interface, or architectural organ, it should lose priority to a branch that can.
|
||||
- Resonance clusters and incubating thoughts should be named as actual claims, questions, or fascination targets with explicit target kinds. Keyword-slash residue is debug lint, not a valid thought surface.
|
||||
|
|
@ -142,8 +143,10 @@ rejected_paths:
|
|||
- name: json_projection_as_state
|
||||
reason: editable whole-state JSON lets unattended agents, helpers, and legacy mirrors bypass typed ownership while pretending the projection is not authoritative
|
||||
- name: semantic_cleanup_as_ownership
|
||||
reason: a giant cleanup organ that repairs bad labels, mirrors, and stale runtime residue is proof the state boundary admitted sludge in the first place
|
||||
reason: a giant cleanup organ that repairs bad labels, mirrors, and stale runtime residue is proof the state boundary admitted sludge in the first place; most recent cleanup code is compensator cruft from failed manual state cleanup passes, not a foundation to preserve
|
||||
- name: lossy_sleep_without_meaning_contract
|
||||
reason: sleep/distillation that collapses concrete claims into generic abstraction creates memory nonsense and then forces later cleanup compensators
|
||||
|
||||
current_status:
|
||||
summary: VoidBot's ordinary bot/worker/provider/RAG/Postgres/Qdrant structure is still conceptually sound, but the moderation/mood/private-self-state foundation has become architectural Jenga. It currently depends on canonical MessagePack plus an editable JSON projection, broad passthrough schemas, legacy mirror fields, a giant memory-organ cleanup pass, and a prompt-owned scheduled runner. That is not a stable foundation for more behavior.
|
||||
next_action: Make the typed CultCache state boundary the top priority. First define the smallest coherent self-state document model and mutation operations, then move repo cursor/open-case/receipt/candidate/memory updates behind those tools. Delete JSON projection authority and legacy mirrors early instead of adding adapters around them.
|
||||
summary: VoidBot's ordinary bot/worker/provider/RAG/Postgres/Qdrant structure is still conceptually sound, but the moderation/mood/private-self-state foundation has become architectural Jenga. It currently depends on canonical MessagePack plus an editable JSON projection, broad passthrough schemas, legacy mirror fields, a giant memory-organ cleanup pass, and a prompt-owned scheduled runner. Much of the cleanup pass is recent compensator cruft from attempts to manually clean exploded state; it should not be dignified into permanent architecture.
|
||||
next_action: Make the typed CultCache state boundary the top priority. First define the smallest coherent self-state document model and mutation operations, then move repo cursor/open-case/receipt/candidate/memory updates behind those tools. Delete JSON projection authority and legacy mirrors early instead of adding adapters around them. Redesign sleep/distillation around a meaning-preservation contract before trusting it to compress memory.
|
||||
|
|
|
|||
|
|
@ -10,3 +10,5 @@ Design and execute the private self-state teardown: replace editable JSON projec
|
|||
- First cut should be state-boundary design and typed mutation tools, not another behavior patch.
|
||||
- JSON can remain a debug export or operation payload format, but not an editable whole-state working copy.
|
||||
- Cut early: repo cursor JSON writes, commit-working-view authority, legacy top-level mirrors, and semantic cleanup code that only exists because invalid durable state was allowed through.
|
||||
- Treat most deterministic cleanup as recent compensator cruft, not machinery to preserve.
|
||||
- Redesign sleep/distillation so compression preserves concrete subject, claim/question, evidence refs, live tension, and future-action implication instead of collapsing meaning into generic slogan paste.
|
||||
|
|
|
|||
Loading…
Reference in a new issue