am.

Engineer & founder / Kolkata, India

Ayushman
Mukherjee.

i’m ash. i’m building Loreflow

so teams can find what happened, why it happened, and where the answer came from.

co-founder & CTO · kolkata, india

things i’ve built
Ayushman Mukherjee wearing a black turtleneck
you can call me ash.
02Hyperion Deltaundoing an agent’s changes without resetting everythingDeveloper tools

an agent changes a handful of files. undoing that attempt shouldn’t require restoring the entire repository.

Hyperion Delta is my TypeScript SDK for checkpoints, branches, and recovery. it tracks the files that changed and restores that set. the source includes the benchmark setup and its limitations, so you can inspect what was actually measured.

code & benchmarks docs
03ButterFencetesting what a coding agent shouldn’t be allowed to doAgent safety

giving an agent access to your repo means giving it access to things it can break or leak.

i built ButterFence to test those failure cases in Claude Code and generate hooks that enforce boundaries. it includes adversarial scenarios, secret scanning, and reports you can take into a code review.

inspect the code
04RouteForgea good-looking molecule still needs a way to be madeScientific software

i built the chemistry-validation, search, and evaluation core to explore molecules through the reactions that could produce them.

the harder lesson: a valid route still doesn’t tell an expert enough to make a decision. i shifted the work toward inspectable routes, uncertainty, and failure evidence.

Independent project · Closed source

what changed my mind ask me about it
01 / Loreflow

the dashboard looked done.
the data wasn’t there yet.

we had a dashboard, a context map, a timeline. you could click around and it felt like a product. underneath, most of the company data wasn’t actually flowing.

i spent the next stretch connecting GitHub, bringing activity into the memory backend, and keeping company data isolated. seeing real activity come back with its original source attached was a small visual change. it meant a lot more than another finished screen.

the original build update
02 / Loreflow

why i made the AI less free

i don’t want a company answer to be a convincing paragraph with sources added as decoration.

in Loreflow’s answer engine, the model has to return individual claims and the evidence behind each one. if it references evidence that doesn’t exist, we reject the answer. Loreflow then assembles the claims into what the reader sees.

that doesn’t make every answer correct. it gives us something concrete to check before showing it to someone.

the original build update
03 / RouteForge

the benchmark i held back

with RouteForge, i reached a point where the ranking looked promising, but i couldn’t defend it well enough to publish a benchmark claim. so i held it back.

a valid chemical route wasn’t enough on its own, either. technical validation and conversations with people in drug discovery pushed me toward a different question: what evidence would an expert need to decide whether this route is worth pursuing?

that changed the product. routes, uncertainty, disagreement, and failed steps needed to be inspectable. a single attractive score couldn’t do that job.

From my RouteForge build, April–July 2026.

The AI Journal / September 2026

Agentic AutoML Should
Know When to Stop

an agent can keep going. when should it have to stop and ask?

Research preprint / Co-author

A Multi-Agent Orchestration Framework for Explainable Human-in-the-Loop AutoML

Selected · 2026

YC Startup School India

Wins & awards

4 hackathons

ayushman.
ash works too.

self-taught engineer · co-founder

i’m based in kolkata. most of my time goes into Loreflow. the other projects here are things i’ve gone deep on: coding agents, scientific software, and tools for developers.

i spend a lot of time on the parts people notice only when they break. missing context. bad retrieval. an agent overwriting something it shouldn’t.

i like being able to explain why something works. when i can’t, that usually becomes the next thing i work on.

there’s more on GitHub

say hello

building something, have a question, or disagree with something i wrote? email me.