From 9b4b1b41a8a5d3bdfe03cdf5b2ed59ae47cc6bc8 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sun, 19 Jul 2026 19:26:36 +0100 Subject: [PATCH] Record status-truth Yggdrasil promotion --- notes/fresh-workspace-handoff.md | 18 ++++++++++++++---- state/ledgers.msgpack | Bin 541963 -> 542378 bytes state/map.yaml | 6 +++--- 3 files changed, 17 insertions(+), 7 deletions(-) diff --git a/notes/fresh-workspace-handoff.md b/notes/fresh-workspace-handoff.md index 9609be64..416422cd 100644 --- a/notes/fresh-workspace-handoff.md +++ b/notes/fresh-workspace-handoff.md @@ -5,10 +5,10 @@ Epiphany's ordinary organizational product path is now deployed on Yggdrasil, not merely proven in local smoke. Bifrost authorized each exact upstream release and Idunn produced successful deployment receipts for Epiphany -`714187812f778160882e204ea4f369423578a195`, Bifrost +`bcff32827a39ca793c3062cc71e02aeeac1b091f`, Bifrost `6491f449cf0dbfa952b409de90ccdf511669a60b` with CultLib `693df0901d75cfd8e3a0a5225e270011eeddb0be`, and VoidBot -`74abfed109e1d793034796e5eff1562b0aa6c8de`. +`26093ace0e4b5d15370bd29e3118fb27c807afa0`. All Epiphany resident services, Idunn, and VoidBot are active. The Bifrost Persona-feedback sidecar is healthy under its own `bifrost-feedback` service @@ -27,9 +27,19 @@ Resident readiness is active and release-authenticated with semantic projectors point at the Ygg-local Qdrant/Ollama path. The Epiphany release id is -`sha256-4ad609a797afbc4e7a06251463c0a52faf760880892b6fe6cb7f9ff239e4c460` +`sha256-e0a9eb079250d3f769040255f3d2805286488896c6e2c38222748d2298daf913` with witness -`sha256-0e4bd42640352b932af8c0395efd473dfc9e799c3020a1774fc86bc7d5f39342`. +`sha256-dd84cfeb730061ee38edae5d8de104b65e1cb2f3c723d62e087b68974eac814e`. + +This promotion exposed an Idunn packaging actuator fault before outage: +`mktemp` pre-created the path later passed to Docker as `--cidfile`, so Docker +refused the run before any service mutation. Ops commit `71beacf` now gives +Docker a nonexistent child path inside a fresh temporary directory and cleans +the exact recorded container. The first two Epiphany promotion attempts failed +closed; the corrected retry admitted the exact release above. VoidBot's audited +artifact is `c513c8591baa931fd47b5ee5e29578f2af58af49637d4a88a44b4bda63821af8` +and its Idunn release is `20260719T182219Z-26093ace0e4b`. The final root checker +passed with no failed units and the canonical brake still engaged. The next proof is organizational interaction, not another deployment: use Discord to request `/epiphany status` and submit ordinary repository feedback diff --git a/state/ledgers.msgpack b/state/ledgers.msgpack index 1db59d813ad57daf7f73737c5f5c4f92fd19eba5..24c0b9127e0a54173c8bc93de63ebeefbf0e6774 100644 GIT binary patch delta 450 zcmXw#F;5&Z5QW)GfNN-olqSuf)JtqHce{IZM=0o{NJ%$qk9RHZ?8WvTP*G4I5vAkA ze@GRSBFZ1g?}{&o;?p$q-n@C=?hk%^Klu4J+pA_`GMgNI{kt_jz5De(yU4Q9?Rs># z9%YHme3f{e*iP&uc7Lx&es^>6rEQhRU=|P}#v$a< z53z&ZyQPc9Sy+)b+K`&TX>a-t?KLz~>q1nb#G;m1)`cwCR7hEJVgiX!@`lx116l>2 zol$caK}=a)pd>~|%|!7@QL;weh?)w{E8U1vR;)yg4A2uS%!(j(-VJRBbcHg)+-UDY z{BWiQYXMVA=S{pm2Je!+Csf8#2p~I>=j5Ts5GcTKFru^NY>OjD?JhjLlP-+NUxx0x^hY24WT_}k6P*A6 diff --git a/state/map.yaml b/state/map.yaml index 1efbe9ab..935ed7d8 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -18,7 +18,7 @@ experiment: sleep_brake_semantics: "An engaged swarm brake is sleep mode, not daemon death. Resident services may remain supervised, publish liveness/health, refresh leases, and expose read-only operator sight. The brake blocks cognition launches, scheduling that creates cognitive work, Hands consequences, publication, and deployment action." swarm_brake_authority: "The only physical brake truth is the runtime-scoped CultMesh key epiphany-local/swarm-brake. Observation uses swarm-brake-status and is byte-pure; mutation uses swarm-brake-set and requires explicit engaged/released status, canonical document id epiphany/swarm-brake, actor, and reason. Legacy swarm-brake/brake commands refuse. The stable owner is epiphany.swarm-brake; command actors are provenance, not owners. Release refuses absent or foreign/legacy identity. Idunn alone may adopt an already-engaged legacy head into the canonical identity during deployment, without any released interval. Discord Sleep preserves foreign brakes; Wake releases only the exact canonical owner. Resident readiness reads the same key, and deployment admission requires brakeEngaged=true before service restart." discord_mind_review_owner: "The typed Discord operator core routes Reviews/Review into the canonical frontier-plan Mind owner, not a parallel queue. Reviews exposes only bounded request/candidate/model/frontier identities. Exact Adopt/Refuse/Hold revalidates immutable Imagination and current RepoModel bindings; Hold/Refuse are terminal inert receipts; Adopt alone uses the existing RepoModel CAS and creates no Hands authority, Substrate grant, Persona speech, Bifrost release, or Idunn deployment. Decision provenance is typed as Mind worker or authenticated operator command/admission/packet/actor; downstream RepoModel provenance is typed as worker result or frontier-plan decision, with Option absence instead of empty sentinels. Replay time derives from immutable issuance, machine faults are not terminal refusals, CultCache v0 decision tuples decode explicitly, and signed v0 deliveries may drain only the original four commands. The v1 Epiphany/Bifrost/VoidBot chain is deployed on Yggdrasil behind an engaged canonical brake; the remaining proof is operator-safe Discord interaction, not schema or deployment work." - discord_status_truth: "The currently deployed Status command reads a narrow coordinator snapshot and the independently owned swarm brake. It does not authenticate or compose packaged-release, resident-readiness, Idunn, or Bifrost health. Successor source namespaces every legacy coordinator display field as coordinator-snapshot/, coordinator-state/, and coordinator-action/, and explicitly refuses to call them deployment/provider readiness. The final Discord status product contract requires owner-authenticated typed projections from each named provider; PID sight, generic ready strings, and caller booleans are forbidden substitutes." + discord_status_truth: "The deployed Status command reads a narrow coordinator snapshot and the independently owned swarm brake. It namespaces the coordinator fields as coordinator-snapshot/, coordinator-state/, and coordinator-action/; VoidBot labels them Coordinator snapshot and Coordinator action. It explicitly refuses to call them deployment/provider readiness and does not authenticate or compose packaged-release, resident-readiness, Idunn, or Bifrost health. The final Discord status product contract requires owner-authenticated typed projections from each named provider; PID sight, generic ready strings, and caller booleans are forbidden substitutes." status: active phase: phase_6_reflection_boundary premise: > @@ -56,8 +56,8 @@ objective: deployment remain separate authorities. Eve/CultUI is downstream display. yggdrasil_deployment_readiness: > Yggdrasil is the ordinary organizational runtime. VoidBot and Bifrost are - live at exact Bifrost-authorized upstream commits: Epiphany 71418781, Bifrost - 6491f449 with CultLib 693df090, and VoidBot 74abfed1. Idunn recorded successful + live at exact Bifrost-authorized upstream commits: Epiphany bcff3282, Bifrost + 6491f449 with CultLib 693df090, and VoidBot 26093ace. Idunn recorded successful deployment receipts for all three. Epiphany's packaged release and witness authenticate, all resident services are active, the operator command nerve is loopback-only on 17875, Bifrost Persona feedback and operator worker are