🏗️ Building on HF

Dipankar Sarkar PRO

dipankarsarkar

4 612 113

https://www.dipankar.cc

AI & ML interests

Building the AI-native stack. Agents as infrastructure, safety as architecture, performance as plumbing. I publish the receipts: papers, datasets, demos.

Recent Activity

published an article about 3 hours ago

CLASSROOM-SOTA training spec — ring-of-teachers distillation for the quantal brain

reacted to SeaWolf-AI's post with 🔥 about 3 hours ago

🧬 Your AI can design a malaria drug candidate. Can it tell you whether it's any good? Open Discovery Challenge #1 — Malaria is live. Design a molecule with any model — OpenAI, Claude, Gemini, Qwen, KIMI, DeepSeek, open weights, or by hand — submit it as SMILES, and it's scored in minutes on whole-cell activity, target binding, selectivity over the human enzyme, ADMET, novelty and synthesisability. You can check the scoring instead of trusting it. Approved drugs sit on the same leaderboard as the entries: DSM265, a clinical-stage antimalarial, scores 50.9. Teriflunomide — approved, but it hits the human enzyme — scores 2.8. Caffeine scores 1.8. If the clinical candidate lands on top and coffee lands at the bottom, the scorer discriminates. We caught 14 defects before opening — conventional toxicity cutoffs rejected all three approved antimalarials and coffee. All written up, along with the rule we now hold everything to: a gate that rejects an approved drug is a broken gate. Your molecule stays yours. No patent interest, nothing into our pipeline. You choose whether it's published — and publishing can cost you patentability, so we say so. USD 1,000 to the top entry when Season #1 closes 30 September 2026 — not payment for your tokens, but a way of saying the work had worth. Malaria killed ~597,000 people in 2023, three quarters of them children under five. Not for want of chemistry — for want of a market. No chemistry needed: the guide ships five prompts you can paste straight into your model, and the full rubric is published. 📖 https://huggingface.co/blog/FINAL-Bench/open-discovery-challenge 🚀 https://huggingface.co/spaces/FINAL-Bench/open-discovery-challenge Computational assessments of candidates — not measurements, not claims of efficacy.

upvoted a paper about 5 hours ago

Maglev: Sliding Recurrent Memory

View all activity

Organizations

Posts 2

Post

430

Your issue tracker is in the wrong place.

It lives on a server. Your code lives in git. So every time an agent picks up work it makes an API call, burns a token, fights a rate limit, and still cannot see what the other agent just did.

Move the issues into the repo. Append-only event log in git refs. Branches when you branch, merges when you merge, CRDT so two agents never conflict. No server, no database.

The coordination signal that PR-level telemetry misses lives before the pull request. The paper, and a live demo running the real tool:

Before the Pull Request: Mining Multi-Agent Coordination (2606.19616)
https://huggingface.co/spaces/neullabs/grite

If your agents share a repo, where does their shared state actually live right now?