Tobi Odeyemi
Tobi Odeyemi'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 @ercross 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 reconD corpus
ercross/reconD: A lightweight container deployment agent that continuously reconciles desired and observed state, inspired by Kubernetes controllers and…
- Look up how reconD implements automation, container, continuous-delivery, with answers cited to file and line.
- Reuse a worked example: the commit “bound forward and rollback deployment attempts” (12 files · Go).
- Answer from reconD's real Go source instead of memory (Operations and SRE).
- Where does reconD handle “bound forward and rollback deployment attempts”?
- How does reconD implement automation?
- What does deployment do in reconD?
Search the GitHub repository ercross/reconD with XERJ (https://hub.xerj.org/corpus/ercross--recond). 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/ercross/reconD reconD && git -C reconD checkout d4fc02ec15c71116cb534762117b1a8dee240196 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./reconD --url http://127.0.0.1:9200 --prefix recond --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 ercross--recond · Operations and SRE
Related corpora: argo-cd, flux2, ol3d/home-ops, kris-hansen/comanda
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
ercross/reconD
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/ercross)
Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.