Skip to content
View prakash601's full-sized avatar
👨‍💻
Innovating through lines of logic
👨‍💻
Innovating through lines of logic

Block or report prakash601

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
prakash601/README.md

Prakash Sankhla

Backend & AI-systems engineer · Ahmedabad, India

Website Followers


I build systems where software does real, verifiable work — and I care most about the unglamorous half: hybrid retrieval that actually ranks, isolated execution, and state that survives a restart.

What I'm building

🔨 Forge — an AI software engineering platform

Not a coding assistant — a platform that owns the loop from task to verified change: understand the codebase → plan → implement in isolation → validate → debug → review → remember the outcome as project memory.

A modular monolith plus an isolated execution worker: the control plane (API + orchestrator + memory) is deliberately separated from the execution plane (worker + sandbox), so untrusted generated code never runs on the API host. FastAPI · Next.js · PostgreSQL + pgvector

🔍 Problem Finder — hybrid search over coding problems

Live demo →

A hybrid search engine that merges three retrieval strategies — semantic (all-MiniLM-L6-v2, 384-d), full-text, and trigram fuzzy — using Reciprocal Rank Fusion, so a half-remembered problem title still surfaces the right result. Includes Norvig spell-correction for "did you mean".

PostgreSQL + pgvector (FTS · trigram · HNSW indexes) · FastAPI · React + Vite — architecture, data-pipeline, API and deployment docs in-repo, with a pytest suite.


How I work

  • Retrieval is a ranking problem, not a lookup problem. Precision comes from fusing signals, not from picking one clever one.
  • Verification over vibes. A change isn't done when tests go green — it's done when I can explain why it's correct.
  • Design before code. Architecture and data-flow docs get written first; the diff follows.
  • Isolation as a default. Untrusted code and untrusted input get their own plane.

Toolbox

Python TypeScript C++ FastAPI Next.js React PostgreSQL pgvector Docker


Open to backend / AI-systems roles — prakashsankhla0601@gmail.com

Pinned Loading

  1. mint-narcissus mint-narcissus Public

    Forked from nhcarrigan-spring-2026-cohort/mint-narcissus

    Repository for Team Mint Narcissus - Spring 2026 Cohort

    JavaScript

  2. problem-finder problem-finder Public

    Hybrid search over 16,335+ coding problems: semantic (all-MiniLM-L6-v2) + PostgreSQL full-text + trigram fuzzy, fused with Reciprocal Rank Fusion. Live: https://azproject.vercel.app

    Python 1