PROJECT INDEX / 01—03

Systems in
the making.

A selection of work across model explainability, research discovery, and retrieval workflows. Each project has a different scope; the notes below keep those boundaries visible.

3 FEATURED CASE STUDIESOPEN SOURCE / RESEARCH
01 FRAMEWORK / LEXSI AI
signal → source

DLBacktrace

Deep models span many architectures and tasks, which makes relevance tracing difficult to inspect consistently. DLBacktrace is a model-agnostic explainability framework for transformers, language models, and Mixture-of-Experts architectures.

View repository

Architecture & implementation

My resume describes contributions across graph capture, activation collection, relevance propagation, trace storage, and visualization. For LLaMA-family and MoE support, the resume specifically describes PyTorch torch.export/FX graphs and routing-aware relevance propagation. The repository presents this as a model-agnostic framework across transformers, language models, MoE, and other task types.

Design constraint — tracing must cover model execution and relevance flow across different architectures; a single-model explanation path would not meet the framework's stated scope.

Inspect the implementation

Status & limits — the public repository contains the framework implementation. The résumé lists comparisons with SHAP, LIME, and Integrated Gradients, but no benchmark figures are repeated here; public README performance claims are not independently reproduced on this site.

02 AGENT WORKFLOW
QUERY↓SEARCH↓SYNTHESIZE
public sources
↘
source-backed answer

Indic Research Agent

India- and Indic-language research questions can require searching several public sources and carefully synthesizing what they support.

View repository

Architecture & decisions

I implemented this workflow across the Chainlit UI, LangGraph tool loop, typed query-kit search tool, and storage/cache services:

  1. Chainlit receives the question and streams progress and answer tokens.
  2. A LangGraph tool-calling loop invokes a typed public-search tool backed by query-kit.
  3. The model synthesizes from returned sources; PostgreSQL stores chat history and Redis caches normalized search/tool results.

Scope decision — this is a public-provider research assistant. It does not ingest or search a local document corpus. Keeping the search boundary explicit avoids implying retrieval over material the app has not indexed.

Inspect the workflow

Status & limits — the repository describes a local application with configurable provider credentials and local persistence/cache services. No user adoption, answer-quality metric, or production deployment result is claimed here.

04 LOCAL PROTOTYPE
SOURCE
retrieved context
→
ANSWER
attribution
RETRIEVE / CHECK / RETRY

Explainable Agentic RAG

Document-grounded RAG evaluation needs the evidence, workflow, and verification steps to remain inspectable. This is my local prototype for exploring that problem.

View repository

Architecture & decisions

I implemented the local-PDF workflows and shared service/contract path. Local PDFs are loaded, split into chunks with source metadata, indexed in memory, then passed through selectable two-step, agentic, single-graph, or multi-agent workflows. The shared service and canonical contracts keep CLI modes on a common response path; attribution carries source, page, rank, and selection details with the answer.

Design choice — compare multiple retrieval/orchestration paths through one service and response contract, so the evaluation runner can use the same mode adapters as the CLI.

Inspect the artifacts

Status & limits — working local prototype. The baseline freezes corpus/configuration inputs but explicitly records no remote model or RAGAS run. No comparative scores are published. The index is rebuilt in memory, retrieval is dense-only, verification is token-overlap heuristic, and durable human-review resumption remains incomplete.

SUPPORTING TOOL

query-kit

A Python CLI and library that searches public research sources, normalizes results, and removes duplicates. It provides sync and async APIs; the repository documents local installation, not a PyPI release.

Inspect repository

Interested in a project or a technical conversation?

Reach out