Skip to content
View sdivyanshu90's full-sized avatar

Highlights

  • Pro

Block or report sdivyanshu90

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. Markdown is supported. 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
sdivyanshu90/README.md
Admission ticket to Divanshu Sharma's Museum of Edge Cases

Enter museum  ·  Browse collection  ·  Visit conservation lab  ·  Meet the curator

Visitor orientation

I don’t collect technologies. I collect the assumptions that failed.

Welcome to a collection about the exact moment a clean abstraction meets an uncooperative world.

Every gallery begins with something that worked: a model, a cache, a provider, a distributed job, a generated program. The exhibit begins when reality supplies the input its designer did not imagine. My work is to preserve that failure, understand the boundary it crossed, and build the system that survives it.

Curator: Divanshu Sharma · Applied AI / ML Systems Engineer · Founding Engineer at Uniiq.ai

Visitor map

Floor plan for six galleries around the central Reality Atrium

The map is arranged around the museum’s permanent stress test: Reality. Open any gallery placard below to inspect the artifact.

DIRECT ACCESS
01 EVALUATION  ·  02 DEBUGGING  ·  03 EFFICIENCY  ·  04 ROUTING  ·  05 SCALE  ·  06 SECURITY

The galleries

GALLERY 01   The Hall of False Confidence

CATALOGUE E—01 · Evaluation systems · Mixed deterministic and model-based media

Observed anomaly
A model can produce a plausible answer while the benchmark, dataset, scorer, or provider contract quietly measures the wrong thing.

Conserved invariant
An evaluation should be reproducible, inspectable, crash-safe, and honest about uncertainty.

GALLERY 02   The Checkpoint That Changed Its Mind

CATALOGUE N—02 · Behavioral debugging · Representations, mechanisms, and training data

Observed anomaly
Two checkpoints disagree, the aggregate metric moves, and the reason remains hidden inside millions of parameters.

Conserved invariant
A behavioral regression should be traceable to a representation, intervention, mechanism, or influential training example.

GALLERY 03   The Compression Chamber

CATALOGUE Q—03 · Model efficiency · INT8, FP4, and NF4

Observed anomaly
The model fits the mathematics and misses the machine: too much memory, too much latency, too much cost.

Conserved invariant
Compression should make its numerical loss measurable through calibration, serialization, validation, and benchmarks.

GALLERY 04   The Vanishing Provider

CATALOGUE G—04 · Provider infrastructure · Routing, failure, cost, and recovery

Observed anomaly
The application behaves as though “the model” were one stable endpoint. The network knows otherwise.

Conserved invariant
Requests should retain identity and policy across routing, failover, circuit breaking, rate limits, semantic caching, and observability.

GALLERY 05   The Distributed Labyrinth

CATALOGUE D—05 · Distributed training · FSDP/ZeRO-3 and tensor parallelism

Observed anomaly
One model becomes many shards; ownership, ordering, checkpoints, and recovery stop being local facts.

Conserved invariant
Scaling should preserve mathematical equivalence and deterministic resume across devices and failures.

GALLERY 06   The Containment Wing

CATALOGUE S—06 · Secure execution · Containers, namespaces, seccomp, and cgroups

Observed anomaly
Generated code needs enough authority to be useful and little enough authority to remain harmless.

Conserved invariant
Every process, file, network request, queue, and resource must remain inside an explicit trust boundary.

Special exhibition · Six things abstractions forget

IDENTITY  A cache key decides when two things are “the same.”
TIME      A retry policy decides which promises survive a delay.
ENCODING  A parser decides what information crosses representation.
STATE     A page token and a shutdown hook decide what gets remembered.
SCALE     A distributed algorithm decides which local truths remain global.
TRUST     A sandbox decides which powers cross into an untrusted process.

Different codebases keep producing these same six exhibits. The syntax changes. The boundary does not.

The conservation lab

The public galleries show finished systems. Behind them is the repair archive: released fixes, merged patches, active investigations, and complete implementations closed by automated triage or contribution-process rules. This wall label updates itself from public GitHub evidence whenever the newest open restoration changes.

The most recently updated open pull request authored by Divanshu Sharma

PERMANENT ACQUISITION · OBJECT 001 — A cache parent directory that existed only in theory, restored upstream and released in lm-evaluation-harness v0.4.13.

Each record preserves four facts independently:

INVARIANT → FAILURE → AUTHORED IMPLEMENTATION → UPSTREAM OUTCOME

Curator’s note

I’m Divanshu Sharma. I build AI systems at the layer between model behavior and production reality: evaluation, inference, retrieval, routing, observability, distributed training, security, and the strange failure modes hiding between them.

The museum is playful. The engineering is literal. Every linked artifact is working code, and every conservation record points back to public evidence.

PORTFOLIO  ·  RÉSUMÉ  ·  CONSERVATION RECORDS

STAFF ONLY · open the maintenance door

Museum policy for handling fragile abstractions:

01  Reproduce before explaining.
02  Preserve the caller's intent across every boundary.
03  Make terminal states explicit.
04  Treat error behavior as part of the interface.
05  Keep provenance even when another actor ships the repair.
06  Leave the seam visible so the next failure is easier to find.

If you reached this room, you are exactly the sort of person I like building systems with.

THE MUSEUM NEVER CLOSES · PLEASE EXIT THROUGH PRODUCTION

Pinned Loading

  1. build-your-own-ai-gateway build-your-own-ai-gateway Public

    OpenAI-compatible multi-provider LLM gateway with routing, failover, circuit breaking, rate limits, semantic caching, cost controls, and observability.

    TypeScript 1

  2. build-your-own-distributed-training build-your-own-distributed-training Public

    LLaMA-style distributed training from PyTorch primitives: FSDP/ZeRO-3, tensor parallelism, sharded checkpoints, deterministic resume, tests, and profiling.

    Python 2

  3. EvalForge EvalForge Public

    LLM evaluation harness with dataset validation, provider adapters, deterministic/model-based scorers, reproducible runs, and regression workflows.

    Python 1

  4. FromScratchQuant FromScratchQuant Public

    PyTorch quantization library implementing INT8, FP4 and NF4 from first principles with calibration, serialization, tests, and benchmarks.

    Python 1

  5. build-your-own-code-interpreter build-your-own-code-interpreter Public

    Sandboxed untrusted-code execution using containers, namespaces, seccomp, cgroups, network/filesystem isolation, queues, and resource controls.

    Python 1

  6. EleutherAI/lm-evaluation-harness EleutherAI/lm-evaluation-harness Public

    A framework for few-shot evaluation of language models.

    Python 14.3k 3.7k