research: persona projector precedents and the empty activation profile

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-11-03 09:21:20 +01:00
commit 502b2fdcff

View file

@ -0,0 +1,49 @@
# Persona projector facts (Eyes, read only, 2026-11-03)
## Part 1: the empty vector
Read via the eureka-state MCP stdio binary pointed at each daemon (HUGINN_ENDPOINT rudp://10.77.0.1:1787x, EUREKA_INSTANCE=slug; persona_get only). Raw: scratchpad `pers\<mind>.raw`, parsed `pers\<mind>.json`; scripts `pg.py`, `an.py`.
All 8 Minds have the identical shape. Every one: receipt updated_at 2026-10-31T09:00:01Z; provenance {authority canonical, sourceSystem huginn, sourceDocumentId = slug, sourceUpdatedAt = exportedAt 2026-10-31T09:00:01Z}; 14 top-level keys; compact value 19.6-26 KB (eureka 24.2, libby 19.6, heimdall 20.1, kiko 21.6, aqua 22.3, weksa 20.7, nibu 20.7, void 21.7).
- EMPTY in all 8: activationProfile (six empty objects: behavioralDimensions, presentationStrategy, situationalState, stableDispositions, underlyingOrganization, voiceStyle; 143 B); affect.moodDimensions [], affect.needs [], affect.socialBiases [], affect.statusReads [], affect.doctrineStances []; candidateActions.actions []; thoughtMemory.shortTerm [], thoughtMemory.incubation [].
- POPULATED in all 8: affect.socialBonds (9 each, ~5.7-6.4 KB, the largest block; prose "summary" plus trust/tension numbers and extensions{numbersAreUnsourcedDefaults:true}); agencyPressure.pressures (7-8, 3.5-4.5 KB); thoughtMemory.memories (5-7, 3.3-5 KB); privateNotes (10-20 strings, 2.2-5.1 KB); values (7-11, 2.4-3.4 KB); presentation (voiceSummary, jurisdiction, homeContext, pronouns, publicHandles, defaultRenderer; 0.6-1 KB); publicName, publicDescription.
- Void: voiceSummary "Lofty and wry, from a great height..."; 5 memories, 8 pressures, 9 bonds, 8 values, 17 private notes; vector empty like the rest.
Where were values last non-empty:
- Not for the Minds. Ruling `eureka-body:ruling:persona-workshop-from-lore-and-journeys` (2026-10-30): swarm Persona states are "drafted fresh" from lore, operator words, repo journey narratives; "VoidBot's Discord-era Persona states are not used (discord-taints-training)". Ruling `eureka-body:ruling:persona-workshop-unbraked` (2026-10-31): "All eight Personas were written from the workshop cards plus the operator's verdict notes into each Mind's own Huginn, with a relationship grid Self extrapolated for all 28 pairs". Follow-up `eureka-body:follow_up:persona-seed-at-bring-up`: "all eight Minds hold a persona with one identical updatedAt that no committed step produced" (no tracked seeding script; writer was a hand persona_put). Workshop card files were not found in the Eureka skill repo, gamecult-ops or Huginn docs by my greps (not exhaustive).
- Eureka's earlier persona (updated 2026-10-29T19:20Z) already had "activationProfile empty" (Huginn/docs/research/2026-10-30-mind-inheritance-prior-art.md:51). So the vector was empty before the 10-31 write.
- Schema: `Huginn/schemas/cultnet/gamecult.persona_state.v0.schema.json` activationProfile is a $ref to six trait maps; VoidBot zod (packages/core/src/persona-state-domain.ts:30-48,74): each trait {mean, plasticity, currentActivation} in 0..1; moodDimensions [{name, value 0..1, source?, updatedAt}]. Huginn test seed (crates/huginn-mind/src/persona.rs:193,198) builds `"activationProfile": traits`, `"moodDimensions": []`.
- VoidBot's old Void store: `.voidbot/private/void-self-state.cc` (named in scripts/simulate-void-mood.mjs at 04dc8e3^). On disk `F:\Projects\VoidBot\.voidbot\` holds only `logs\`; no .cc found, so no old values are quotable here. VoidBot's blank-profile seed (packages/core/src/void-self-state-projection.ts:88-95) writes six `{}`, and `moodDimensions: []` (line 143); activationProfile entered the typed model via legacy-state projection at 77ea82f (2026-05-16, readActivationCategory). A mood-drift runner (scripts/run-void-mood-drift.ps1, simulate-void-mood.mjs 400 lines) existed until 04dc8e3 "Delete local Void mood and memory runners" (2026-07-16); physiology moved into the daemon at 15a7c58 and still reads `faceAffect.moodDimensions` (apps/persona-scheduler/src/void-physiology-domain.ts:88; names anger, annoyance, irritation, envy, pride, smugness, playfulness, anxiety, commandForce). VoidBot's friendly export maps `personality: mapActivationProfile(profile.activationProfile)` (scripts/export-persona-friendly-input.ts:139) and mood at :152.
- Whether Void's VoidBot-era vector held values before July: not determinable from what is on disk.
- Writers today: cut spec r4 (`eureka-substrate:cut_spec:cut-doctrine-persona-in-huginn.r4`): "Writers today are persona_put on the eureka-state MCP and HuginnClient::persona_put in Rust; the huginn CLI has no persona verb ... no organ writes it." Her Persona turn "may rewrite any field (ruling identity-write-all-visible) once it has a write path; it has none yet." I ran no persona_put. Follow-up `eureka-body:follow_up:huginn-cli-persona-verbs`. Follow-up `weksa-lowering:follow_up:persona-state-speech-community` notes the standard has open trait maps and moodDimensions but no speech-community field.
## Part 2: projectors
### Huginn today
`F:\Projects\Huginn\crates\mind-body\src\persona.rs:367-370` (HEAD 577cae2): `render_instructions` = fixed line "You are the persona whose state follows. Speak and act as it, in your own voice." + `serde_json::to_string_pretty(state)`; no field selection, no omission. Called from the persona fetch (line ~360) when a turn loads her instructions. Pretty JSON adds whitespace over the compact sizes above.
### VoidBot standard projector
`F:\Projects\VoidBot\apps\persona-scheduler\src\persona-standard-state-projector.ts` (4,204 B, one function `projectGamecultPersonaState(identity, state)`):
- Pure template, no model. Lines: "<name> is a native VoidBot Persona, not a repo Face."; authority line (canonical vs non-canonical projection); avatar URL/path; publicDescription; then bulleted lists, cap 12 each: Private notes, Values (label: summary), Activation traits (reads profile.activationTraits, a key the schema does not have), Memories, Short-term residue, Agency pressure, Affect needs, Social bonds, Doctrine stances.
- Per field it takes the first of summary/claim/description/text/label/id/name; all numbers (trust, tension, intensity, priority, mean/plasticity/currentActivation, moodDimensions values) are dropped. OMITS: activationProfile, moodDimensions, socialBiases, statusReads, candidateActions, presentation (voiceSummary, jurisdiction, pronouns, handles, homeContext), provenance detail, ids, timestamps, extensions.
- No sample output found or run (read only).
- Richer per-turn path: persona-state-packet-projector.ts (2,203 B) -> persona-memory-projector.ts (`renderPersonaTypedStateSections`, `renderPersonaPressureSections`, `composePersonaMemoryPacket`), persona-social-context-projector.ts, persona-conversation-projector.ts (14.9 KB), persona-turn-prompt-projector.ts (12.4 KB), plus curiosity, relative-chronology, repo-activity projectors. Typed-state affect (packages/core/src/void-self-state-projection.ts ~300-340): top 4 needs, 4 active bonds, 4 status reads by intensity, top 8 moodDimensions by value; if all empty: "- What <name> feels and wants: no explicit affect state yet." Needs render as "Need/<kind> for <target> (<status>, <intensity 2dp>): summary / claim / What rubs / What it wants next". Template plus truncation, numbers printed to 2 dp; not numeric-to-words, not model inference.
- Runs in the scheduler per persona turn (persona-turn-assembler.ts); no cache seen in the files read. Yggdrasil runs no VoidBot persona scheduler (Soul finding `eureka-substrate:finding:cut-doctrine-persona-in-huginn.s1.voidbot-path-not-live`: "voidbot.service swarm publisher and voidbot-retrieval only").
- Recorded lessons on what prose gained or lost: none located (grep of VoidBot notes/docs/state for activationProfile/moodDimensions found only state/map.yaml:156 on Face affect). Git-commit bodies not read.
### Ghostlight
- Design doc `F:\Projects\Ghostlight\docs\architecture\agent-state-distributions-and-prompt-projection.md` (12.6 KB): canonical latent state / perceived state / prompt projection; "Prompt rendering should be treated as projection, not storage"; projection sections Identity And Role, Cultural Default Frame, Current Presentation Strategy, Current Situation, Relationship Context, Relevant Memory, Goals And Constraints, Listener Model; "What The Prompt Should Not Do": not the sole store, not a full memory dump, not "a taxonomy recital", not omniscient; "compact, selective, and scene-bound". Its six state families (Underlying Organization, Stable Dispositions, Behavioral Dimensions, Presentation Strategy, Voice Style, Situational State) are the activationProfile categories.
- Built shape: `docs/architecture/ghostlight-dungeon-mvp.md:324-340` (Projector-Persona-Interpreter membrane). Deterministic code builds a permissioned `SubjectView` (occupancy, knowledge, memories, relationships, pressures, boundaries, executable affordances; private views omit unavailable facts by construction). The Projector is a MODEL organ: receives the view and stimulus, emits "one lived narrative stream: perception, memory, uncertainty, desire, bodily circumstance" in prose, cannot choose an action or emit schema. The Persona sees only identity guidance plus that narrative: no field names, IDs, JSON, tool definitions. Prose is "private derived context, not world truth". Config `GHOSTLIGHT_CONTROLLER_PROJECTOR_MODEL` (:479); receipts bind state digest + Projector receipt (:366); membrane has its own behavioral evaluation (:621): replacement by a tool-using agent must show no regression in "voice, embodiment, uncertainty, tonal range, schema leakage, tool-shaped diction"; until then narrative Personas stay prose-only.
- Not located: the Rust Projector implementation file (crates/ghostlight/src/controllers.rs is 18k+ lines, not traced), sample outputs, before/after sizes, per-turn vs cached timing.
### Where the standard says the projection path moves
- Operator ruling `eureka-body:ruling:voidbot-retired` (2026-10-22): "The Persona State Standard's read/projection owner moves to Huginn." Follow-up `eureka-body:follow_up:voidbot-retirement` (in force; waits on huginn-prose-index): "Move the Persona State Standard's read/projection/migration path to Huginn".
- The checkout F:\Projects\gamecult-ops\docs\persona-state-standard.md still says VoidBot owns read, projection, migration and "no agent should route Persona-state work to Huginn". Cut spec r4 (InForce 2026-11-01) rewrites it: Huginn holds each Mind's canonical state; "VoidBot keeps projection and repo Personas". Cut report `eureka-substrate:cut_report:cut-doctrine-persona-in-huginn.h2` exists; whether it landed on origin was not checked. The ruling and r4 differ on who keeps projection.
### Mind rulings (huginn query --near, no campaign filter; 14,907 docs; 8-row pages)
- `eureka-body:ruling:memory-persona-projection` (2026-10-10): Persona state canonical for lessons; MEMORY.md and files generated from it, provenance projection. File projection, not prompt prose.
- `eureka-body:ruling:persona-doctrine-set-ruled`: a Persona turn loads colossus.md and persona.md only. `eureka-body:ruling:persona-session-landed`: leased claude session, result decoded into typed PersonaReply.
- No ruling or follow-up found on prose projection of Persona state for the prompt, on `render_instructions`, or on populating activationProfile/moodDimensions.
## Gaps
No persona_put done. Ghostlight Projector code, sample outputs, token counts before/after unknown. Workshop card files not found. Void's pre-July VoidBot values not recoverable on this machine.