Invitation to build an independent implementation
OLIP needs at least two implementations by different organizations before it can be put forward to an independent standards body. Today there are none: both reference endpoints have the same author. If you build agents, intake software, legal-aid tools or security tooling, this is an open invitation.
What counts as independent
- Built from the published specification, schemas and OpenAPI, not by copying
reference/server.mjsoralt-python/. - Runs on your own infrastructure, with no sponsor-controlled backend behind it.
- Built by people who are not employed or paid by the sponsor for this work (say so if they are).
What to send
- The unedited conformance
results.jsonand the suite hash (how). - The run log (command, date, runtime, operating system).
- Where the spec was unclear, wrong or hard to implement. This feedback is the main point.
- Permission to list your implementation and to quote your feedback, or a request to keep it private.
What you get
A listing on Implementations on equal terms, credit in the decision log for any change your feedback causes, and nothing else: no fee, no badge, no endorsement in either direction.
The sponsor contacts potential implementers individually and only with their consent; it does not publish names, affiliations or counts of anyone who has not agreed in writing.