Dirk Wahrheit
Dirk Wahrheit'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 @dirkwa 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 tracks corpus
SignalK/tracks: Plugin for tracks accumulation and the track API
- Reuse a worked example: the commit “list tracks from store summaries” (9 files · TypeScript).
- Answer from tracks's real TypeScript source instead of memory (API design and specification).
- Where does tracks handle “list tracks from store summaries”?
- What does src do in tracks?
Search the GitHub repository SignalK/tracks with XERJ (https://hub.xerj.org/corpus/signalk--tracks). 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/SignalK/tracks tracks && git -C tracks checkout 91233e736924b65098f10ff76748a022c53f91dd 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./tracks --url http://127.0.0.1:9200 --prefix tracks --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 signalk--tracks · API design and specification
Related corpora: json-schema-spec, swift-book, box-openapi, postman-collection
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
SignalK/tracks
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/dirkwa)
Included with the author's permission (email, 2026-10-21), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.