Document extraction is not the product. The review loop is.
OCR or an AI model can extract fifteen fields from an invoice. That does not make the workflow reliable.
The useful system also knows:
• which fields are mandatory
• which values must match business rules
• when confidence is too low
• how to detect possible duplicates
• where uncertain cases should go
• how a human correction returns to the process
I treat extraction as one component. The actual product is a controlled path from document intake to an accepted record — with uncertain cases visible instead of silently approved.
Wanting another run even when you are bad at it is a pretty good sign. What took more iteration in Heatwave, the driving feel or the police chase behavior?
Hi! I’m a college student and an aspiring AI/ML engineer who loves building things with technology and turning ideas into real projects.
I built the Arshi Masale website for a local spice business from Sindhudurg, Maharashtra. This project was special to me because it showed me that even as a student, I can use what I’m learning to create something useful for a real business.
I focused on making it modern, simple, mobile-friendly, and ready for future e-commerce features. This is one of the projects that motivates me to keep learning, building, and eventually turn my passion for AI and technology into a career.