Instruments of resolution
Noisegoes in.Signalcomes out.
A repository. A Postgres backup. A bank export. A lab PDF. Six systems that take input nobody vetted — and refuse to guess about the parts they can't resolve.
01 / the ratchet
carabiner
A security baseline that only tightens.
- Problem
- Repository posture rots silently between audits.
- Hard
- A ratchet that never loosens — not by accident, not by a well-meaning PR.
- Cost
- 60 repos calibrated · 79 tests · 18 drills against live GitHub settings · SARIF · PyPI, GHCR, Marketplace
02 / the vessel
firedrill
A backup is not proven until something restores it.
- Problem
- A
pg_dumpthat exits 0 can still be a truncated file nobody has ever tried to read back — andpsqlrestores a truncated plain dump with exit 0, rows silently missing. - Hard
- Matching the archive's own Postgres major and restoring inside a disposable container with no path to production, ever.
- Cost
- 6 Postgres majors, both directions on the corpus · field-tested against pagila, chinook and northwind — and found a real gap in a published sample database nobody had caught · PyPI, GHCR, GitHub Action
03 / the rotor
recur
Which charges actually recur.
- Problem
- A bank export is a wall of rows. The subscriptions are in there somewhere.
- Hard
- Postgres row-level security, so a query that forgets its tenant filter returns zero rows instead of someone else's money.
- Cost
- FastAPI · SQLAlchemy · argon2id · OAuth 2.1 + PKCE · remote MCP server · pgvector matching, measured and cut · 0 bank credentials stored, ever
04 / the spectrometer
LabLedger
A lab PDF, resolved to codes.
- Problem
- Every lab formats results differently. The numbers stop meaning anything.
- Hard
- Resolving each test to a LOINC code, converting units, and picking the right reference interval — an LLM only for the ambiguous ones.
- Cost
- FastAPI · MongoDB · role-based access, 2FA, audit log · anything uncertain goes to a human
05 / the tumbler
QuizNest
Knowledge either aligns, or it doesn't.
- Problem
- Reading something is not knowing it, and a score out of ten doesn't tell you which part you missed.
- Hard
- Generating questions that actually discriminate, then turning a stream of answers into analytics a learner can act on.
- Cost
- MERN · Gemini-generated questions and graded written answers · Google sign-in · per-topic analytics
06 / the manifold
AI-Recipe-Maker
Five measured inputs, one plan.
- Problem
- "What can I cook with this?" is easy to answer badly and hard to answer with real nutrition behind it.
- Hard
- Dosing the constraints — what's in the fridge, what it costs nutritionally, what a week of it looks like — into one coherent plan.
- Cost
- TypeScript · Claude-powered generation · nutrition analysis · meal plans
07 / the core sample
Wizcommerce
Backend in production, on a multi-tenant platform.
Backend DeveloperGurgaon · Apr 2025 — Sep 2026
- 30+ REST APIs on FastAPI — 30% faster data retrieval
- A multi-tenant backend: each client's data private and isolated, and the system still easy to scale
- Search on Elasticsearch — response time down ~40%
- Long-running work moved onto Celery, so the API stays fast and responsive for users
- PostgreSQL queries and SQLAlchemy code reworked — 25% less database load
- Centralized logging and Sentry alerts, so issues are caught and fixed faster
08 / the feeler gauge
What I reach for
Seven leaves, each ground to one thickness.
- Language
- Python · SQL · Java · JavaScript
- Backend
- FastAPI · REST · JWT · OAuth2
- GenAI
- RAG · OpenAI, Gemini & Claude APIs · prompt engineering · MCP · Claude Code, Cursor, Copilot
- Data
- PostgreSQL · MongoDB · SQLAlchemy
- Search
- Elasticsearch · Redis
- Ship
- Celery · Docker · Git · CI/CD · Sentry
- Judgement
- System design · API design · performance tuning · debugging
B.Tech Computer Science Engineering, Chitkara University, 2022–2026 — CGPA 9.02. Certificates in deep learning, data science and product management.
09 / the rack
More, on GitHub
Six above are one system each, worth their own mechanism. These share a rack instead — real, tested, published, each with its own CI, read at a glance rather than one at a time.
- receipt — verified receipts for what a shell command, an AI agent's tool call or a browser click actually did, in one tamper-evident format
- invariant — declare what must stay true, check it in CI with its own GitHub Action, keep a proof bundle of every run
- playhead — replay an AI coding session like a video timeline, imported straight from its transcript
- satchel — a local-first reading archive that imports Pocket and Omnivore and rescues dead links from the Wayback Machine
- sourced — checks each claim of LLM output against its source; an optional Claude judge must quote its evidence verbatim
- lockstep — catches installed code edited after install, which a version number never shows
- escrow — a self-hosted dead man's switch for cron and CI jobs, alerting when one goes quiet or fails
- drift — checks a device's real traffic, HTTPS included, against its maker's own RFC 8520 MUD file
- witness — a browser extension that holds a site to the claims it publishes about itself
Let's buildsomethingthat holds up.
Fremont, California · Green Card holder, authorized to work in the U.S.
How this page works
One object, never cut. Every boundary is the shape before it turning into the shape after. Pick one to watch it happen again.