Grok Bot engineer explains agent trust layer and contrasts Jev for routing decisions
Notes from a workshop on the trust layer behind 800 PRs a month: constraints are hard-coded and routing still relies on frontier model paragraphs, while Jev returns typed options with probabilities at $0.042 per million input tokens.
SpaceXAI engineer behind Grok Bot just dropped a free workshop This 1-hour session on the trust layer behind an 800-PR month: 05:36 - her agents automerged 20 PRs while she slept 10:40 - no verification skill and you become the verifier, the bottleneck 24:01 - a judge agent of a different model cross-checks the score 35:04 - grok bot gives every agent its own identity 48:07 - ci checks turn the build red, rules and bugbot stay soft 57:13 - grok bot is the iMessage moment for everyone outside tech 800 PRs in 12 days. 600 of them refactoring the codebase so the agent stops needing her But every one of those constraints is hard-coded Directory the agent can't import from, a check that fails the build Every routing decision inside that team still goes back to a frontier model, which answers with a paragraph Chatbot used as a switch statement Jev returns typed options plus a probability, $0.042 per million input tokens, and never writes a sentence LLM creates the work -> Jev decides what happens next -> code enforces it Save this before you open another agent tab
This post quotes another post: “Jev turns routing, scoring and verification into a decision layer”