This content originally appeared on DEV Community and was authored by eXWarHammer
I’m Edin, and I work in customs/import-export.
I’m building an AI-powered customs classification assistant focused on HS code determination, auditability, and anti-hallucination validation.
The main project is private because it contains domain-specific customs work and beta infrastructure, so I created a sanitized public demo repo and a guest-only live demo for review.
Live demo:
https://carinski-ekosistem-demo.pages.dev
Public demo repo:
https://github.com/kalaba992/Carinski-ekosistem-demo
The demo contains:
- no private data
- no credentials
- no Auth0
- no Convex
- no OpenAI
- no production infrastructure
- synthetic examples only
- illustrative classification outputs only
I’m specifically looking for critical feedback in these areas:
- React / TypeScript structure
- UI/UX clarity
- validation flow
- security risks
- testing strategy
- maintainability
- wording that may create legal/professional overclaim risk
I do not need general praise. I need direct feedback on what is weak, unsafe, confusing, or not production-grade.
Review guide:
https://github.com/kalaba992/Carinski-ekosistem-demo/blob/main/docs/REVIEW_GUIDE.md
If you are willing to help, please open a structured issue in the demo repo using one of the templates.
This content originally appeared on DEV Community and was authored by eXWarHammer
eXWarHammer | Sciencx (2026-05-22T04:03:28+00:00) I built a sanitized public demo of an AI customs classification assistant — looking for critical feedback. Retrieved from https://www.scien.cx/2026/05/22/i-built-a-sanitized-public-demo-of-an-ai-customs-classification-assistant-looking-for-critical-feedback/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.