0 public items
External feedback starts at zero until linked GitHub issues prove otherwise.
Try the public demo, inspect the support-ticket failure, and leave one GitHub issue with what was useful, confusing, or missing. Your review helps turn this project into public, resume-safe evidence.
External feedback starts at zero until linked GitHub issues prove otherwise.
A confirmed user must state that they tried the demo or ran the repo.
GitHub issue count increased after opening the public review request.
The repo verifies agent behavior, API routes, safety boundaries, and evidence artifacts.
The demo analyzes an anonymized support-ticket export. The expected result is a failing quality report with duplicate IDs, missing routing fields, negative amounts, and outlier evidence.
Skim the report snapshot and confirm whether the data-quality failure is understandable.
Open DemoLook for tool-calling, read-only data boundaries, structured evidence, verifier guardrails, and fallback behavior.
Agent Capability MatrixWrite what worked, what confused you, and whether the project feels credible for an AI Engineer internship review.
Submit GitHub Feedbackexternal_feedback_items.If you ran the local repo or replayed the CSV/PostgreSQL path, submit a redacted replay note.
Submit Replay Evidencereproducible_feedback_items.Please do not post raw customer data, secrets, private emails, addresses, tokens, production rows, or private company names. Redacted summaries are enough.