Alpharius
Alpharius'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 @abraxis717 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 Elpis_DEV corpus
abraxis717/Elpis_DEV: abraxis717/Elpis_DEV (Python)
- Reuse a worked example: the commit “add original frozen Rust source closure for unreso…” (7 files · Rust).
- Answer from Elpis_DEV's real Rust source instead of memory (API design and specification).
- What does research do in Elpis_DEV?
Search the GitHub repository abraxis717/Elpis_DEV with XERJ (https://hub.xerj.org/corpus/abraxis717--elpis-dev). 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/abraxis717/Elpis_DEV Elpis_DEV && git -C Elpis_DEV checkout 6776cd4c18c83f9bf75b6ddabfa22428cb2ff090 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./Elpis_DEV --url http://127.0.0.1:9200 --prefix elpis-dev --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 abraxis717--elpis-dev · API design and specification
Related corpora: adyen-openapi, siren-hypermedia, swagger-ui, swift-book
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
abraxis717/Elpis_DEV
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/abraxis717)
Included with the author's permission (email, 2026-10-18), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.