Reda Araar
Reda Araar'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 @Pastoray 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 Flume corpus
Pastoray/Flume: An embedded LSM-tree key-value store in Go, built from scratch on the standard library. Features leveled compaction, range scans…
- Look up how Flume implements compaction, database, golang, with answers cited to file and line.
- Reuse a worked example: the commit “add distributed sharding, k8s manifests, raft replication/failo…” (32 files · Go, shell).
- Answer from Flume's real Go source instead of memory (Databases and storage engines).
- How does Flume implement compaction?
- What does raft do in Flume?
Search the GitHub repository Pastoray/Flume with XERJ (https://hub.xerj.org/corpus/pastoray--flume). 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/Pastoray/Flume Flume && git -C Flume checkout e4c04732a82d42948272a51901d97f8e5673758e 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./Flume --url http://127.0.0.1:9200 --prefix flume --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: MIT. Keep the copyright notice and credit the authors.
corpus pastoray--flume · Databases and storage engines
Related corpora: badger, valkey-src, ZoneTree/ZoneTree, Mikedan37/BlazeDB
Case study: reference coding for agents
Selected work
Pastoray/Flume
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/Pastoray)
Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.