Move typed Persona memory rendering into projector
This commit is contained in:
parent
85d60b6155
commit
85c8da9d71
7 changed files with 103 additions and 202 deletions
|
|
@ -414,3 +414,4 @@
|
|||
{"ts":"2026-07-15T23:41:50Z","type":"implementation","status":"ok","note":"Extracted read-only Persona Body/Mind acquisition into persona-state-source.ts. Scheduler pulses now project current rest facts without writing sleep cycles or synthetic speaking pressure; memory rendering consumes the acquired typed observation. Smoke proves missing observation creates no file and existing .cc bytes remain unchanged."}
|
||||
{"ts":"2026-07-15T23:50:14Z","type":"implementation","status":"ok","note":"Extracted semantic Persona-memory vector refresh/query into persona-memory-context-source.ts. It consumes the existing PersonaStateObservation, returns typed hits/unavailability, and cannot reload canonical .cc state or render prompt prose. Deleted vector-store and recall-query mechanics from the heartbeat shell; smoke proves missing Mind fails before vector access."}
|
||||
{"ts":"2026-07-16T00:00:35Z","type":"implementation","status":"ok","note":"Extracted Persona memory projection policy into persona-memory-projector.ts. One boundary now owns deterministic/model selection, projector prompt construction, minimum output, and schema/path leak rejection through an injected text-model port; repo Faces and typed native Personas share it. Smoke proves model-free projection and negative leak rejection."}
|
||||
{"ts":"2026-07-16T00:11:13Z","type":"implementation","status":"ok","note":"Moved the pure typed Persona-state core into persona-memory-projector.ts: identity texture, activation/runtime pressure, needs, bonds, status, mood, and durable/short-term memory. Deleted duplicate shell renderers and repaired the stale leak-validator reference. Execution-level --assemble-prompt nibu succeeded under file storage, covering the script path that tsc -b omits."}
|
||||
|
|
|
|||
|
|
@ -278,4 +278,4 @@ rejected_paths:
|
|||
|
||||
current_status:
|
||||
summary: VoidBot's bot/worker/provider/RAG/Postgres/Qdrant/CultCache structure is live. Repo Face/persona heartbeat jobs run through the direct `openai_api` provider configured for MiMo `mimo-v2.5-pro`, with the expensive state-projector pass still disabled. The 2026-07-04 transport repair replaced the old Bifrost HTTP/token bridge shortcut with typed Bifrost CultMesh Discord command and receipt documents advertised in the Bifrost provider store at `cultmesh://asgard.starfire.bifrost/commands/discord-post`. VoidBot stores the Bifrost target as a CultMesh URI, writes command docs to `E:/Projects/Bifrost/.bifrost/provider-store.cc`, optionally pumps Bifrost's command processor, and waits for typed receipts before completing repo Face Discord delivery. Bifrost's provider advertisement exposes `discord.post` command metadata for Odin/Eve agents, and a bounded Weksa live-fire completed visibly. Eve live state now runs end to end through CultLib dev retained publications, Hermodr ordered SSE, Eve component bindings, and VoidBot typed control state. Receipts acknowledge intent only. Heat initial load, provider-driven change, and browser-command change were visibly verified without reload through the same subscription.
|
||||
next_action: Move the deterministic `renderRepoFaceStatePacket` family from `scripts/run-repo-face-heartbeats.ts` into `persona-memory-projector.ts`. Pass registry/social, room-weather, human-clarity, self-maintenance, and optional curiosity facts explicitly; keep curiosity retrieval and Discord acquisition outside the projector.
|
||||
next_action: Move agency-pressure, incubation, candidate-intervention, and recent-speech sections into `persona-memory-projector.ts`, parameterized by the externally observed `clarityPressureActive` fact. Then make the shell pass social/room/clarity/maintenance/curiosity sections explicitly into a final projector-owned composition primitive.
|
||||
|
|
|
|||
Loading…
Reference in a new issue