WHAT NEW IN X11.01 SUN

AI collections from X · 22 collections · 63,170 posts

jevVIDEO

Jev engineering pattern: decide, act, gate

A demo of Jev core routing and planning, tools executing, and a 36-check gate that blocks deploy at 34/36, with humans stepping in only before a route locks, when the gate turns red, and before prod.

Klonzu
@KlonzuArchived 19 days agoOriginally posted 2026.10.12
Klonzu @KlonzuOriginally posted 2026.10.12
Open original on X

holy sh*t. stop letting your agent ship on 34 of 36 green checks while nobody reads the diff let the gate own the deploy, not the model deploy(model) if http://checks.green else repair() Jev core decides: route 4 of 12, 3 branches, plan depth 6 Tools act: 3 tables queried against a schema and a baseline Checks gate: 36 checks, deploy blocked at 34/36, unlocked only at 36/36 A human only needs to step in at three critical moments: → before a route locks: is route 4 of 12 right, or did the router drop a branch? → when the gate turns red: is repair() fixing the 2 failed checks, or just rerunning them? → before prod: did an analyst actually read the diff, or did review.approved get rubber-stamped? Jev decides. Tools act. Checks gate This is the Jev engineering pattern I keep pointing at, one layer down: 1,239 tool calls across 20 blocks and 596 links in 26.97 seconds, and engine.deploy("jev-core-2", env="prod") still waits for one approved review Route once. Gate everything. Ship at 36/36. - the full pipeline setup > 01 ingest: feeds, schema, baseline on 16 signal taps > 02 decide: engine.decide(ctx, policy), then route.plan(depth=6) > 03 query: 3 tables, checks = validate(frame, baseline) > 04 anomaly: 34 of 36 pass, deploy blocked, repair() > 05 + 06: request_review("@analyst"), assert approved, deploy at 36/36 paste this prompt into Claude Code below: "Set up my Claude Code project so nothing ships without a green gate and a human: 1. Add a deploy gate to CLAUDE.md: > Before any deploy command, run the full test and lint suite > If any check fails, fix the cause and rerun, never deploy on a partial pass 2. Add a PreToolUse hook on Bash that blocks deploy and push commands unless the last check run was 100% green 3. Put deploy, push and release commands on ask in .claude/settings.json permissions 4. Before asking me to approve, show: > the full diff, the failed checks and what changed to fix them Show every configuration diff first. Do not apply edits until confirmed"

This post quotes another post: x.com/hanakoxbt/status/2101709924828934222

x.com/klonzu/status/2109404446962962752Archived 2026.10.12 10:04