LOOP

Multi-tenant customer feedback platform turning raw tickets, surveys, and CSVs into grounded themes, trends, and cited answers scoped strictly by organisation and role.

Organisation: Zidio Development (Bengaluru, hybrid internship · team project)
Role: Full-stack developer (internship)
Timeline / Repo: Aug – Sep 2026

Traceroute path · 7 hops

Each hop isolates problem, constraints, architecture decisions, verification artifacts, and limits.

- Teams needed one workspace to ingest support comments via CSV, API, or manual entry.
- Every trend or AI-generated answer had to cite specific underlying feedback items instead of synthesizing unverified summaries.
Next hop follows below
- Strict organisation isolation across four roles: owner, admin, analyst, viewer.
- Evaluators needed deterministic local execution without external paid LLM API keys.
- CSV exports required protection against spreadsheet formula injection (=, +, -, @ prefixes).
Next hop follows below
- Implemented CSV ingestion with header mapping and Zod row validation alongside manual/API ingestion paths.
- Separated UI role awareness from server-side permission assertions; defined Row Level Security policies in schema migrations.
- Built a heuristic fallback classifier/trend comparator so core workflows run offline when no LLM key is set.
Structural schematic · Illustrative (not measured telemetry)
Illustrative pipeline: CSV/API ingestion -> validation -> org-scoped storage -> trend & Ask LOOP citation path.
Next hop follows below
- Repository contains full application source, schema migrations, and unit test suite.
- Note: UI screenshots have not yet been committed to this portfolio repository.
Asset status (screenshot): UI screenshot asset not yet provided in portfolio repo (logged in GAP-07). Inspect code directly via GitHub.
GitHub: kantimohanthy/zidio-Web-dev
Next hop follows below
- Covered modules: trend engine, tenancy & role enforcement, CSV parser/escaper, fallback analyzer, Ask LOOP grounder, and permission helpers.
- Executed locally by me (commit 1b898e9, pushed 29 Sep 2026). This count reflects LOOP's repository suite only, separate from this portfolio's tests.
Recorded verification command
```
npx vitest run  # 6 files · 13 tests passing (commit 1b898e9, 2026-10-03)
```
Next hop follows below
- The evaluator demo runs on seeded sample data with one-click role switching — demo behavior, not production persistence or adoption.
- RLS policies exist in SQL migrations; they have not yet been verified via live multi-user Supabase queries.
- Playwright end-to-end tests were not run, and no public demo URL is hosted yet.
Next hop follows below
- Run Playwright E2E scenarios verifying viewer vs owner isolation against an active Postgres/Supabase instance.
- Commit verified UI screenshots into the evidence ledger.