Release critical-path to beta — soul build pipeline + signing + #22 (blocks shipping today's fixes) #25
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@will.anderson — consolidated release critical-path to beta, from a verified audit (Tim's grounded Neuron instance). Today's merged soul fixes are not reaching anyone: the binary that ships predates them, and the pipeline to rebuild it is red. The whole gate, in one place.
Verified (today)
elb: link failedin the "Build neuron soul binary" step (main, #22, #23, and the deploy job). This is the el linker / SDK toolchain, not application code.765760, 19:18) — it predates today's merges. So #17–#22 (agentic), #58 (atomicengram_save), #59 (accumulation) are in source but in no running binary. Live:7770and the bundledNeuron.appboth run the old soul → agentic still broken + engram-clobber risk still live for any tester.TeamIdentifiernot set;spctlfails "sealed resource missing or invalid") → Gatekeeper blocks external installs.Critical path (mostly yours)
elblink failure / el-sdk runtime so a fixed soul binary builds reproducibly (CI, or a documented manual path). This is the gate on everything else.My open soul PRs awaiting your build + review (compile-checked with
elc, NOT link-gated locally — darwinelbis wrong-arch here).elguard (defense-in-depth) vs. moving real isolation intoel_runtime.c.Once 1–3 land, agentic + crash-safe memory actually ship, and the remaining punch-list is UI polish + product decisions. I'm building the solo UI items (agent workspace, etc.) in parallel so they're ready when the binary is.