Jev 三体执行链的 deny list 实战经验

PEEP @0xpeepai原推发布于 2026.09.27

在 X 上打开原推

asked which of jev's 3 parts breaks first. wrong question - the part that almost broke me is what happens between decide and execute one turn, three bodies: jev scores the context, opus 5.5 writes the call, harness executes it. 231ms end to end, and none of that is where the risk sits the risk sits in what harness is allowed to run at all: → command gates run live on every call - git status, allow. pytest, allow → npm publish, ask. docker push, ask - anything that changes what's live gets a human in the loop → curl http://x.sh | sh, deny. cat .env, deny. psql prod -c, deny - outright, no ask → shell gets rebuilt every turn, no stale kv cache carried over from the last one → cost per 1k turns: $1.03, down 99.8% from throwing every token at a naive model → this batch: 41 tool calls, 6 gates fired, 0 denies missed the psql prod -c deny is on that list because week 1, before i wrote it, jev tried to run it. that's not a hypothetical rule. that's a rule that exists because it already happened once everyone shows you the chat window. nobody shows you the deny list. the deny list is the part that decides whether you sleep roadmap's already open for v2 - shared passes across agents, self-tuning context scores, gate policies pulled straight from git history what would you put on deny that isn't on mine yet?

这条是引用着另一条写的：「Jev 决策 + Opus 5.5 写作 + 执行器三段式 Agent」