RUN LIVE prem@runtime · v3.0 --:--:-- IST pipeline projects skills contact
$ whoami · mumbai, in

Prem
Jethwa

Full-stack engineer, 7+ years deep — React & React Native up front, event-driven Node/TypeScript underneath. These days I point that stack at agent systems that survive production: queues that hold, sends that can't go out half-formed, human checkpoints where they matter.

7+ yrs · full-stack → agents TypeScript · Node · React Claude · LLM pipelines
Prem Jethwa — phosphor-dithered portrait
subject · prem.jethwa
status · building agents
01 · what my agents look like

A live run, not a diagram.

This is the actual shape of my job-hunt agent — and of every agent I ship. Deterministic filters before any model call, batch scoring to amortise prompts, and a human gate before anything irreversible. Watch the tokens: nothing crosses a checkpoint on its own.

2 human checkpoints 0 unsupervised sends $0 spent on hard-filtered roles Thompson sampling on outreach voice
02 · selected systems

Each one runs. Right here.

Every card carries a live miniature of the system it describes — because "trust me, it works" is not an engineering argument. Agents up top; the full-stack products underneath them — storefronts, dashboards, mobile apps — further down.

Agent · Feedback loops

agent-job-hunt

An agent that runs a senior job hunt end-to-end: sources roles, scores them in batch, drafts outreach — and learns which voice gets replies via a Thompson-sampling bandit. Human approval over Telegram at every send.

direct
.42
warm
.33
curious
.25
TypeScript · BullMQ/Redis · MongoDB · Claude CLI · Telegraf · IMAP
Orchestration

Ashmero Orchestrator

The control plane behind my product suite: per-project FIFO queues, job lifecycle with cancel scoping, state-preserving releases with WAL checkpoints — v0.14.8 after a structured 7-bug audit cycle.

Node.js · SQLite WAL · Telegram control · Claude CLI subprocesses
In production · Brightstar Lottery

Jira Bug-Fix Agent

Pulls assigned bug tickets, proposes a fix, applies it, opens PRs against upstream and base — with a human checkpoint at every step. The agent proposes; a person stays accountable for what lands.

TICKET
FIX
✋ HUMAN
PR
Node.js · Jira API · GitHub API · Claude
Media pipeline

Reelchain

A reel-rendering monorepo with a headless export worker: Playwright captures an image sequence frame-by-frame, ffmpeg assembles with HDR→SDR tonemapping, BullMQ keeps cancellation honest across tab unloads and restarts.

queued…0%
Turborepo · Playwright · ffmpeg · BullMQ · Zustand
Computer vision · SaaS

Ashmero Image Studio

Jewellery photo studio in the browser: multi-engine background removal (RMBG-1.4 / BEN2), brand overlays on a Konva canvas, plan-gated catalog PDF export. Drag the divider — raw phone shot to studio-grade.

RAW UPLOAD
STUDIO OUTPUT
React/Vite · Node · MongoDB · Cloudflare R2 · BullMQ
Conversational AI

Ashmero Outbound Agent

Multi-channel outreach across WhatsApp, Instagram and email with fuzzy identity linking, a conversation-scoring engine and a Hinglish-aware sentiment classifier — because real Indian B2B conversations don't happen in textbook English.

TypeScript · MongoDB · BullMQ · Thompson sampling
Full-stack · Next.js storefront

SR Web Store

A jewellery retailer's storefront end to end: SSR product pages, live gold-rate ticker, wishlist, plans, cart → checkout → orders — public/protected routes split via HOC + dual API clients, per-route SEO with structured data.

/collections/rates/wishlist/plans/checkout/orders
Next.js 15 · TypeScript · Redux Saga · Tailwind · SSR + SEO
Full-stack · Web + Mobile

Ashmero JMS

Jewellery management for retailers: 46+ features across 9 modules — consultations, appointments, plans, rates, artisan (karigar) management with gold & wastage tracking. React admin dashboard plus two React Native apps (customer + artisan).

booting modules…0/46 features
React · React Native · Node.js · MongoDB · BullMQ
03 · capabilities

Ask the machine.

prem@runtime: ~/skills
prem@runtime:~$ ./prem --capabilities
agents/ multi-agent orchestration · human-in-the-loop design · Claude CLI & API · prompt-cache + batch economics · interpretable feedback loops (Thompson sampling, Beta tracking)
backend/ Node.js · TypeScript · event-driven systems · BullMQ/Redis · MongoDB · SQLite WAL · queue semantics that survive restarts
frontend/ React · React Native · Next.js · Vite · canvas/Konva · Zustand · Tailwind
infra/ Docker · Railway · Cloudflare R2 · self-hosted NAS automation · Playwright/ffmpeg media pipelines
judgement/ knows when an agent should stop and ask a human
prem@runtime:~$
04 · how i work

Boring on purpose, where it counts.

P-01

A blocked send beats a broken one

My job-hunt agent once drafted a confidently wrong visa answer. It never shipped — because nothing irreversible happens without a human. That rule is architecture, not policy.

P-02

Filter before you infer

Most rejected work should cost zero model calls. Deterministic hard filters, dedupe hashes and batch prompts come before any token is spent.

P-03

Interpretable beats clever at low N

With dozens of outcomes, not millions, a Beta-per-bucket model stays honest where a dense one overfits. I can read exactly what my systems have learned.

P-04

Traceable or it didn't happen

Request-scoped logs, state-preserving releases, WAL checkpoints before every upgrade. A debuggable system is the difference between an agent and a black box.

05 · checkpoint: human

Your move. The agent is waiting.

Building agents that need to work unsupervised at 3 a.m.? Let's talk shop about reliability, feedback loops, and where the human belongs.