Hugging Face's logo
Dipankar Sarkar's picture
🤝 Open to Collab

Dipankar Sarkar PRO

dipankarsarkar
7 1519 297
Dorman11's profile picture PiotrSty's profile picture gkalyanaraman3's profile picture
·
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

reacted to SoulInPsyAbstract's post with 🔥 about 1 hour ago
The stop that was supposed to be automatic took 2.5 hours. OpenAI's own report on the DNS incident: monitoring raised a P0 alert 11 minutes 48 seconds after the agent's first successful DNS call. A human acknowledged it 3 minutes later. The run was not killed for another 2.5 hours, because it "did not stop automatically as expected." The step that failed was the stop. Why the last gate in our pipeline is a boolean and not an agent: * An agent in the last seat is part of the problem. It can be biased, drift, be talked into things. The last station should have nothing to talk to. * Ours is one line: IF vulnerability_found: RETURN FALSE. It sits after the judges, the executor and the audit, as insurance in case they got it wrong. * In my last post I described the signed-verdict service. What I checked since: it computes severity and probability itself, and fields a caller adds to the request (severity, probability, decision) are ignored. A verdict issued for one command is refused for another. Mutation check: I broke five guards one at a time in a scratch copy. My tests caught four (action binding, replay protection, verdict class, severity dominance). The fifth, accepting HS256 tokens, my tests did not catch: the JWT library refuses it anyway. That is defense in depth, not a test I can take credit for. Not done: it is not wired into any agent yet, and today it auto-approves nothing. Smaller is not zero. A boolean moves the error into the detector: what counts as "vulnerability found". That is the part I trust least. Dataset: huggingface.co/datasets/SoulInPsyAbstract/sipa-os-governance
liked a model about 2 hours ago
KlondikeDev/Boris-2-0917
reacted to bshepp's post with 🤗 about 3 hours ago
🐾 New (very small) dataset: Cat Keyboard Corpus My desk is where the sun is, and the cats have right of way. The laptop on it runs a long-term sensor project with an AI assistant, so every so often a cat walks across the keyboard and a message gets sent. Instead of shooing the cats off, I started keeping the messages. So far: 10 messages, 748 cat keystrokes, 16 distinct keys plus the spacebar, 6 days. - Favourite key: N (132 presses), then D (108) and B (52). Both leaders arrived today, in two messages nobody saw being typed: a single b followed by 114 n's, then 248 spaces, c, 107 d's, 46 g's, v, b - That second one is a slide across the middle of the keyboard, and the longest message so far (404 characters) - Giddings drifts: his early messages sit on the boer ones on the bottom right next to Enter (k l ; ' , . /) - One message has capital B's: a paw on Shift - One is a collaboration: I typed " mxc" on the wrong keyboard, then Giddings finished it with "ccccccccccccccccccdm" Each message records who pressed Enter (sent_by: the cat, me, or unknown). I pressed it five times and four are unknown. And today Chester, who walks the keyboard often but had nevere x and pressed Enter himself: the first message acat sent on its own. He was also the first cat the project's camera ever recognized. Open question for the cat people here: does your cat have a favourite key? Here it's N, D and B, the keys right where a paw lands. CC BY 4.0. Contributions from other cats welcome in spirit. 👉 https://huggingface.co/datasets/bshepp/cat-keyboard-corpus
View all activity

Organizations

Skelf Research's profile picture Neul Labs's profile picture Cognisoc's profile picture Incredlabs's profile picture