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.
| Layer | Where it runs | Artifact |
|---|---|---|
| Rust | The substrate: sensorimotor, memory, tooling, kernel | operant, 7 crates with a 7,168-test gate; holon, the governed kernel; deckmill, 46 slide types measurement record |
| TypeScript / SvelteKit | This site, prerendered and deployed to Cloudflare Pages | This repository, and the build you are reading |
| Python | The kernel that learns and evolves, and the telemetry compiler | The telemetry compiler that produced the reconciled execution count, including the hardcoded default value that was removed measurement record |
| MCP | Tool surfaces served to agents across the fleet | switchpost 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.
- holon The agentic-OS kernel and the portfolio's flagship: persistent AI employees organised into departments under a ratified charter, with a gate that proves the kernel green end to end. public
- operant The Rust agent runtime under the flagship kernel: typed tools, memory, scheduling, and a plugin surface in one consolidated workspace, with the portfolio's strongest executed gate. public
- deployed web Three production surfaces plus this site, deployed and serving: the portfolio's proof that the full-stack claim ends in a live URL, not a repository. public
- switchpost Social posting infrastructure that runs on your own hardware: one Rust binary, 26 platforms, and three interfaces into one engine, with an MCP surface of 389 countable tools. public
- ecosystem backends Three private TypeScript backends: a versioned core package with semver and consumer checks, a better-auth integration, and a Supabase CMS that already speaks MCP. private
- scorestrata A deterministic music compiler: a plain-language brief in, a mastered WAV out, byte-identical on replay from the same contract and seed. public
- deckmill Browserless slide factory: a 46-entry registry rendered by an embedded engine, zero Chromium anywhere in the pipeline. public
- sourcehound Web search and browser navigation for agents, with TOON-compressed payloads. private
- memory-wire The memory-bank CLI the operation writes durable cross-session lessons to: one bank per function, wired into the harnesses that need to remember. public
- organism The private operation substrate: a governed agentic OS of 25 system pools that runs the whole single-operator business. The subject of the first essay. private
- project-genome Repository governance as a skill: owned document roles, mutability classes, and a stdlib CLI, self-checking with 35 of 35 cases. public
- tdg-rust A cognitive memory engine in pure Rust: each memory a (Content, Embedding, Telos) node, traversed as a graph and served over MCP. Legacy by operator ruling, green at its pinned gate. public
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.