GameCult/Epiphany
Archived
Watch
9
0
Fork
You've already forked Epiphany
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Mark Phase 5 complete enough

Browse source
This commit is contained in:
Meta Vens 2026-04-25 15:41:23 +01:00
commit 0dcdfab6d2
6 changed files with 44 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

4
notes/epiphany-current-algorithmic-map.md
View file

@ -110,7 +110,9 @@ Source audit on 2026-04-25 re-read each flow below against the cited code instea
The current landed machine is still coherent. The core shape is not ornamental: one protocol state object flows through session state, prompt rendering, rollout persistence, thread hydration, explicit retrieval/indexing, read-only distillation/proposal, verifier-backed promotion, the single durable update writer, and now a live state notification that reflects completed writes. The useful simplification pressure is already present in the boundaries: retrieval reads, indexing writes only the semantic catalog, distillation/proposal draft patches, promotion gates, update persists, and notification broadcasts only after the write is done.
Nothing in the current typed spine obviously deserves deletion right now. The parts that would turn this into Jenga are still correctly listed as non-flows: automatic tool-output ingestion, watcher invalidation, GUI reflection, specialist scheduling, broad event streaming, and an automatic Compact-Rehydrate-Reorient-Continue coordinator. The next Perfect Machine move is therefore not adding another writer or a shiny surface. After match-kind-aware map-delta judgment, source-output-aware distillation, first risky-delta promotion policy, a richer app-server smoke harness, and the first state-update notification, the next pressure belongs in running that harness as a guardrail and adding only the smallest source-grounded notification/read/proposal/promotion rule real use exposes.
Nothing in the current typed spine obviously deserves deletion right now. The parts that would turn this into Jenga are still correctly listed as non-flows: automatic tool-output ingestion, watcher invalidation, specialist scheduling, broad event streaming, and an automatic Compact-Rehydrate-Reorient-Continue coordinator. Thin GUI/client reflection is no longer forbidden as a category, provided it reflects and steers typed state rather than inventing a second source of truth.
The next Perfect Machine move is not adding another writer, and it is no longer another generic scrape of notification/read/proposal/promotion hardening. That wording turned into a loop hazard: after a phase is coherent, "one more smallest safety slice" can become a polite way to rearrange the furniture forever. The Phase 5 smoke harness should guard the existing control plane against regressions. The next organ should move outward toward a Phase 6 reflection/scene-surface or job-state precursor that lets clients inspect the machine Epiphany already built.
## Natural Language Spine