Authors and community
People behind ABRL and BanditRLlib
Project authorship and community contribution are different records. The six paper authors are listed in paper-author order; future community contributors appear separately with their accepted work and preferred credit.
Community Contributors
A community contributor is added after a real teaching, formalization, review, or library contribution is accepted. Git commit activity is not automatically treated as paper authorship.
How contribution credit works
Code and proof credit
Lean declarations, proof repairs, tests, and module-level refactors are credited through Git history and the merged pull request.
Mathematical provenance
Book, paper, and original-result sources stay attached to a lemma packet. Citing an author does not make that author an ABRL contributor or endorser.
Teaching and review credit
Substantive explanations, counterexamples, assumption audits, dependency maps, and formal review are valid contributions even when they do not add a theorem.
flowchart LR
Authors["Project authors<br/>paper authorship"] --> Project["ABRL research project"]
Community["Community contributors<br/>specific reviewed contributions"] --> Proposal["Issue or contribution packet"]
Proposal --> Review["ABRL review and full gate"]
Review -->|accepted| Library["BanditRLlib main"]
Library --> Registry["Contribution credit<br/>scope recorded"]
Project --> Library
Registry -. "does not imply paper authorship" .-> Authors
Join the contributor list
Begin with one well-scoped result or documentation improvement. Your preferred name and credit travel with the proposal, review, and eventual integrated declaration.