Tighten agent state schema from evaluation

notes/fresh-workspace-handoff.md

@@ -38,6 +38,8 @@ Ghostlight now has the persistence spine plus the first architecture payload:
 - 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
@@ -62,6 +64,15 @@ state unless explicitly revived.
 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

notes/ghostlight-current-system-map.md

@@ -45,6 +45,10 @@ state and re-entry discipline.
 - `docs/architecture/projection-distillation-plan.md`
   - plan for using a frontier teacher model to generate reviewed projection
     artifacts before training a smaller student projector
+- `docs/architecture/schema-future-mechanisms.md`
+  - parking lot for appraisal, transition, belief, action, conversation,
+    resource, dyad, institution, memory, and embodiment mechanisms not yet
+    promoted into the v0 schema
 - `schemas/agent-state.schema.json`
   - v0 canonical agent-state contract for agents, relationships, events,
     scenes, perceived overlays, and dialogue context packs

notes/ghostlight-implementation-plan.md

@@ -23,6 +23,10 @@
 3. Build the prompt projection layer for authoring.
    - Use `docs/architecture/prompt-projection-contract.md` as the first
      renderer contract.
+   - Use `docs/architecture/schema-future-mechanisms.md` to keep appraisal,
+     transition, belief, action, conversation, resource, dyad, institution,
+     memory, and embodiment needs visible without prematurely bloating the v0
+     agent-state schema.
    - Render scene and dialogue scaffolds from structured state, relevant
      memories, scene pressure, cultural defaults, and perceived state.
    - Keep the prompt renderer a projection surface instead of a second brain.