Ghostlight/notes/fresh-workspace-handoff.md

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
• evaluation follow-up docs:
  • docs/architecture/schema-future-mechanisms.md
• 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

An older corridor-crisis game slice is not the current build target. It can remain fertile story ground, but it should not steer Ghostlight's implementation state unless explicitly revived.

Current Next Action

Define the projection example schema and create the first reviewed Cat/Oz projection artifacts from the Call of the Void fixture.

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

The projection path is:

• build a deterministic speaker-local input slicer
• define schemas/projection-example.schema.json
• create reviewed Cat/Oz projection examples
• 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.