GameCult/VoidBot
Watch
9
0
Fork
You've already forked VoidBot
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Polish compaction handoff notes

Browse source
This commit is contained in:
Meta Vens 2026-04-26 02:38:45 +01:00
commit ffa72cbd30
2 changed files with 15 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
notes/fresh-workspace-handoff.md
View file

@ -25,6 +25,12 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
- Ops health, backup verification, offsite sync, and dashboard surfaces already exist.
- The new state/notes surfaces are now the continuity spine for future nontrivial work.
## Likely Next Bounded Move
- The next good structural cut is probably `apps/bot/src/discord-bot.ts` or `packages/core/src/interaction-memory-logic.ts`.
- Prefer the seam with the clearest concern split rather than chasing line count for its own sake.
- Do not broaden scope into a heroic "refactor everything" binge. One organ at a time.
## Important Paths
- Project root: `E:\Projects\VoidBot`

12
notes/voidbot-implementation-plan.md
View file

@ -4,7 +4,7 @@ This is the current forward plan for the next larger organs. It is not a changel
## Current Aim
Use the new persistent project-state surfaces to keep future work source-grounded and rehydratable while the stack keeps getting more interconnected.
Use the persistent project-state surfaces to keep future work source-grounded and rehydratable while continuing to cut oversized runtime organs into cleaner seams.
## Near-Term Organs
@ -23,9 +23,15 @@ Use the new persistent project-state surfaces to keep future work source-grounde
### 3. Admin And Forensics Surfaces
- richer inspection around jobs, provider runs, tool usage, interaction memory, and rate-limit denials
- better “what happened?” answers without spelunking raw artifacts by candlelight
- better "what happened?" answers without spelunking raw artifacts by candlelight
### 4. The Still-Scaffolded Paths
### 4. Legibility Hardening
- continue splitting oversized runtime files where concern boundaries are already obvious
- likely next cuts: `apps/bot/src/discord-bot.ts`, `packages/core/src/interaction-memory-logic.ts`, or `packages/core/src/state-storage.ts`
- keep behavior stable while moving concerns into smaller organs
### 5. The Still-Scaffolded Paths
- replace the remaining scaffolded provider paths with funded or production-grade implementations
- move sandbox execution from policy theater to real constrained runners when the policy story is ready