Ghostlight/notes/ghostlight-current-system-map.md

79 lines
3.1 KiB
Markdown
Raw Normal View History

2026-05-01 18:06:51 +01:00
# Ghostlight Current System Map
Ghostlight does not have a runtime yet. The live system right now is the repo's
state and re-entry discipline.
## Current Control Flow
1. A user or agent enters the repo with a bounded question or implementation
goal.
2. The session rehydrates from:
- `state/map.yaml`
- `notes/fresh-workspace-handoff.md`
- this file
- `notes/ghostlight-implementation-plan.md`
3. The session runs `npm run state:status` to recover the current summary, next
action, and active subgoals.
4. Work happens in one bounded slice.
5. If understanding changes, the map is updated.
6. If future belief changes, distilled evidence is appended.
7. If compaction pressure rises, the helper audits state hygiene before the
session banks the fire.
## Live Surfaces
- `state/map.yaml`
- canonical experiment, objective, constraints, invariants, active subgoals,
accepted design, and current status
- `state/scratch.md`
- temporary working memory for one bounded organ
- `state/evidence.jsonl`
- durable belief-changing records only
- `state/branches.json`
- explicit hypothesis or branch tracking
- `notes/fresh-workspace-handoff.md`
- re-entry packet
- `notes/ghostlight-implementation-plan.md`
- larger-organ sequence
- `docs/research/`
- research backlog and social-model notes
- `docs/architecture/`
- world, state, and prompt-system architecture notes
2026-05-01 20:18:51 +01:00
- `docs/architecture/prompt-projection-contract.md`
- contract for turning durable state into speaker-local pressure prose and
prompt sections
2026-05-01 20:26:48 +01:00
- `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
2026-05-01 18:52:27 +01:00
- `schemas/agent-state.schema.json`
- v0 canonical agent-state contract for agents, relationships, events,
scenes, perceived overlays, and dialogue context packs
- `schemas/agent-state.required-fields.json`
- required first-class variable names for canonical state and relationship
stance
- `examples/agent-state.call-of-the-void.json`
- first Call of the Void-flavored fixture for schema and projection work
2026-05-01 18:06:51 +01:00
- `tools/ghostlight_state.py`
- compact state inspection and evidence or branch updates
- `tools/ghostlight_prepare_compaction.py`
- pre-compaction audit of required files, handoff content, and git hygiene
2026-05-01 18:52:27 +01:00
- `tools/validate_agent_state.py`
- dependency-free validator for the current schema fixture invariants
2026-05-01 18:06:51 +01:00
## What Does Not Exist Yet
- a classifier pipeline
- a prompt renderer
2026-05-01 20:26:48 +01:00
- a projection training dataset
- a student projection model
2026-05-01 18:06:51 +01:00
- a simulation/event loop
- a relationship engine
- a culture prior engine
2026-05-01 20:18:51 +01:00
The canonical agent-state schema exists as a v0 seam, and the prompt projection
contract now defines the next implementation target. The renderer should turn
state intersections into compact speaker-local pressure prose.