From df0ce95ff77bd6eab6fe366f9390a98590c65a26 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sat, 20 Jun 2026 03:52:26 +0100 Subject: [PATCH] Document repo swarm MVP answer --- notes/epiphany-repo-swarm-mvp-contract.md | 51 +++++++++++++++++++--- notes/fresh-workspace-handoff.md | 1 + state/ledgers.msgpack | Bin 317695 -> 318122 bytes state/map.yaml | 2 +- 4 files changed, 47 insertions(+), 7 deletions(-) diff --git a/notes/epiphany-repo-swarm-mvp-contract.md b/notes/epiphany-repo-swarm-mvp-contract.md index 5f113e0d..21acfc3c 100644 --- a/notes/epiphany-repo-swarm-mvp-contract.md +++ b/notes/epiphany-repo-swarm-mvp-contract.md @@ -838,12 +838,18 @@ a receipt that says what happened without lying about who had authority. ## Full Migration Plan To Repo Swarm MVP -This plan starts from the current state: fourteen native front doors exist, but -the work loop is not yet a full physiology. `init`, `online`, `accept`, -`derive-plan`, `plan`, `run`, `adopt`, `execute`, `close`, `tick`, `publish`, -`overview`, `queue-run`, and `sync` prove the typed path from repo birth to -branch-local scheduler pulse, typed queue selection, Bifrost/GitHub publication -receipts, compact proof-bundle sight, and upstream-main sync proof. +This plan starts from the current state: seventeen native front doors exist, +but the work loop is not yet a full physiology. `epiphany-repo init`, +`epiphany-swarm online`, `epiphany-swarm run`, `epiphany-work accept`, +`epiphany-work persona-intake`, `epiphany-work derive-plan`, +`epiphany-work plan`, `epiphany-work run`, `epiphany-work adopt`, +`epiphany-work execute`, `epiphany-work close`, `epiphany-work overview`, +`epiphany-work export-proof`, `epiphany-work tick`, +`epiphany-work queue-run`, `epiphany-work publish`, and +`epiphany-work sync` prove the typed path from repo birth to branch-local +scheduler pulse, typed queue selection, Bifrost/GitHub publication receipts, +redacted public proof export, compact proof-bundle sight, and upstream-main +sync proof. `tick` now also proves brake refusal, active-turn refusal, completion-anchored cooldown refusal, and stale active-turn recovery through typed scheduler receipts; `serve` now proves bounded cadence around that same @@ -899,6 +905,39 @@ wrapper loop as a daemon soul. Long-running autonomy belongs to Self's scheduler physiology and, when installed as a service, to Idunn-owned lifecycle aftercare around that same scheduler pulse. +### Functional Swarm Answer + +Yes: the machine is headed toward a functional repo swarm, and the current +front doors are no longer decorative. They already prove repo birth, online +local Verse projection, Persona/Bifrost intake, Imagination action-item +receipts, branch-local Hands execution, deterministic Soul/Modeling/Mind +closure, Gjallar-visible proof rows, Bifrost/GitHub publication receipts, +redacted public-proof export, and upstream-main ancestry proof after explicit +merge authority. + +No: the machine is not yet Epiphany Online in the full MVP sense. The remaining +gap is not "more permission prompts." The remaining gap is to make the +existing typed artery run as a living repo organism: + +- richer model-authored safe-family breadth so Imagination can propose more + useful branch-local work without arbitrary shell authority +- richer model-authored closure where Soul and Modeling inspect source and + consequences beyond the deterministic mechanical path +- Bifrost public-proof publication transport beyond local Verse, so redacted + proof bundles can become public Verse / credit / case-study evidence without + Gjallar or Self stealing publication authority +- an Idunn-owned service lifecycle path for the queue-run pulse when the + operator explicitly grants service mutation or elevated host authority +- a fresh-repo acceptance run that proves the whole path without supervisor + contamination + +The MVP is functional when a human can talk to the repo Persona, the swarm can +turn that pressure into typed work, keep advancing lawful branch-local steps +under Self/Hands/Soul/Mind receipts, stop at Bifrost publication gates, export +operator-safe proof, and finally prove sync to upstream main after maintainer +or Bifrost merge authority. That is autonomy with organs, not autonomy as a +single hungry prompt. + ### MVP Status Board Use this board to decide whether a new slice belongs in the MVP or is a later diff --git a/notes/fresh-workspace-handoff.md b/notes/fresh-workspace-handoff.md index 65f1674e..b543139b 100644 --- a/notes/fresh-workspace-handoff.md +++ b/notes/fresh-workspace-handoff.md @@ -114,6 +114,7 @@ remembers doctrine; the branch remembers the blade. - 2026-06-20: Published/credited proof-bundle rows are live. `epiphany-work overview` now adds `publicationRows` to `epiphany.repo_work_proof_bundle.v0`, lifting Bifrost intent/publication/GitHub/ledger/credit/PR fields, Hands commit/PR fields, and upstream-main ancestry fields from publish/sync receipts without granting publication, merge, scheduler, service lifecycle, cross-repo, or private-state authority. Disposable proof `.epiphany-smoke\checklist-note-20260620-031347\12-overview-published-proof.json` ran close -> publish -> sync -> overview after the checklist safe-family proof; overview reported `complete-or-awaiting-new-work`, `upstreamMainSynced=true` from `authority.upstreamMainSynced`, three publication rows, and `privateStateExposed=false`. The next cut is richer public/export packaging outside the local bundle or model-authored closure, not basic Bifrost/GitHub/sync row visibility. - 2026-06-20: Public proof export is live. `epiphany-work export-proof` calls overview, distills the local `epiphany.repo_work_proof_bundle.v0` into redacted `epiphany.repo_work_public_proof_bundle.v0`, and writes `.epiphany/public/proof-bundles/repo-work-public-proof-.json` by default without raw receipt bodies, local receipt paths, expected paths, worker thought, publication authority, or private Verse exposure. Disposable proof `.epiphany-smoke\checklist-note-20260620-031347\13-export-proof.json` reported eight artifact rows, three publication rows, zero artifact path fields, `rawReceiptBodies=false`, and `private=false`. The next cut is Bifrost/public Verse transport for exported proof, richer model-authored safe-family breadth, or richer model-authored closure; not another local public-proof export wrapper. - 2026-06-20: Public proof local Verse transport is live. `epiphany-work export-proof --local-verse-store \.epiphany\local-verse.ccmp` now mirrors each redacted export as `epiphany.cultmesh.repo_work_public_proof.v0` under `gamecult-local/repo-work-public-proof/latest`, with compact `PUBLIC-PROOF` TUI rows, artifact/publication row counts, public proof artifact ref, SHA-256, upstream-main sync truth, and `privateStateExposed=false`. `epiphany-verse-query swarm-overview` reads those rows as `repoWorkPublicProofRows` / `repoWorkPublicProofTuiRows`, exposes `latestRepoWorkPublicProof`, and adds non-mutating/non-elevated `repo-work-public-proof` action rows owned by Gjallar sight while Bifrost still owns publication/credit consequence. Disposable proofs `.epiphany-smoke\checklist-note-20260620-031347\14-export-proof-verse.json` and `15-swarm-overview-public-proof.json` reported latest `repo-work-public-proof-checklist-request`, one public proof row, one action row, SHA-256 `e781e09c2ba340c8818d3ef95e54085ccd0c92c6a3b5f73cc4878fb224e49dff`, `mutates=false`, `elevated=false`, and `private=false`. The next cut is Bifrost/public publication transport beyond local Verse, richer safe-family breadth, or richer model-authored closure. +- 2026-06-20: `notes/epiphany-repo-swarm-mvp-contract.md` now has the explicit functional-swarm answer. The current seventeen front doors are real proof surfaces, not decorative wrapper smoke, but Epiphany is not fully online until the typed artery can run as a living repo organism: richer model-authored safe-family breadth, richer Soul/Modeling closure, Bifrost public-proof publication beyond local Verse, Idunn-owned queue-run service lifecycle under explicit operator authority, and a fresh-repo acceptance run without supervisor contamination. Use that section when answering whether Epiphany is headed toward a functional swarm. - 2026-06-20: Gjallar/swarm-overview now exposes repo-work overview history as first-class compact sight, Persona's public Eve surface lowers the same queue for peer-readable collaboration, and Self has a first runnable queue surface over it. `SwarmOverviewOutput` and `SwarmTriageOutput` include `repoWorkOverviewCount`, `repoWorkOverviewRows`, `repoWorkOverviewTuiRows`, `latestRepoWorkOverview`, `latestRepoWorkGate`, `latestRepoWorkBlocker`, and `latestRepoWorkNextSafeMove`; the shared `swarmActionRows` queue gets priority 35 `repo-work-overview` rows owned by Gjallar, hosted body `repo-work`, authority gate `repo.work.overview`, effect class `repo-work-readback`, no mutation, no elevation, proof-bundle ref, and private-state seal. `eve-surfaces`, direct `connect-eve`, and the globally invokable Persona `eve-connect` daemon tool readback expose public `REPO-WORK-PEER` rows with item, gate, blocker, next safe move, branch, publication, sync, and `private=false`. `epiphany-work queue-run` reads the same typed queue, selects current-repo rows at `ready-to-run`, `ready-to-adopt`, `ready-to-execute`, or `awaiting-closure`, delegates to `tick`, refreshes overview after real advancement, and wrapper `repo-work-queue-run` exposes the operator surface. Disposable proofs `.epiphany-smoke\gjallar-repo-work-queue-20260620-012027`, `.epiphany-smoke\eve-repo-work-queue-20260620-013322`, `.epiphany-smoke\queue-run-20260620-014314`, and wrapper artifact `local-20260620-014627-174-aada0241` prove two-item queue sight, Eve lowering, direct queue-run advancement, and wrapper dry-run without publication, merge, service lifecycle mutation, elevation, cross-repo mutation, or private-state exposure. The next cut is richer Persona-to-Imagination plan derivation, not another queue display surface. - `service-execution-runbook` makes that next cut repeatable: it generates the exact elevated wrapper command sequence without mutating the service manager, continues after per-step failure to preserve more receipts, runs `service-execution-audit` in `finally`, exits nonzero if any step failed, and seals a typed runbook lifecycle receipt. Run the generated artifact only with explicit operator authority. - `service-execution-audit` is the non-mutating acceptance proof after the elevated rite: it reports `complete` only when typed lifecycle receipts prove the runbook witness plus expected elevated chain, and otherwise reports the missing/failed sealed checks. diff --git a/state/ledgers.msgpack b/state/ledgers.msgpack index 428dd4d1806f83d9c482604842dc8bc32468dd9b..0d273f1e243db13aff286288a2b11934d0a5b3ff 100644 GIT binary patch delta 386 zcmX9)J4*vW5cZMavhjfp$RbArHn>z+^Nb1oGN|)v7=XL(b5o zGWdcmX5eIwkjtSqy3uMt=Mkk0M+5A_k&YRhhcXO|R_WY(e#j;|46tI#z_5zZBGpCG zNfwAw9#b?J1q_(lK=ov+-8l@DMR~j~qnh?G&!K(QjUUKB#>VK1)MCjXmBP|XQn7a+ IFcGlx2Wfzd761SM delta 49 zcmZ3rRrvo#;SCau+$Kg=CMHqG7+9{~*{sZ1$jB(&Je8?^Dib3RgJ|aMQ<+$@t^ok4 C!w^~k diff --git a/state/map.yaml b/state/map.yaml index dd70ed0a..b22b3a85 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -634,4 +634,4 @@ current_status: - `tools/epiphany_local_run.ps1 -Mode swarm-online-runbook` now emits an explicit Idunn preflight summary before the operator elevation boundary. Its JSON and one-line summary report `preflightStatus`, child artifact present/hash-verified/mismatch/missing counts, aggregate service execution failed/missing check counts, child preflight rows with expected/actual SHA-256s, and private-state exposure. Live proof `local-20260619-025627-410-9724e2f6` generated the non-mutating parent artifact with `preflightStatus=ready-for-elevated-operator`, two child runbooks present, two hashes verified, zero mismatches, zero missing artifacts, eleven failed sealed service checks, zero missing checks, explicit aftercare audits, and `privateStateExposed=false`. The remaining scar is still explicit elevated operator execution followed by complete Idunn audits, not missing parent/child artifact readiness. - Service lifecycle receipt history is now event-only: `load_epiphany_cultmesh_daemon_service_lifecycle_receipts` filters out the `epiphany-local/daemon-service-lifecycle-receipt/latest` mirror, while `load_latest_epiphany_cultmesh_daemon_service_lifecycle_receipt` remains the latest-state reader. Focused unit test `service_lifecycle_receipt_history_excludes_latest_mirror` proves two per-receipt writes return exactly two history records and latest points at the second. Fresh smoke `verse-query-lifecycle-history-filter-smoke` and live overview/triage `local-20260618-145632-497-efac6f0d` / `local-20260618-145632-321-867947af` prove compact swarm sights still expose service lifecycle attention plus the present elevated runbook artifact without daemon pokes or service mutation. Do not use a broad unscoped cargo test filter for this check on Windows; it fans out across bin harnesses and hit a broken pipe during this pass. - `epiphany-verse-query seed-compact` is the compact seed receipt for wrappers and read-only rites. The older `seed` command still prints the full local Verse context for explicit debugging, but compact wrapper modes now avoid full `seed`/final `query` readback after the combined overview proof exposed Windows debug stack overflow from full-context serialization pressure. - next_action: Continue repo-swarm MVP work from the documented Epiphany Online cut order in `notes/epiphany-repo-swarm-mvp-contract.md`. Typed Gjallar repo-work history/queue sight, peer-readable Persona Eve lowering, Self-owned `epiphany-work queue-run`, bounded `epiphany-swarm run`, execute-to-close scheduler handoff through `close-from-execute`, deterministic `derive-plan` families `append-worklog`, `planning-note`, and `checklist-note`, typed Imagination action-item receipts over allowlisted safe families, hash-backed local proof bundles with Bifrost/GitHub/credit/PR/upstream-main publication rows, redacted `epiphany-work export-proof` public bundles plus local Verse `epiphany.cultmesh.repo_work_public_proof.v0` Gjallar readback, Idunn-hosted non-mutating queue-run lifecycle plan/runbook receipts, and the speech-audited `epiphany-work persona-intake` mouth plus wrapper `repo-persona-intake` are live with `privateStateExposed=false`; the next cut is Bifrost/public publication transport beyond local Verse, deeper model-authored safe-family breadth, or richer model-authored closure. Preserve Idunn service lifecycle ownership and existing CultMesh/Odin/Eve tool directories; service install/start execution still requires explicit elevated operator authority. + next_action: Continue repo-swarm MVP work from the documented Epiphany Online cut order in `notes/epiphany-repo-swarm-mvp-contract.md`. Typed Gjallar repo-work history/queue sight, peer-readable Persona Eve lowering, Self-owned `epiphany-work queue-run`, bounded `epiphany-swarm run`, execute-to-close scheduler handoff through `close-from-execute`, deterministic `derive-plan` families `append-worklog`, `planning-note`, and `checklist-note`, typed Imagination action-item receipts over allowlisted safe families, hash-backed local proof bundles with Bifrost/GitHub/credit/PR/upstream-main publication rows, redacted `epiphany-work export-proof` public bundles plus local Verse `epiphany.cultmesh.repo_work_public_proof.v0` Gjallar readback, Idunn-hosted non-mutating queue-run lifecycle plan/runbook receipts, and the speech-audited `epiphany-work persona-intake` mouth plus wrapper `repo-persona-intake` are live with `privateStateExposed=false`; the contract note now explicitly answers that Epiphany is headed toward a functional repo swarm but is not fully online until the typed artery runs as a living repo organism. The next cut is Bifrost/public publication transport beyond local Verse, deeper model-authored safe-family breadth, or richer model-authored closure. Preserve Idunn service lifecycle ownership and existing CultMesh/Odin/Eve tool directories; service install/start execution still requires explicit elevated operator authority.