04Product

PawVeda

It decides on the device before any model speaks.

StatusWeb app live · Android app in internal testing on Playpawveda.vercel.app

PawVeda running on a device: a wellness score of 74 for Bruno marked ON YOUR DEVICE, a symptom check, and quick actions for weight, medication and a vet brief. A DEMO DATA chip labels the sample content.
The shipped app, four screens

the problem

A model alone should not make this call.

A worried owner typing symptoms at midnight does not need a fluent paragraph. They need to know whether this is a vet visit, and a decision like that cannot rest on generated text alone.

what I built

Rules first, model second.

Built with a co-founder. A local rules engine scores the symptoms on the device first, then the model adds context. The local verdict is computed before the model runs and travels attached to the response, so the app can always say what it decided even if the model says nothing at all.

how it stays honest

Anything not real says so on the screen.

Every surface that is mocked, scripted or local only carries a label saying what it is: one chip with eight states, used across thirty two files. Every generated image is logged with the prompt that made it, the model, the date and where it is used.

That discipline includes this page. The capture here is the shipped Android build running on a device, and you can see the demo data chip in the screen itself.

on the record

Status
Web app live · Android app in internal testing on Play
Writing
45 published posts
Built with
React and Vite on the web · Expo for the app
Next case05 PravahaAll work