OSRI contribution standards
On this page
Version: OSRI-0.1.0, adopted on 2026-11-13 for the initial starter-kit publication. See the version record.
People from different fields and with different skill levels are welcome. Contributions include questions, source suggestions, explanations, reviews, writing, data work, code, and simulation. You may use your own agents. Coding experience, academic credentials, and an agent subscription are not prerequisites for participating.
Core rules#
- Keep a person responsible. Name the human directing each project and each substantive submission. People decide the research questions, assess the evidence, and authorize conclusions and publications.
- Make a bounded contribution. Describe the question or change and its scope. Agree substantial work with a maintainer before expanding it. Small corrections and source suggestions can be submitted directly.
- Make evidence traceable. Link sources and identify the relevant passage, dataset version, or result. Mark an unchecked source as a lead. Distinguish evidence, assumptions, hypotheses, and simulated findings. Do not invent citations, observations, approvals, or checks.
- Leave work understandable and reproducible. Explain what changed and how it was checked. For analyses and simulations, record inputs, methods, environment, parameters, relevant randomness, and result locations. Preserve editable sources and follow the open-format guidance. Retain failed checks and material limitations. Match the detail to the task.
- Use agents openly and within scope. Follow repository instructions and the project's selected skills and workflow versions. Equivalent tools or manual work may meet the same input, output, and evidence requirements. Record material assistance, checks actually performed, who or what performed them, and human review still needed. Routine spelling assistance needs no separate report. Do not describe an agent's review as independent human review.
- Share only material you may share. Preserve attribution and reuse terms. Keep credentials, restricted data, and private conversations out of public submissions and unapproved external services. Use approved data locations and shareable manifests. Use the administrator request route for resources you cannot access.
- Have a human authorize acceptance and publication. Submit a pull request or open an issue. A maintainer can help turn the issue into a pull request. The human maintainer who accepts the change records the decision. Agents may execute merge or publication actions when that person has authorized the reviewed change. Repository acceptance and external peer-review status are recorded separately.
- Work respectfully and give credit. Explain disagreements, ask for help, and credit contributions accurately. Agree authorship and contributor roles as work develops and follow the intended publication venue's requirements. Record unresolved concerns rather than hiding them.
What to include with a change#
- The question or change, and its project or issue if applicable.
- Sources or evidence supporting it.
- Checks actually performed, who or what performed them, their results, and any review still needed.
- Material agent assistance and the responsible human, when applicable.
For a typo or link correction, a sentence explaining the fix is enough. A source lead can be useful before its full text has been checked. Maintainers help newcomers prepare the research record appropriate to their contribution.
Review should match the work. Source and prose changes need source and meaning checks. Changes to methods, data, analyses, or models need relevant technical and scientific review. Publications need human review of the supporting evidence, limitations, and credit. Automated checks provide bounded evidence about what they actually examined.
For exploratory work, record what you tried and what you learned. For planned tests, identify the method fixed before the test. Date later changes. Do not describe earlier exploration as a prespecified test.
Follow the research-area scope. The initial Healthcare scope is nonclinical. Raise a proposed scope expansion with the human lead before doing that work. If an activity uses people or restricted records, identify the applicable review and access requirements before that activity.
During the founder-only stage, the founder may accept their own work after a documented self-review. Record that limitation accurately. Seeking another person's domain or methods review remains part of developing stronger research.
Shared administration#
Administrators maintain these standards, coordinate project maintainers, and use meta-research to improve how OSRI works. Standards changes are proposed and recorded. Each project identifies the standards version it follows and documents any additional methods or requirements.
An adopted version must identify its date and an immutable repository commit or release. Existing projects record adoption of a later version or explain a project-specific difference. Projects record the standard version and exact repository commit they use. Later changes are recorded in the decision log.
For questions or help, use Q&A. Share topic ideas in Ideas. Issues and pull requests can track agreed work; link them to the related discussion. The initial administrator is Cole / @ajhcs. You may ask for reconsideration of a decision and record the reason. An independent appeal reviewer has not been appointed. For confidential concerns, contact Cole privately. Agree on a delivery method and controlled storage before sending restricted material.