Charles Fonseca
Charles Fonseca'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 @barddoo 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 zedis corpus
barddoo/zedis: Opinionated Redis in Zig
- Look up how zedis implements cache, redis, zig, with answers cited to file and line.
- Reuse a worked example: the commit “update max memory setting” (6 files · Zig).
- Answer from zedis's real Zig source instead of memory (Databases and storage engines).
- Where does zedis handle “update max memory setting”?
- How does zedis implement cache?
- What does src/app do in zedis?
Search the GitHub repository barddoo/zedis with XERJ (https://hub.xerj.org/corpus/barddoo--zedis). 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/barddoo/zedis zedis && git -C zedis checkout 3a758b5118f8b2517efb67a047e96eda137955fa 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./zedis --url http://127.0.0.1:9200 --prefix zedis --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 barddoo--zedis · Databases and storage engines
Related corpora: valkey-src, dagger, awolverp/cachebox, Yoruxyv/semantix
Case study: reference coding for agents
Selected work
barddoo/zedis
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/barddoo)
Included with the author's permission (email, 2026-10-23), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.