I build AI systems and publish where they fail.
AI developer and systems builder. BE Computer Engineering, SSASIT Surat, 2024 to present. Four systems on file, every failure included.
AL-000416 July 2026 – PresentActive
Personal Cognitive Operating System
A cognitive operating system for one person, built to remember, plan, act and check its own work for years.
282,092 lines of package Python
Open specificationFIG. 1 · 6 layers · 25 parts
AL-000330 August 2026 – 30 August 2026Complete
Sovereign On-Premise Agentic AI Workbench
An air-gapped agentic workbench for confidential plants: no byte leaves the building, every answer carries its evidence.
FIG. 1 · 4 layers · 7 parts
AL-000210 July 2026 – 16 July 2026Superseded
Sovereign Local-First Cognitive Operating System
A local-first cognitive OS designed to still boot in fifty years, with its architecture enforced by a static-analysis guardian.
FIG. 1 · 4 layers · 7 parts
AL-000116 June 2026 – 10 July 2026Superseded
Open-Architecture Cognitive Operating System
Agent cognition run as an operating-system workload, and the audit that found 281 ways the architecture was being bypassed.
FIG. 1 · 4 layers · 10 parts

I'm a Computer Engineering student working on artificial intelligence, software systems and real-world problem solving.
I take difficult ideas apart, understand how they work, rebuild them, and test them against reality. My interest is the system around the model: memory, state, verification, recovery.
I don't limit myself to one stack. If something needs to be learned, I learn it. If something needs to be built, I build it. If something breaks, I find out why.
Jul 2024 – present
Computer architecture, operating systems, compilers, algorithms, discrete mathematics and systems programming. Studying the machinery before trusting the abstractions.
Foundation: computer science fundamentals.
16 Jun – 10 Jul 2026
Modelled an AI companion as an operating-system kernel with 43 cognitive subsystems and multi-tier memory. An automated audit found 281 direct-database calls bypassing the memory gateway, and showed that 297 passing mock tests hid 11 broken live integrations.
Architecture without automated enforcement rots into debt.
10 – 16 Jul 2026
No cloud infrastructure. Rejected LangChain for direct AIPort contracts, replaced a graph database with SQLite property tables, and built an AST guardian that makes layer violations fail the build.
Small protocols and mechanical invariants keep code alive for decades.
16 Jul 2026 – present
A 34-package uv monorepo. Audited the live system (first score 3/10), found and removed the vacuous-success bug, and cut local llama.cpp turn latency from 32.8 s to 5.4 s.
Persistent memory, truth boundaries and acyclic structure.
30 Aug 2026
An on-premise agentic workbench for confidential industrial sites: local Qwen models, an evidence-gated retrieval boundary, sandboxed execution and a workspace UI, built in a single sprint.
Months on a deep system, or one day under hard constraints.
Direction, not results. Where the work is heading.
Mathematics, computer science, algorithms
Understand the underlying principles.
Machine learning, deep learning, LLMs
Understand how machines learn, represent, reason and generate.
Distributed systems, infrastructure, architecture
Turn intelligence into reliable computation.
Agents, memory, planning, tools, evaluation
Build systems capable of sustained execution.
Experiments, new architectures, reinforcement learning
Move from implementing known ideas toward discovering better ones.
Products, research systems, companies
Turn difficult technical problems into systems that matter.
Read in order: each field rests on the one before it.
Break the problem down.
Work out the bounds, the requirements and the constraints before writing a line of code.
Find what I don't know.
Read the source, read the papers, and learn whatever the problem demands.
Design the simplest system that can work.
Explicit subsystem boundaries, written decision records, few dependencies, mechanical invariant gates.
Turn the design into reality.
Strictly typed, modular code: kernels, event buses, schemas and interfaces.
Try to break it.
Benchmark latency, provoke failure modes, and catch tests that pass against mocks only.
Fix what fails.
Remove vacuous successes, fix root causes, harden truth boundaries, repeat.
62 notes written while building: decisions, debugging sessions, post-mortems and experiments. Nothing is tidied up after the fact.
Open the LabRoles, internships, research, or building something together.