WHAT NEW IN X10.29 THU

AI collections from X · 22 collections · 58,925 posts

jevIMAGE

Putting Jev between agent proposals and tool execution as a permission gate

An 8-page architecture guide for using Jev to make typed allow/confirm/review/deny decisions on each agent action proposal, leaving authority to deterministic policy and injecting credentials only inside the executor.

morph
@morpphhhawArchived 2026.09.28Originally posted 2026.09.27
Putting Jev between agent proposals and tool execution as a permission gate
morph @morpphhhawOriginally posted 2026.09.27
Open original on X

Jev + MCP + coding agents is how you stop treating a prompt like a security policy Claude Code and Codex can plan, edit, test and call tools. the dangerous part starts when the same agent also decides whether its own action is allowed so I mapped the architecture into an 8-page guide for putting Jev between an agent’s proposal and the tool that creates the effect: step 1 → describe every consequential action as a proposal before it runs: objective, target, arguments, side effects, safeguards and reversibility step 2 → normalize that proposal in code: resolve paths, account IDs, environments and budgets before any model sees it step 3 → ask Jev atomic typed questions: choose allow / confirm / review / deny, score risk and estimate whether the stated policy is satisfied step 4 → keep the full probability distribution. the winning label alone hides whether the decision was obvious or almost tied step 5 → let deterministic policy grant authority. a confident model answer cannot override missing approval, wrong scope or a blocked effect class step 6 → gate effects instead of tool names: read, draft, write, publish, deploy, spend, delete and access changes each get a different policy step 7 → issue short-lived authorization objects bound to exact targets, expiry and operation count step 8 → inject credentials only inside the executor after authorization. secrets never enter Jev state or the agent’s proposal step 9 → record the proposal, Jev distribution, policy result, executed effect and returned evidence under one decision ID step 10 → start in shadow mode, then automate reads, searches, drafts and tests before touching publication, deployment or money the resulting stack is clean: Jev judges a bounded question. code owns permission. Claude Code, Codex and browser agents execute only the effects they were authorized to perform the complete 8-page Jev + MCP + Coding Agents guide is in the comment section ↓

This post quotes another post: x.com/morpphhhaw/status/2102740313953439950

x.com/morpphhhaw/status/2104220888144990597Archived 2026.09.28 10:02