The collectionby Ujjwal PrakashSOURCE INSPECTED
RésuméContact
UJJWAL PRAKASH / INDEX

Follow your
curiosity.

Bengaluru, IndiaProduct / AI / Systems
A shorter way through the work.

Choose a destination or press its number.

Ctrl / ⌘ K · Esc to close · Optional audio

02 / Feedback synthesisWorking prototype
← All works

DISTILL

Less scattered feedback. More useful questions.

Customer feedback arrives as fragments. Product teams need to inspect the themes without losing sight of the original input.

Inspect the implementation ↓
DISTILL — Actual source UI in an isolated local render. Built-in sample data; fixture analysis, no live model call.
Actual source UI in an isolated local render. Built-in sample data; fixture analysis, no live model call.
MY CONTRIBUTION

Independent product work; detailed authorship and collaborator attribution remain to be documented.

TECHNOLOGY

React / TypeScript / Vite / Tailwind

VERIFICATION

Inspected 2026-10-31
Original development date unverified

01 / THE PRODUCT

What you can
actually inspect.

  • Text input and text-file upload
  • Built-in demo data and analysis panels
  • Inbox, roadmap and detail drawer views
  • Model selection and provider request source

Demo output is a fixture. Provider code is present but real model output was not tested. Integration switches change local state; they do not establish connected services. Source includes invented fallback counts, so counts are not evidence of customer demand.

DISTILL / LIVE ANALYSIS

Bring your own
raw signals.

Find possible themes in feedback using DeepSeek. Review the output against the original words.

Submitting sends this text to DeepSeek. Use synthetic or non-sensitive feedback; don’t include private customer details.

Open the working DISTILL sample workspace

Choose “Load Demo Data” to inspect the sample workspace. Synthetic authentication; live models and external services disabled.

Open the sample workspace in a separate tab ↗
Actual source components / isolated capture · Built-in fixture analysis; no live AI.
02 / A CLOSER LOOK

The decision
inside the interface.

Keep raw input beside the synthesis, and make the boundary between sample output and live analysis explicit.

Present-day source analysis, not historical research.

Under the hood / source evidence
  • src/App.tsx
  • src/context/DistillContext.tsx
  • src/components/InputSection.tsx
  • src/services/openai.ts
  • Isolated demo-mode browser capture

Actual source UI in an isolated local render. Built-in sample data; fixture analysis, no live model call.

03 / STILL OPENA working question

How can each synthesized claim be traced back to its actual source, without invented counts?

Usability and outcomes still need evidence.

Discuss the product