← all corpora

twelve-factor

reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · DESIGN

What an agent uses it for

an agent containerising or configuring an app queries this for the factor's exact statement and rationale (G3 borderline: well-known prose: keep only if G7 shows retrieval value)

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/twelve-factor.json
xerj corpus add --from ./twelve-factor.json
xerj corpus index twelve-factor then xerj code twelve-factor "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: "twelve-factor", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
twelve-factor 1385d2c80bacMIT 21.8 MB / 1,070 files LICENSE at pin: MIT (site code + content). | profiler evidence: PROFILER 2026-10-02T00:49:45Z trees-only: files=1070; backlog hint: verify at pin (code MIT reported; content licence separate); api licence: unknown; evidence: LICENSE→MIT

21.8 MB across 1,070 files. Added 2026-10-02.

People behind this corpus

Upstream authors (1)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

heroku@heroku · upstream

All contributors.

Rights

MIT. 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)

5.0/5 relevant. Graded .

Q: Where does a twelve-factor app store its config?
expect:
top-5: twelve-factor/content/en/config.md / twelve-factor/content/en/config.md / twelve-factor/content/en/build-release-run.md / twelve-factor/blog/intuit-thrilled.md / twelve-factor/blog/narrow-conduits.md
grade: pass
Q: Should a twelve-factor app write and rotate its own log files?
expect:
top-5: twelve-factor/content/en/logs.md / twelve-factor/content/en/concurrency.md / twelve-factor/content/en/config.md / twelve-factor/content/en/dev-prod-parity.md / twelve-factor/blog/intuit-thrilled.md
grade: pass
Q: Are sticky sessions acceptable in a twelve-factor app?
expect:
top-5: twelve-factor/content/en/processes.md / twelve-factor/content/it/processes.md / twelve-factor/content/cs/processes.md / twelve-factor/public/onetrust/oneTrust_production/scripttemplates/202401.2.0/otBannerSdk.js / twelve-factor/content/de/processes.md
grade: pass
Q: What should a worker process do on graceful shutdown?
expect:
top-5: twelve-factor/content/en/disposability.md / twelve-factor/content/en/disposability.md / twelve-factor/content/sk/disposability.md / twelve-factor/content/en/concurrency.md / twelve-factor/blog/narrow-conduits.md
grade: pass
Q: It works on my machine but breaks in production: which gaps does the twelve-factor methodology say cause this?
expect:
top-5: twelve-factor/blog/open-source-announcement.md / twelve-factor/blog/blog.md / twelve-factor/content/en/dev-prod-parity.md / twelve-factor/content/en/config.md / twelve-factor/blog/intuit-thrilled.md
grade: pass

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.