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 has shipped, what is still open, and what is deliberately not being built. |
| Release status | What v1.0.0 promises, what it does not, and how releases work. |
What state the project is in
Worth knowing before you evaluate it:
- Ovrin is at v1.0.0, and the API is stable. All nine modules are tagged, and a breaking change
now requires a v2. - That promise is about compatibility, not accuracy. 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.
- Nobody outside the project has reported running it in production. That makes early reports
unusually valuable. - 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.