Small decisions. Interesting possibilities.Submit contentSubmit

A draft quality gate

it's f*cking insane Jev sat between GPT and me, killing every draft that broke my rules before i saw it. good setup. then Jev did not answer. the agent decided silence was safer and stopped sending me anything at all. took a second agent to unstick it. your checker needs a branch for the moment it goes quiet: > let it…

Added to Jevfast

How it uses Jev

Input: a draft and the author’s writing rules. Jev appears to flag drafts that violate those rules before GPT output reaches the user. The post also describes a failure when Jev returned no answer; suggested fallbacks are advice, not confirmed implementation. Exact Jev request and answer shape are undisclosed.

Why it is interesting

The example exposes an important boundary case for a writing gate: the caller needs an explicit policy for missing answers. The post does not establish that the proposed recovery paths were built.