How it works
Publish from GitHub
Connect a public repository you can write to, then publish through the website or openvs publish. Include a paper (PDF, Markdown, or LaTeX) or a root claims.yaml, alongside its code and data.
Each repository has a shareable repository publication page. Future pushes to the connected branch publish automatically. Each version is archived at its exact Git commit.
Claim checks
OpenVS extracts claims, reviews them against the submitted evidence, and assigns a verification status.
- Verified: the submitted evidence and reasoning passed the completed checks.
- Unverified: the checks could not establish support, or evidence or tools were unavailable.
- Unsupported: a completed check found a substantive problem with the evidence or reasoning. This does not establish that the claim is false.
Search
Search research questions and get relevant findings and methods. Open a search result to see the relevant claim highlighted alongside the repository’s other claims, as well as its verification status. Related claims indicate similarity, not agreement.
Privacy and unpublishing
Publishing requires a public GitHub repository. If you make it private, OpenVS stops importing changes. Previously published versions remain public until you choose Unpublish on OpenVS. Unpublishing hides your repository, claims, and evidence while retaining a private archive. To republish, make your GitHub repository public and publish again.
Archives
Archives contain the repository’s committed files and any external evidence OpenVS downloaded. Unpublishing cannot withdraw copies already downloaded or independently published elsewhere.