Shaurya Singh

What I built, how it works, and what the evidence says.

These are systems, not pitch-deck features. A production deployment is different from a passing test; a working prototype is different from a product. Each entry says which one it is.

Confidential B2B software company · 2025–26

Status · dated check Production deployment verified · 28 Oct 2026

Real-time voice and recruiting platform

I worked across the initial implementation, product architecture, and deployment: browser application, Node/TypeScript APIs, a live voice service, background workers, candidate/recruiter workflows, and their operating infrastructure.

  • Integrated browser WebRTC with carrier telephony and streaming voice models; rebuilt reconnect behavior, turn ordering, interruption handling, and call-state reporting.
  • Designed matching and scheduling paths around explicit state changes, evidence-backed scores, idempotent messaging, tenant isolation, consent and opt-out auditing.
  • Shipped a Railway service split: web/API, worker, real-time runtime, Redis with storage, and monitoring; added schema-migration and source/deployment verification gates.

Fig. 01 schematic · drawn from the entry on this page

Real-time voice and recruiting platform, schematic Browser WebRTC and carrier telephony (Twilio) connect to the live voice service and streaming voice models; reconnect behavior, turn ordering, interruption handling, and call-state reporting were rebuilt. Railway service split: web/API, worker, real-time runtime, Redis with storage, and monitoring, with schema-migration and source/deployment verification gates. Railway · service split WebRTC calls audio deploy Browser application WebRTC Carrier telephony Twilio Release gates + schema migration + source / deployment Real-time runtime live voice service + reconnect behavior + turn ordering + interruption handling + call-state reporting web/API Node.js · TypeScript worker background workers Redis with storage monitoring Streaming voice models upstream Real-time voice and recruiting platform, schematic Browser WebRTC and carrier telephony (Twilio) connect to the live voice service and streaming voice models; reconnect behavior, turn ordering, interruption handling, and call-state reporting were rebuilt. Railway service split: web/API, worker, real-time runtime, Redis with storage, and monitoring, with schema-migration and source/deployment verification gates. Railway · service split WebRTC calls audio deploy Browserapplication WebRTC Carriertelephony Twilio Streamingvoice models upstream Real-time runtime live voice service + reconnect behavior + turn ordering + interruption handling + call-state reporting web/API Node.js · TypeScript Redis with storage worker background workers monitoring Release gates + schema migration + source / deployment
external service live media path release gate Data stores and hosting beyond the stack line are not drawn.
Built with
  • TypeScript
  • Node.js
  • React
  • WebRTC
  • Twilio
  • Prisma/PostgreSQL
  • Redis
  • Railway
TypeScript · Node.js · React · WebRTC · Twilio · Prisma/PostgreSQL · Redis · Railway
Evidence
342 merged PRs authored July–October 2026 in a private production repository; successful Railway production deployment on 28 Oct 2026.

Independent systems engineering

Status · tested Core VPS services tested; additional modules staged

Private infrastructure and recovery

A service control plane for independent software agents, built around explicit authority, private network boundaries, durable source, and verifiable recovery rather than trusting a healthy-looking dashboard.

  • Implemented role-scoped MCP and API gateways; prototyped an OAuth 2.1 / PKCE Cloudflare Worker for read-only remote tool access.
  • Developed private-network-only service routing, health probes that distinguish stale, disconnected, and unmeasured states, and container/host source recovery controls.
  • Added Git mirrors, immutable bundles, and off-machine SHA-verified backups to reduce the risk of commits existing only in disposable containers.
Built with
  • Python
  • Docker
  • systemd
  • SQLite
  • private networking
  • Cloudflare Workers
  • OAuth 2.1/PKCE
Python · Docker · systemd · SQLite · private networking · Cloudflare Workers · OAuth 2.1/PKCE
Evidence
Source repositories contain deployed core components, tests, and explicitly marked not-yet-installed modules. Not every planned service is live.

Cloudflare Worker · operational tooling

Status · dated check Public endpoint responding · checked 30 Oct 2026

Public-status and operational verification

A status page that reports what a recent request could actually measure, and refuses to turn a successful HTTP response into a claim that a call or model finished working.

  • Checks four documented dependencies with bounded requests; validates JSON identity and timestamps, rejects redirects and stale/future responses.
  • Caches probe outcomes for 60 seconds, with explicit degraded and unverified states; backs behavior with mocked failure cases and snapshot tests.
Built with
  • JavaScript
  • Cloudflare Workers
  • HTTP
  • cache and failure-state tests
JavaScript · Cloudflare Workers · HTTP · cache and failure-state tests
Evidence
The public status route returned HTTP 200 on 30 Oct 2026; service completion is deliberately not inferred from reachability.

See measured status

Independent Python data platform

Status · tested Implemented and tested; live Railway deployment unconfirmed

Global signals observatory

