Add typed memory maintenance runner
This commit is contained in:
parent
79485cd832
commit
e3735fb9c4
9 changed files with 542 additions and 9 deletions
|
|
@ -33,9 +33,10 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
|
|||
- Prompt-facing rumination chronology is projected by `scripts/lib/void-rumination-context-projection.ps1`. Exact timestamps stay in typed state/status/cursors; the child context gets relative phrases like `5 minutes ago`, including recent Discord messages, repo activity, receipts, memory timestamps, and sleep/speech timing.
|
||||
- `scripts/simulate-void-mood.mjs` has been rebuilt as a typed-only sleep/speaking-pressure pass over `.voidbot/private/void-self-state.cc`.
|
||||
- The old memory-organ script family, legacy moderation-state template, and legacy moderation context exporter have been deleted. Do not revive their cleanup, agency, dream, vector-incubation, or mirror-repair behavior as compatibility scaffolding.
|
||||
- `scripts/run-void-memory-maintenance.ps1` is the first replacement memory-maintenance organ. It builds a bounded context from typed memories/incubation/candidates/runtime, loads `prompts/void-memory-maintenance.md`, and applies only allowed memory/incubation/candidate typed operation proposals through `scripts/void-self-state.mjs`.
|
||||
- Most of the deterministic legacy translation and retention code 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 bad state cannot enter, and keep only narrow historical migrations for old debris.
|
||||
- The desired agency shape is typed state operations plus derived/model-owned policy, not a permanent sermon generator in maintenance code.
|
||||
- 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.
|
||||
- Sleep/distillation now has a runner boundary and prompt contract, but the substantive model behavior still needs live exercising. The invariant is fixed: 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.
|
||||
- Typed memory operations now enforce the first ingress wall for the next brain: `append_distilled_memory`, `propose_memory_distillation`, and `apply_memory_distillation` require a concrete target, claim or question, tension, action implication, and evidence refs unless the operation explicitly tags `evidence:missing`. This does not fix old state. It prevents new summary-only mush from being accepted as memory.
|
||||
- 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`.
|
||||
|
|
|
|||
|
|
@ -120,6 +120,8 @@ This note is the source-grounded description of how the live VoidBot stack is sh
|
|||
- rumination context projector. It turns typed timestamps and helper payloads into prompt-facing relative phrases while leaving exact chronology in parent-owned typed state, status, and cursor bookkeeping.
|
||||
- `scripts/void-self-state.mjs`
|
||||
- typed self-state operation CLI. It applies strict operation payloads such as cursor updates, open-case changes, delivery receipts, repo cursor updates, memory appends, incubation merges, candidate interventions, sleep-cycle updates, and speaking-pressure updates through `packages/core/src/void-self-state-service.ts` against the CultCache `.cc` store.
|
||||
- `scripts/run-void-memory-maintenance.ps1`
|
||||
- typed memory-maintenance runner. It builds a bounded prompt-facing context from typed memories, incubation, candidates, receipts, and scheduled runtime; loads `prompts/void-memory-maintenance.md`; asks Codex for memory/incubation/candidate operation proposals; then applies only allowed typed operations through `scripts/void-self-state.mjs`. It accepts `-StateFilePath` so fixture passes can use a throwaway `.cc` store.
|
||||
- `scripts/install-moderation-rumination-task.ps1`
|
||||
- installs the local 15-minute scheduled task that runs the moderation/participation loop through the hidden PowerShell launcher shim.
|
||||
- `scripts/simulate-void-mood.mjs`
|
||||
|
|
@ -183,4 +185,14 @@ Within the Postgres path, the implementation is split on purpose now too:
|
|||
2. `scripts/simulate-void-mood.mjs` reads typed documents from `.voidbot/private/void-self-state.cc`.
|
||||
3. It updates `void.scheduled_runtime.sleepCycle` and `void.scheduled_runtime.speakingPressure` through `update_sleep_cycle` and `update_speaking_pressure` operations.
|
||||
4. It writes `.voidbot/status/void-mood-drift.json`.
|
||||
5. The old memory-organ script family, legacy state template, and legacy context exporter have been deleted. Memory maintenance, incubation, dream residue, and agency must be rebuilt as typed operation proposals with meaning-preserving contracts rather than revived from the compensator stack.
|
||||
5. The old memory-organ script family, legacy state template, and legacy context exporter have been deleted.
|
||||
|
||||
## Flow 7: Typed Memory Maintenance
|
||||
|
||||
1. `scripts/run-void-memory-maintenance.ps1` exits if moderation rumination is holding its lock.
|
||||
2. It reads `.voidbot/private/void-self-state.cc` through the typed self-state service.
|
||||
3. It writes `.voidbot/status/void-memory-maintenance-context.json` with prompt-facing relative chronology and only typed memory/incubation/candidate surfaces.
|
||||
4. It loads `prompts/void-memory-maintenance.md` and asks Codex for operation proposals unless `-SkipModel` is set.
|
||||
5. The parent runner rejects any operation outside memory, incubation, or candidate-intervention maintenance.
|
||||
6. The parent runner applies allowed operations through `scripts/void-self-state.mjs`.
|
||||
7. This is the replacement path for sleep/distillation and agency work: model-owned proposals crossing the typed operation boundary, not deterministic repair code editing state.
|
||||
|
|
|
|||
|
|
@ -164,7 +164,7 @@ The runner can hand these to a CLI/MCP tool. The store decides what survives.
|
|||
- the old memory-organ script family, legacy moderation state template, and legacy context exporter have now been deleted instead of preserved as forensic bait
|
||||
- deterministic cleanup is mostly recent scar tissue from failed manual cleanup passes; it should stay deleted rather than be ported unless a future typed operation protects a real invariant in the new model
|
||||
- hard-wired agency policy is mostly current scaffolding, not the final authority; identity, advocacy, and speech candidates should emerge from typed memory/state operations plus model-owned judgment under validation
|
||||
- sleep/distillation currently lacks a hard meaning-preservation implementation in the active runner, so it remains offline until rebuilt
|
||||
- sleep/distillation now has a typed maintenance runner and reviewed prompt boundary, but still needs real model-pass hardening before it should be scheduled unattended
|
||||
|
||||
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.
|
||||
|
||||
|
|
@ -239,8 +239,9 @@ Verdict: stop feature work and rebuild this foundation. The rest of the machine
|
|||
|
||||
### Commit 9: Replace Compensating Cleanup With Meaning-Preserving Sleep
|
||||
|
||||
- Delete cleanup paths whose only job was repairing JSON projection edits, legacy mirrors, keyword sludge, or overgrown runtime residue.
|
||||
- Delete or demote hard-wired agency paths whose real job is turning current heuristic scores into doctrine, advocacy, or speech candidates without an explicit typed-state contract.
|
||||
- Landed cut: cleanup paths whose only job was repairing JSON projection edits, legacy mirrors, keyword sludge, or overgrown runtime residue have been deleted with the old memory-organ stack.
|
||||
- Landed cut: hard-wired agency paths that turned heuristic scores into doctrine, advocacy, or speech candidates without an explicit typed-state contract have been deleted.
|
||||
- Landed replacement boundary: `scripts/run-void-memory-maintenance.ps1` asks the model for memory/incubation/candidate typed operation proposals using `prompts/void-memory-maintenance.md`, rejects non-maintenance operations, and applies the rest through `scripts/void-self-state.mjs`.
|
||||
- Treat legacy brain mush as a migration problem, not the design center. New memory writes must cross the meaning-preserving typed operation schema before they reach CultCache.
|
||||
- Redesign sleep/distillation around an explicit contract:
|
||||
- preserve the claim/question/fascination target
|
||||
|
|
@ -250,7 +251,7 @@ Verdict: stop feature work and rebuild this foundation. The rest of the machine
|
|||
- 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.
|
||||
- Remaining verification: model-pass fixtures such as `AquariumSynthCSharp: Workflow cannot own the body` survive sleep with their subject, claim, evidence, and tension intact.
|
||||
|
||||
### Commit 10: Resume Product Hardening
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue