Building an AI Workflow That Can Reject Its Own Output
Most AI workflow demos follow a familiar pattern: connect a few model calls, pass the output of one into the next, and show the final result. The interesting engineering problems begin when one of those calls returns something that is valid JSON but wrong, or when a reviewer confidently approves an artifact it should have rejected. I ran into those problems while building FictionForge, a story-planning workflow I worked on as part of an applied AI engineering project....