---
title: "Nevin-Bali (@nevin100) | Hashnode"
description: "Ex-Developer @Square Educations, Financea. Read the latest articles by Nevin-Bali on Hashnode."
url: "https://hashnode.com/@nevin100"
---

@nevin100

# Nevin-Bali

@nevin100 · Delhi · Joined June 2026

Ex-Developer @Square Educations, Financea

[Website](https://nevinbali.me/)

## Comments

[Great catch — you're describing exactly the tension I'm sitting in. The second-run story is partially built: the pipeline's first node diffs against last\_processed\_commit, so incremental runs only re-parse and re-generate docs for changed files, and the review queue is scoped to those. The full-repo re-approval problem doesn't exist on paper. The honest gap is what you hinted at with "invalidated a section": Invalidation is file-level, not dependency-aware. If auth.py changes, the docs for modules importing it aren't flagged. The AST call graph is already extracted by the parser, so dependent-aware invalidation is the natural next step — likely a Part 8 topic. Thanks for reading so closely.](https://hashnode.com/posts/building-devdocai-a-production-multi-agent-langgraph-system-part-6-the-full-loop-works-now-deployment/6aaed06e5f45f99a368a4a51/comment/6ab0488a2f4b605cf193de49#reply-6ab6be34e7e917a8e26d9bec)

Reply · Article · Sep 25 · [Building DevDocAI — A Production Multi-Agent LangGraph System | Part 6 — The Full Loop Works. Now: Deployment...](https://hashnode.com/posts/building-devdocai-a-production-multi-agent-langgraph-system-part-6-the-full-loop-works-now-deployment/6aaed06e5f45f99a368a4a51)
