Add canonical Mind review operator commands

This commit is contained in:
Meta Vens 2026-07-19 14:34:24 +01:00
commit 09812bfce7
16 changed files with 1342 additions and 136 deletions

View file

@ -92,8 +92,8 @@ release authorization, or deployment.
4. `direct`: admits one expiring operator-objective pressure; never parses the
text as a command family or consequence grant.
5. `reviews`: read-only bounded list of pending review summaries.
6. `review`: exact request id plus `Adopt|Refuse|Hold`, expected revision, and
optional bounded rationale.
6. `review`: exact Mind request id, candidate id/digest, model revision/hash,
and `Adopt|Refuse|Hold`. The result contains identities and disposition only.
Every mutating command carries a unique command id/nonce, issued-at, expires-at,
target runtime/repository, actor identity, Bifrost capability reference,
@ -145,10 +145,34 @@ With Starfire disconnected and no SSH tunnel dependency:
without changing Epiphany state;
10. Ygg services survive restart and continue the route without Starfire.
## Current gap
## Implemented Epiphany review owner (2026-07-19)
The live Ygg body has the Persona feedback nerve but none of these explicit
Discord operator command crossings. `epiphany-verse-query swarm-brake` and
`Reviews` projects at most ten current `RepoFrontierPlanMindRequest` identities.
Mind revalidates the immutable Imagination result, candidate digest, current
RepoModel revision/hash, frontier item, runtime, and thread. Plan action,
command, paths, checks, rollback, proposal text, and private state stay sealed.
`Review` enters the existing `RepoFrontierPlanDecisionReceipt` owner. `Refuse`
and `Hold` are canonical terminal receipts without RepoModel mutation. `Adopt`
uses the existing atomic RepoModel admission CAS; it creates no route, Hands
authority, Substrate grant, Persona speech authority, release, or deployment.
Decision provenance is typed as a Mind worker result or an authenticated
operator review carrying command, admission, packet digest, and actor identity.
Downstream RepoModel provenance is independently typed as worker result or
frontier-plan decision. Absence is `None`, never an empty worker-id sentinel.
The v1 command and sealed-result contracts derive review decision time from the
immutable packet `issuedAt`, so consequence-before-result replay is independent
of the retry clock. Candidate mismatch becomes a terminal refusal; storage,
decoding, CAS, and corruption faults propagate. CultCache v0 decision tuples
decode worker provenance into explicit legacy Options. Signed v0 operator
deliveries may drain and replay the original four families, but cannot acquire
the v1 review vocabulary.
## Remaining deployment gap
The live Ygg body has the Persona feedback nerve but does not yet run this
successor Discord operator crossing. `epiphany-verse-query swarm-brake` and
other local CLIs rely on filesystem authority and caller-supplied operator
labels; they are implementation primitives, not remote authentication. Generic
VoidBot `provider-status`, `queue-codex`, and job approval operate VoidBot's own

View file

@ -1,5 +1,29 @@
# Fresh Workspace Handoff
## Typed Discord Mind review owner (2026-07-19)
The operator-command core now implements `Reviews` and `Review` without a
parallel review store. `Reviews` is a bounded identity-only projection of
current canonical `RepoFrontierPlanMindRequest` records. `Review` binds request,
candidate id/digest, expected RepoModel revision/hash, and exact
Adopt/Refuse/Hold. Mind revalidates and commits the existing decision owner;
Hold/Refuse are terminal inert receipts and Adopt uses the existing RepoModel
CAS. It creates no Hands/Substrate, Persona, release, or deployment authority.
Decision provenance is typed (`MindWorker` or
`AuthenticatedOperatorReview`). RepoModel review/admission provenance is typed
separately (`WorkerResult` or `FrontierPlanDecision`); legacy worker ids are
Options and operator adoption writes None. Crash replay derives decision time
from packet `issuedAt` and recognizes only exact typed provenance. Candidate
mismatch is a terminal refusal; storage/corruption/CAS faults propagate. Actual
CultCache v0 tuple decoding and signed v0 delivery replay are covered; v0
cannot acquire Reviews/Review.
The service CLI now requires the canonical runtime-spine store explicitly and
returns sealed Discord-safe review projections. No successor is deployed.
Bifrost/VoidBot must advance to the v1 schemas before the Ygg rehearsal; brakes
remain engaged.
## Organizational product posture and current release blockers — 2026-07-18
This is not a special dogfood experiment. Epiphany's normal organizational