Policies

Scope

OpenVS publishes research from GitHub repositories containing a PDF, Markdown paper, or claims.yaml. GitHub authorization confirms repository access, not the author’s identity or expertise.

Checks, not peer review

CI reviews each claim against its submitted evidence and reasoning. Code reruns are currently disabled on the hosted service; a required rerun that cannot complete leaves the claim Unverified. Automated checks cannot establish whether an experiment actually happened.

What is public

• Publishing requires a public GitHub repository. Published claims whose evidence or reasoning fails a completed check are marked Unsupported. Incomplete or inconclusive checks are Unverified.
• Every status comes from that claim’s own checks. Similar claims do not alter it.

Privacy and unpublishing

Making your GitHub repository private stops new imports but does not hide previously published versions. Choose Unpublish in OpenVS to hide your repository, claims, and evidence while retaining a private archive. To republish, make the GitHub repository public and publish again. Files already downloaded or independently published copies cannot be recalled.

Version history

Published archives are read-only. Each claim is identified by its commit and name. Push a new commit to revise it; earlier published versions retain their own checks.

Removal

Permanent erasure is separate from unpublishing and is used where the law requires it: infringing material, personal data, unlawful content. Removal stops this server serving it and erases the claim text, but keeps a public record of the id, the reason, and the checks, so citations still resolve. Disagreement is never grounds for removal.

Licensing

Put a LICENSE file in your repo. OpenVS takes only the non-exclusive right to distribute what you publish and its metadata.