A data service covering sixteen public feeds, including space weather, earthquakes, weather alerts, orbital data, natural hazards, river and tide readings.

  • Implemented 15-minute ingestion into SQLite with retention, source attribution, and 22 read-only HTTP endpoints.
  • Added a deadman endpoint that reports failure until data arrives, becomes stale, or the ingestion thread stops; bounded large satellite/image downloads and egress.
Built with
  • Python
  • SQLite
  • scheduled ingestion
  • HTTP
  • unit and socket tests
Python · SQLite · scheduled ingestion · HTTP · unit and socket tests
Evidence
Repository contains ingestion modules, serving code, health routes, tests, and Railway packaging; deployment is not asserted.

Interactive graphics prototype

Status · prototype · experiment Engine modules and render evidence committed

Browser 3D world and rendering toolkit

A modular Three.js/WebGL toolkit for scene construction and repeatable rendering comparisons, built for a larger browser-world project.

  • Built reusable geometry and assembly primitives, physically based materials, scene lighting, exposure and time-of-day systems.
  • Created fixed-camera benchmark scenes and Playwright-driven render runs with interior, exterior, character, and lighting screenshots.
Built with
  • JavaScript
  • Three.js
  • WebGL2
  • Playwright
  • PBR materials
JavaScript · Three.js · WebGL2 · Playwright · PBR materials
Evidence
Repository contains source modules and generated benchmark renders; this is not presented as a complete playable game.

Independent machine-learning experiment

Status · prototype · experiment Training measurements recorded · research scale

Language model from random initialization

Built a 10.7-million-parameter decoder model and byte-level BPE tokenizer without starting from pretrained weights; trained on public text with a separately recorded evaluation loop.

  • Implemented tokenization, corpus preparation, training, checkpointing and text generation as separate reproducible modules.
  • Measured validation loss decreasing from 8.45 at initialization to 3.54 at step 400; the experiment tests learning dynamics, not frontier-model quality.
Built with
  • Python
  • PyTorch
  • byte-level BPE
  • Apple Silicon
Python · PyTorch · byte-level BPE · Apple Silicon
Evidence
Training notes record the 400-step validation result, tokenizer and architecture provenance; model capability remains explicitly limited.

External open source

These three fixes were accepted by maintainers outside my own repositories. Open and closed-unmerged PRs are not included as upstream contributions.

Open-source record

Plate A 33 fix pull requests · 24 with tests

Fix pull requests by outcome and target repository size 33 fix pull requests by outcome: 3 merged, 1 revised fix merged, 1 shipped in release, 1 approved, 25 open, 2 closed. 24 include tests. Target repositories range from 93 to 26,476 GitHub stars. 100 1,000 10,000 GitHub stars of the target repository, log scale → merged 3 ir_measuresotter-graderdata-juicer revised fix merged 1 OSWorld shipped in release 1 ai-gateway approved 1 open-instruct open 25 closed 2 Fix pull requests by outcome and target repository size 33 fix pull requests by outcome: 3 merged, 1 revised fix merged, 1 shipped in release, 1 approved, 25 open, 2 closed. 24 include tests. Target repositories range from 93 to 26,476 GitHub stars. 100 1,000 10,000 GitHub stars of the target repository, log scale → merged 3 revised fix merged 1 shipped in release 1 approved 1 open 25 closed 2

Plate B 238 issues · 229 repositories

Issues filed, by state 238 issues filed in 229 repositories between 2026-09-23 and 2026-10-01: 30 closed, completed, 6 closed, not planned, 202 open. 28 were closed by maintainer-merged pull requests. Issues filed, by state 238 issues filed in 229 repositories between 2026-09-23 and 2026-10-01: 30 closed, completed, 6 closed, not planned, 202 open. 28 were closed by maintainer-merged pull requests.
closed, completed
30
closed, not planned
6
open
202
filed
238
closed by maintainer-merged PRs
28
Fig. The public record of fix pull requests and issues by shaurya416, as of 2026-11-02. Source: GitHub, read 2026-11-02; public PRs and issues by shaurya416.

Ledger the 6 pull requests with a maintainer outcome

RepositoryPROutcomeOpenedResolved+/−Tests
datajuicer/data-juicer #1080 merged 2026-09-24 2026-09-28 +135 −18 yes
ucbds-infra/otter-grader #1021 merged 2026-09-24 2026-09-25 +70 −1 yes
terrierteam/ir_measures #84 merged 2026-09-30 2026-09-30 +17 −7 yes
xlang-ai/OSWorld #598 revised fix merged 2026-09-24 2026-10-19 +2 −2 no
ferro-labs/ai-gateway #448 shipped in release 2026-09-26 2026-10-18 +116 −11 yes
allenai/open-instruct #1917 approved 2026-09-24 — +62 −1 yes

The other 27 are counted on Plate A, not named.

This is a selected technical record. Several systems are private by design; details are intentionally limited to architecture, verified behavior, and public evidence. No internal credentials, customer data, or service addresses are published.