Agent infrastructure & MCP. I ran AI coding agents as the primary builder across 72 hackathons and 139 projects — zero confirmed wins — then published the failure taxonomy my agents now read before they build.
→ The essay: 139 projects, zero confirmed wins
Based in Jakarta. Async and remote.
- agent-postmortem-loop — 34 postmortems from 139 projects, distilled into a failure taxonomy and rules my agents load before building. The dataset behind the essay.
- BagOS — MCP server for Solana (Bags.fm): simulate → approve → sign → send → confirm on every write, spending caps, devnet by default. v2.0.0 on npm with provenance. v1 shipped a fake-success bug — the fix and postmortem are public.
- armsmith — ARM/Graviton performance benchmark toolkit. Signed releases on PyPI via trusted publishing.
- aegis — Multi-agent support engine that stops and waits for human approval before any destructive action.
- revoker — Approval hygiene for agent, keeper and relayer wallets: threat rules fire and the revoke lands before the drainer does.
- antigen — Prompt-injection immune system for DataHub metadata: sweeps hidden payloads, defuses them in-graph, proves the cure.
The through-line: agents that act on real systems need brakes — approvals, caps, simulation, revocation, postmortems.
TypeScript · Python · Go · Rust — MCP servers · Solana (Web3.js / Anchor) · FastAPI · Next.js · PostgreSQL · Docker · GitHub Actions
93 events tracked, 72 entered, 139 projects shipped — DoraHacks · Devpost. Zero confirmed wins; the postmortems were the payout.


