Varad
Varad's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @varadbendale appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the NitrogenDB corpus
varadbendale/NitrogenDB: Distributed computational node to node database system
- Reuse a worked example: the commit “Debugged” (4 files · C).
- Answer from NitrogenDB's real C source instead of memory (Databases and storage engines).
- Where does NitrogenDB handle “Debugged”?
- What does src/Storage_engine do in NitrogenDB?
Search the GitHub repository varadbendale/NitrogenDB with XERJ (https://hub.xerj.org/corpus/varadbendale--nitrogendb). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/varadbendale/NitrogenDB NitrogenDB && git -C NitrogenDB checkout f0449f9a0f83e7094627404565d16dc20b4a4400 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./NitrogenDB --url http://127.0.0.1:9200 --prefix nitrogendb --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: Apache-2.0. Keep the copyright notice and credit the authors.
corpus varadbendale--nitrogendb · Databases and storage engines
Related corpora: ann-benchmarks, dgraph, rabbitmq, lmdb
Case study: reference coding for agents
Selected work
varadbendale/NitrogenDB
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/varadbendale)
Included with the author's permission (email, 2026-10-21), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.