dipankarsarkar/grite-corpus
Viewer • Updated • 1.4k • 82
Dipankar Sarkar PRO
dipankarsarkar
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
liked a dataset about 2 hours ago
rmems/llm-eval-flakiness-trajectories repliedto their post about 2 hours ago
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:
https://huggingface.co/papers/2606.19616
https://huggingface.co/spaces/neullabs/grite
If your agents share a repo, where does their shared state actually live right now? repliedto kanaria007's post about 2 hours ago
âś… Article highlight: Benchmark Publication Without Governance Inflation (art-60-274, v0.1)
TL;DR:
This article argues that a benchmark result is not a governance maturity claim.
A score may be real, reproducible, and worth publishing—and still say nothing by itself about safety, deployability, assurance, institutional quality, or platform maturity. 274 treats benchmark publication as a discipline of comparability, disclosure, lifecycle limits, and anti-inflation.
Read:
https://huggingface.co/datasets/kanaria007/agi-structural-intelligence-protocols/blob/main/article/60-supplements/art-60-274-benchmark-publication-without-governance-inflation.md
Why it matters:
• prevents measured results from being inflated into safety or maturity claims
• separates historical results from current comparability
• makes scope, freshness, omissions, and unsupported readings visible
• allows honest publication without requiring full platform assurance
• treats narrower wording as trust discipline, not underselling
What’s inside:
• the publication triad: comparability, disclosure, and anti-inflation
• bounded publication outcomes such as PUBLISHABLE, PUBLISHABLE_WITH_LIMITS, NOT_COMPARABLE, and NOT_PUBLISHABLE
• benchmark publication profiles
• comparability disclosure notes
• public non-claims registers
• inflation checklists for result-to-maturity, comparison-to-assurance, historical-to-current, and wording inflation
Key idea:
Do not say:
“this system scored well, therefore it is mature, safe, or ready to deploy.”
Say:
“this result was observed under this benchmark and comparability frame, remains valid within these lifecycle and disclosure limits, and does not support these broader governance claims.”
Better benchmark publication is not a louder score.
It is a result that is harder to overread.Organizations
