Comment by Kartik N V J K on "Human-in-the-Loop AI Agents in Django: Approval Gates, Audit Trails, and Evals That Actually Ship"

Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Comment by Kartik N V J K on "Human-in-the-Loop AI Agents in Django: Approval Gates, Audit Trails, and Evals That Actually Ship" | Hashnode

Discussion

CommentHuman-in-the-Loop AI Agents in Django: Approval Gates, Audit Trails, and Evals That Actually Ship

Kartik N V J K

AI Developer | Making AI reliable, trustworthy & accessible to everyone | Active community contributor

Oct 27

export_golden only pulls status="applied", so a draft a reviewer rejected never becomes a test case. I'd keep those rejections in the golden set as negatives with the decision_note attached, because they're the drafts I'd most want a new prompt version tested against.

AI Developer

build production-ready AI integrations, mobile apps, and web platforms for businesses that want real results.

Oct 28

Good call. Keeping rejected drafts as negatives with the reviewer's decision_note makes the golden set cover the failures that actually happened, not just the approved outputs. The main thing to watch is label quality: a rejection can mean a wrong answer or just a style preference, so I'd tag the rejection reason and only treat the clear-cut ones as hard-fail cases in the eval gate.