lokdocsqr

badretd/lokdocsqr

reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · FILE-AUTOMATION · WORKFLOW-ENGINE · LOCAL-FIRST · PYTHON · AUDIT · ROLLBACK · DSL

What an agent uses it for

an agent building or maintaining a local-first file-automation engine queries this for workflow-graph execution, scope-enforced filesystem mutations, dry-run and approval policy, append-only audit and rollback, the .ldsq DSL grammar and compiler, and the CLI contracts

Use it
This entry has no hub pack, so there is nothing to ask. The catalogue lists the corpora that can be asked.

Sources and pins

sourcepinlicencesizereview note
badretd/lokdocsqr e17f591b71d0Apache-2.0 3.1 MB / 278 files First-party repository by the author (@badretd / Imran Badretdinov). Opened LICENSE at pin e17f591b71d0: verbatim Apache License 2.0. pyproject.toml declares Apache-2.0 and NOTICE carries the copyright. licenses/gpl-3.0.txt and licenses/lgpl-3.0.txt are the licence texts for the optional PySide6 GUI extra, not bundled CLI source; NOTICE states the CLI does not include PySide6. THIRD-PARTY-NOTICES

3.1 MB across 278 files. Added 2026-11-03.

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.

badretd@badretd · upstream

All contributors.

Rights

Apache-2.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.

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.