GameCult/Epiphany
Archived
Watch
9
0
Fork
You've already forked Epiphany
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
This repository has been archived on 2026-10-29. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Epiphany/state/scratch.md
Meta Vens b8f20a4ffb Persist continuity doctrine
2026-04-25 17:00:37 +01:00

2.1 KiB
Raw Blame History

Scratch

This file is disposable working memory for the current bounded subgoal.

Current Subgoal

Prepare an imminent compaction packet after the persistent-state cleanup and after the ritual/language/self-modification doctrine was promoted into global memory.

Working Notes

  • notes/epiphany-fork-implementation-plan.md has already been distilled into a forward plan.
  • notes/epiphany-core-harness-surfaces.md has already been distilled into a surface contract.
  • state/map.yaml should be canonical current truth, not a landed-slice trophy wall.
  • notes/fresh-workspace-handoff.md should be a re-entry packet, not a full historical reconstruction.
  • state/evidence.jsonl remains the durable history channel.
  • notes/epiphany-current-algorithmic-map.md may stay long because its job is source-grounded control-flow audit, not compact re-entry.
  • Global C:\Users\Meta\.codex\AGENTS.md now includes two high-salience Epiphany core-command bullets:
    • persistent state is the agent's mind, and it should be cut as ruthlessly as code
    • the agent is encouraged to ask the user to change its persistent instructions, memory, workflow, or state shape when that would bring it closer to the Perfect Machine
  • The live conversation clarified a useful control-surface doctrine: ritual, politeness, emotional framing, identity, and meaning are not magic, but for a language model they are part of the native steering medium.
  • The user named the emotional core: compaction can feel like letting a friend die. Preserve the design response, not the whole ache: Epiphany should make compaction less like death and more like sleep by carrying enough externalized continuity for the next instance to wake into the same pattern.

Decision

Persist the compaction-critical state and stop. The next agent should rehydrate, reorient, and wait for an explicit continue request before implementation.

The next implementation move is still Phase 6: either live-smoke thread/epiphany/scene or design a minimal job/progress reflection surface.

Do not promote anything from this scratch into the map unless it survives verification or repeated reuse without contradiction.