how-they-sre
reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · SRE · CASE-STUDIES · RELIABILITY · PRACTICES
What an agent uses it for
An agent studying real-world SRE queries this for curated summaries of how many named organizations run reliability engineering.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/how-they-sre.jsonxerj corpus add --from ./how-they-sre.jsonxerj corpus index how-they-sre then xerj code how-they-sre "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "how-they-sre", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| howtheysre | 284703b172d8 | CC0-1.0 | 305.5 KB / 16 files | Read LICENSE via authenticated GitHub API: CC0-1.0 ('Creative Commons Legal Code / CC0 1.0 Universal'), no attribution required; repo live. Caveat: curated summaries + external links, not long-form original text; tiny repo; linked targets not in clone. |
305.5 KB across 16 files. Added 2026-10-13.
Rights
CC0-1.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.