HOW AGENTS ACTUALLY USE TOOLS
From model output tokens to sandboxed execution environments: deterministic JSON schema validation, error recovery loops, and safety rails.
I build software, explore agent architectures, and try to understand what breaks when systems scale.
ENGINEERING / SYSTEMS / ML / AGENTS
help or press /A multi-agent research system that breaks complex questions into smaller tasks, searches for evidence in parallel, evaluates findings, and produces a structured final report.
Used explicit graph-based orchestration so planning, research and evaluation remain observable and independently controllable.
Receive multi-faceted user research inquiry and establish search constraints.
A hybrid retrieval engine combining sparse keyword matching and dense vector search with cross-encoder reranking for low-latency, verifiable factual recall.
Paired sparse lexical search with dense semantic embeddings to prevent hallucinations on exact identifiers while retaining natural language recall.
An event-driven triage assistant that intercepts security telemetry, correlates threat indicators against live intelligence feeds, and orchestrates incident mitigation.
Implemented deterministic rule verification before granting LLM agents permission to invoke quarantine and policy mutations.
Exploratory codebases, active research spikes, and technical curiosity.
How do we constrain autonomous browser tool-calls to prevent runaway DOM state?
Constrained browser automation agent running in sandboxed headless Chromium with token-budgeted DOM snapshots.
Most of the things I learn follow the same pattern: I find something I don't understand, pull at the thread, and eventually try to build something with it.
Right now those threads happen to be agents, security, systems and lower-level software. A few months from now, there will probably be another one.
Evidence-linked technical foundations. Hover any tool to inspect verified project or lab usage.
Autonomous agent workflows, deterministic tool routing, and evaluation pipelines that keep LLM systems observable and reliable in production.
Fast, typography-driven web applications with high visual craft, clean component architectures, and minimal client-side overhead.
Low-latency retrieval engines, asynchronous worker queues, and structured data indexing pipelines built to handle edge cases gracefully.
Investigating runtime internals, memory layouts, network protocols, and automated threat triage pipelines.
From model output tokens to sandboxed execution environments: deterministic JSON schema validation, error recovery loops, and safety rails.
Why mechanical sympathy matters in modern software: cache lines, pointer indirection costs, and struct-of-arrays memory layouts.
When vector search degrades on exact identifiers, alphanumeric codes, and domain queries, and why hybrid BM25 pipelines remain critical.
A role, project, architecture problem, or rabbit hole worth exploring together.