Ovrin is an open-source project with a deliberately documented engineering process. The pages here
cover how it is built, what the standards are, and where the project honestly stands today.
Project
| Page | What it covers |
|---|---|
| Contributing | How to propose a change, and what review will ask you. |
| Rules | The numbered engineering rules the codebase is held to. |
| Roadmap | What is built, what is next, and what is deliberately not being built. |
| Release status | Current maturity, and what is still pre-v1. |
What state the project is in
Worth knowing before you evaluate it:
- The library is implemented, and no release is tagged. Everything through the v0.3 feature set
exists; the version numbers do not exist yet. - The API is not stable and will change before v1.0.
- No accuracy figure has been published, and none will be until the evaluation harness can
reproduce it. The evaluation corpus today is entirely synthetic. - Confidence is a ranking signal, not a probability. The weights are provisional until calibration.
- The bus factor is one. The project says so out loud rather than leaving you to discover it.
Disagreement is welcome
Every significant decision in Ovrin is written down as an architecture decision record, with the
alternatives that lost and the costs that were accepted. That format exists so the decisions can be
argued with. Disagreeing with a recorded decision is treated as a contribution, not a nuisance.