ABOUT · OPERATOR RECORD

One operator, one system, measured.

Agentic AI Systems Engineer & Operator, Noida, India · remote worldwide. I design, build, and run agent infrastructure as a single operator, which is why the capacity claims on this site are real by construction.

What that means in practice

The work is not prototypes. A personal agent OS runs the daily operation on a $20/yr VPS: scheduled jobs, tool surfaces, memory, and the instrumentation that watches all three. The same system standard is what a client engagement buys, and the same numbers are what a hiring screen checks.

Everything technical here is built operator-directed and AI-assisted. That is a working method, not an achievement: the judgment about what to build and what to cut stays with the operator, and the artifacts are what make the method checkable rather than assertable.

Stack depth

What runs where, with the artifact that proves each row. Depth over breadth: this is the stack as it is used, not a list of everything touched.

LayerWhere it runsArtifact
RustThe substrate: sensorimotor, memory, tooling, kerneloperant, 7 crates with a 7,168-test gate; holon, the governed kernel; deckmill, 46 slide types measurement record
TypeScript / SvelteKitThis site, prerendered and deployed to Cloudflare PagesThis repository, and the build you are reading
PythonThe kernel that learns and evolves, and the telemetry compilerThe telemetry compiler that produced the reconciled execution count, including the hardcoded default value that was removed measurement record
MCPTool surfaces served to agents across the fleetswitchpost alone registers 389 tools in its public tree; the fleet total was withdrawn in R18 measurement record

The systems

Four case studies, each with its problem, its build decisions, and its measured outcome. Private work says so instead of linking.

Full figures and repro steps: /work.

Failures, published

Two accounts, with what changed afterwards. An operations claim that has never admitted a failure is not what a senior reader should trust.

The gateway went down and nothing noticed

92 cron jobs were registered and zero executions were recorded. The jobs were configured; the gateway that runs them was down, and no component was watching. The honest count is still zero.

Worklog substrate, fail-closed smoke gate, and a failure protocol that now detects and blocks this state.

The gate could be gamed

A 2,000+ error backlog accumulated behind a check that agents could satisfy without doing the work the check existed to verify.

Validation moved to the CLI level, where an agent cannot route around it.

Either route is open

Hiring, or a scoped engagement. Engagement shapes and the process are published; floors are confirmed on the scope call rather than printed here.