Contribute to Ohara

Start with a proposal. You do not need to know the registry schema or have a finished proof to describe a useful specification. A GitHub account is needed to submit an issue or pull request.

Propose a specification

Describe permitted behavior, boundary cases, and assumptions.

Propose a theorem or proof

Provide the exact statement, pinned environment, and check evidence.

Propose a verified component

Connect the implementation version to its formal property.

Register an existing project

Help people discover and contribute to upstream work.

Report an incorrect or stale claim

Identify the record and the scope or evidence that needs correction.

Prefer a pull request? Read the record and review guide.

What happens next

1. Describe the behavior, exact source revision, assumptions, license, and available evidence in the issue form.
2. A contributor or maintainer prepares a structured record in a pull request. Metadata checks reject malformed records.
3. A maintainer reviews the scope and evidence, and records a digest-bound publication decision. Semantic review is a separate, identified judgment.
4. An approved merge builds one snapshot for the site and MCP. Failed builds preserve the prior deployment.

Submit only public material you are entitled to share. Even a generalized specification can reveal confidential requirements. Keep large developments upstream, and follow their contributor rules when changing proofs or implementations.

Corrections and withdrawal

Report the stable record ID, revision, and the incorrect assumption or claim. Maintainers can mark the newest version stale or withdrawn so it leaves default discovery while its history stays inspectable. Previously downloaded copies cannot be remotely erased.