YASH DOKE.
B.E. Computer Engineering · PESMCOE, SPPU · Class of 2027

YashDoke.

I build the layer between a language model and everything it needs to know — retrieval, memory, and context budgets. The gap between research and production is where I work.

Yash Doke
Pune, IN 2026
About

I'm a final-year Computer Engineering student in Pune, and most of what I've built comes from the same observation: language models are rarely limited by the model. They're limited by what reaches the context window, and by what it costs to put it there.

So I work on the plumbing. A retrieval engine that reads a repository's structure instead of grepping it. A memory hierarchy borrowed from OS paging, so a fifty-turn conversation doesn't quietly forget its own constraints. An admission gate that decides which of your personal context a model is allowed to see. None of it is glamorous, and all of it is the difference between a demo and something you'd actually run.

I try to finish things. Every project below is benchmarked against real baselines, shipped as an installable package or a running system, and written up — because an idea that stays in a folder never had to survive contact with anything.

Better context is invisible when it works and catastrophic when it doesn't.

Work

Systems I've built end‑to‑end

Each of these was taken past the prototype stage — benchmarked against published baselines, packaged, and released. Metrics are from my own evaluation harnesses; the code and methodology are public.

SkeletonGraph

Coding agents waste most of their budget before they solve anything — grepping around a repository, reading whole files to find one function. SkeletonGraph replaces that search with structure: a tree-sitter symbol and call graph across ten languages, ranked by PageRank centrality, fused with BM25 and code embeddings through reciprocal rank fusion. No LLM calls in the index, so it rebuilds instantly after every edit.

Evaluated on SWE-bench Verified with Docker-verified test runs against eight competing pipelines, including aider's repo-map and two knowledge-graph tools. It matched a frontier agent's solve rate while cutting the expensive tail — which turned out to be the real finding: retrieval barely moves average cost, but it stops the worst 5% of tasks from running away.

−42%p95 task cost
86%first-search hit rate
0.91retrieval recall
fewer tokens than repo-map
tree-sitterPageRankBM25 + RRF MCPSWE-benchPython
HierMem

Long conversations decay in a specific way: the model doesn't forget everything evenly, it forgets the constraints you set at the start. HierMem borrows virtual-memory paging to fix that — a four-level hierarchy from a compact topic index down to raw turns, a stateless curator that decides what to page in, and a non-evictable zone for constraints that must survive.

Benchmarked over fifty-turn conversations across four domains against RAG, RAG+summary, MemGPT-style memory, and full-history prompting. The result that mattered wasn't the score — it was that placement policy, not retrieval volume, turned out to dominate whether a constraint survived.

93.3%constraint survival
4.7×context compression
8.46judge score (vs 6.90)
1.4k+PyPI downloads
PyTorchChromaDBLiteLLM LLM-as-judgePython
PERCH

Every assistant I use keeps its own private copy of who I am, and none of them talk to each other. PERCH inverts that: your context lives in one place you own — imported from the official exports of the assistants you already pay for — and is summoned by a hotkey inside whatever application you're already working in, answering beside your work and writing back into it.

The hard part was never the panel. It was the admission gate: a declarative, auditable rule layer over six user-owned memory classes that decides what any given model is allowed to see, and routes private classes to a local model instead of the cloud. A single global relevance threshold stops leaks but throws your identity away, so you stop sounding like yourself. Per-class floors keep both.

0leaked items in ablation
6memory classes
4B → APIone memory, two model tiers
OllamaSQLiteWindows UIA local-firstPython
LLM Reasoning Pipeline

Most reasoning benchmarks tell you whether a model got the answer wrong. This one tells you which step went wrong. Ground-truth backtracking and error-propagation analysis locate the failing link in a chain, teacher–student diagnostics classify it, and then a QLoRA fine-tune targets that failure mode specifically rather than retraining on everything.

62.5 → 76.3%reasoning accuracy
−63%step-level failures
3.5×reasoning stability
Qwen2.5-3BQLoRA / PEFTllama.cpp GGUFPyTorch
Research

Preprints

Both write up systems above, with full evaluation methodology and the negative results included.

Preprint · 2026

SkeletonGraph: A Zero-LLM Structural Retrieval Engine for Coding Agents, and Why Its Gains Land in the Cost Tail, Not the Median

10.21203/rs.3.rs-10749266/v1
Preprint · Jun 2026

HierMem: Context Curation Over Context Scaling — Hierarchical Memory with Invariant Constraint Placement for Long-Horizon LLM Conversations

10.21203/rs.3.rs-10055780/v1
Robotics

ABU Robocon 2026 — Team Vulcans

Software & AI Lead, PESMCOE. Competition complete.

R2 autonomous stack

I led software and AI for our Robocon robot: the ROS2 architecture, real-time perception, and path planning where the map is incomplete and the obstacles move. Validated in Isaac Sim and Gazebo before it ever touched hardware, then integrated with the embedded controllers — including closed-loop position-hold on an ESP32 mecanum base, so the robot actively resists being pushed off its mark.

ROS2NVIDIA Isaac SimGazebo ESP32PIDC++ / Python
Background

Education & stack

Degree
B.E. Computer Engineering, PESMCOE — Savitribai Phule Pune University·Class of 2027
Standing
CGPA 9.38 / 10
Coursework
Machine Learning·Design & Analysis of Algorithms·Information Retrieval·Artificial Intelligence·Data Science & Big Data Analytics·Distributed Systems·Theory of Computation·Cyber Security
Languages
Python·C++·TypeScript·SQL·MATLAB
ML
PyTorch·Transformers·QLoRA / PEFT·XGBoost·SigLIP·sentence-transformers
LLM systems
Ollama·llama.cpp / GGUF·LiteLLM·RAG·MCP·tree-sitter·ChromaDB
Robotics
ROS2·NVIDIA Isaac Sim·Gazebo·path planning·reinforcement learning
Backend
FastAPI·Flask·PostgreSQL·MongoDB·Firebase
Infra
Docker·Google Cloud·AWS·AMD Developer Cloud·Git·pytest
Contact

Open to research and engineering roles.

yashdoke215@gmail.com