Paweł
Paweł'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 @bauerpawel 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 DOCKYARD corpus
bauerpawel/DOCKYARD: Dockyard: a browsable gallery of 600+ Portainer app templates, built from YAML and kept fresh automatically
- Look up how DOCKYARD implements docker, docker-compose, portainer, with answers cited to file and line.
- Reuse a worked example: the commit “Harden deployment and expand the app catalog” (55 files · Python, PHP).
- Answer from DOCKYARD's real Python source instead of memory (Operations and SRE).
- Where does DOCKYARD handle “Harden deployment and expand the app catalog”?
- How does DOCKYARD implement docker?
- What does tests do in DOCKYARD?
Search the GitHub repository bauerpawel/DOCKYARD with XERJ (https://hub.xerj.org/corpus/bauerpawel--dockyard). 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/bauerpawel/DOCKYARD DOCKYARD && git -C DOCKYARD checkout 2df1e10aca3fdcc9ff70d14c37488bab930d51e8 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./DOCKYARD --url http://127.0.0.1:9200 --prefix dockyard --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 bauerpawel--dockyard · Operations and SRE
Related corpora: ann-benchmarks, docker-docs, bifrost0x/webssh, danileau/prettypleaseprint
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
bauerpawel/DOCKYARD
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/bauerpawel)
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.