Ghostlight/notes/fresh-workspace-handoff.md
2026-05-01 23:40:32 +01:00

7.2 KiB

Ghostlight Fresh Workspace Handoff

Do not trust this file for the exact live HEAD. Use git for volatile truth.

Do not continue implementation automatically from a rehydrate-only request.

Immediate Re-entry Instruction

  1. Read state/map.yaml.
  2. Read notes/ghostlight-current-system-map.md.
  3. Read notes/ghostlight-implementation-plan.md.
  4. Run npm run state:status.
  5. Restate the persisted next action before touching code or docs.

Current Shape

Ghostlight now has the persistence spine plus the first architecture payload:

  • canonical map
  • scratch
  • evidence ledger
  • branch ledger
  • compact re-entry note
  • system map
  • implementation plan
  • Python helpers for state summary and compaction audits
  • architecture notes for:
    • personality structure
    • signal classification
    • state distributions and prompt projection
    • Aetheria content generation targets
    • population scaling for socially dense authored slices
  • first schema seam:
    • schemas/agent-state.schema.json
    • schemas/agent-state.required-fields.json
    • examples/agent-state.call-of-the-void.json
    • tools/validate_agent_state.py
  • prompt projection and distillation docs:
    • docs/architecture/prompt-projection-contract.md
    • docs/architecture/projection-distillation-plan.md
    • docs/architecture/sequential-agent-runtime.md
  • evaluation follow-up docs:
    • docs/architecture/schema-future-mechanisms.md
  • Aetheria lore grounding docs:
    • docs/architecture/aetheria-lore-grounding-architecture.md
    • docs/architecture/lore-grounding-digest-format.md
  • lore grounding seam:
    • schemas/lore-grounding-digest.schema.json
    • examples/lore-grounding/historical-flashpoint.template.json
    • examples/lore-grounding/cold-wake-panic.ganymede-corridor.json
    • tools/validate_lore_grounding.py
  • Cold Wake story-lab seam:
    • docs/experiments/cold-wake-story-lab.md
    • examples/agent-state.cold-wake-story-lab.json
    • examples/projections/cold-wake-story-lab.jsonl
    • examples/projections/cold-wake-story-lab.pretty.json
    • experiments/cold-wake-story-lab/the-narrowest-possible-margin.md
    • experiments/cold-wake-story-lab/scene-03-maer-veyr.qwen3-5-9b.capture.json
    • experiments/cold-wake-story-lab/scene-03-maer-veyr.qwen3-5-9b.v2.capture.json
    • experiments/cold-wake-story-lab/scene-03-maer-veyr.qwen3-5-9b.v3.capture.json
    • additional scene 1, 2, 3, and 4 Qwen captures under experiments/cold-wake-story-lab/
    • tools/build_cold_wake_story_lab_fixture.py
    • tools/run_qwen_projection.py
    • tools/validate_qwen_captures.py
  • Cold Wake fixture note:
    • docs/architecture/aetheria-cold-wake-training-fixture.md
  • first projection example seam:
    • schemas/projection-example.schema.json
    • examples/projections/call-of-the-void.scene-broken-taxi-oz.jsonl
    • examples/projections/call-of-the-void.scene-broken-taxi-oz.pretty.json
    • tools/validate_projection_examples.py
  • visitor-facing README refreshed to explain Ghostlight's goals

There is still no full runtime yet. The live machine is design, state discipline, a cleaner repo boundary, the first executable state contract, and a documented projection path.

Current Direction

Use Ghostlight first for:

  • content generation inside the Call of the Void slice described in AetheriaLore
  • dialogue scaffolding and procedural drama for narrated Aetheria timeline stories

Cold Wake is now selected as the first historical grounding fixture because it is authored pre-Elysium lore. It is not the current game target. Treat it as training feedstock for projection and dialogue scaffolding.

Current Next Action

Build the first deterministic scene-local dialogue prototype: local awareness, projection controls, action/dialogue prompt, Qwen event proposal, conservative state mutation, and validation on one Cold Wake story-lab beat.

Cat/Oz remains useful as an Elysium procedural mechanics fixture, but grounded training data should start from authored historical lore rather than gameplay era Elysium outcomes.

The evaluation follow-up fixed the immediate v0 schema issues:

  • behavioral_dimensions.warmth became interpersonal_warmth
  • voice_style.warmth became verbal_warmth
  • Cat now has a perceived-state overlay for Oz
  • Cat and Oz now have relationship summary memories
  • event-drone-lie now includes observed exchange, private interpretations, and event effects

Completed projection path items:

  • define schemas/projection-example.schema.json
  • create reviewed Cat/Oz projection examples
  • choose Cold Wake Panic as the first authored historical flashpoint
  • fill the first draft lore grounding digest: examples/lore-grounding/cold-wake-panic.ganymede-corridor.json
  • define the Cold Wake story lab as a four-scene arc with Maer Tidecall as protagonist
  • add the first Cold Wake projection example and first Qwen response capture
  • widen projection from dialogue-only turns to response turns that can include action, silence, withdrawal, violence, or mixed beats
  • revise the first Maer/Veyr projection through v3 so unresolved personhood/claimant suspicion stays unresolved in Qwen output
  • save both useful failed captures and the accepted v3 response as training material
  • complete the first readable Cold Wake story, experiments/cold-wake-story-lab/the-narrowest-possible-margin.md, with a receipts table tying accepted story beats to projection and capture artifacts
  • promote projection controls into the projection artifact shape: frame_controls, authority_boundaries, object_custody, required_semantics, and forbidden_resolutions
  • add a Qwen projection runner and capture validator so response artifacts are reviewed training receipts, not loose logs

Remaining projection path:

  • build a deterministic speaker-local input slicer
  • build a renderer that emits projection controls before prompt prose
  • build the first scene-local branching tick so an agent can act from local awareness, produce branchable speech or non-speech action, trigger NPC responses, and mutate only the state it has authority to affect
  • keep the near-term product target to interactive dialogue trees and scene-local consequences
  • preserve training-data hooks for future open-world behavior, iterated decisions, psychologically grounded consumer choices, scarcity/reputation pressure, and major faction or institution decision-making
  • defer implementing world-scale simulation loops, autonomous offscreen factions, economy loops, and long-horizon plot machinery until the scene-local machine works
  • use a frontier teacher model to generate/audit projection artifacts
  • train a smaller student projector only after the artifact schema, input slicer, and evaluator stabilize

Warnings

  • Do not let this repo become a mirror maze of notes that say the same thing in slightly different outfits.
  • Keep canonical state small. If evidence starts turning into an activity feed, cut it back.
  • Keep the prompt-projection doctrine intact: prompt text is projection, not truth storage.
  • Do not accidentally re-promote the older corridor-crisis idea into a game MVP because an old doc had a strong chin and good lighting.
  • notes/evaluation.md may exist as an untracked user-supplied file for the next session. It was intentionally left unread and uncommitted during the compaction prep.