Community
OLIP 2.0 is published by its initial sponsor, and outside review is what it needs most: AI agent developers, intake and practice-management vendors, legal-aid organizations, lawyers, security practitioners and consumer advocates. You do not need an account with the sponsor or any company to implement, test or comment on OLIP.
Feedback
The source code, specification and issue tracker are public at github.com/olip-ai/olip. Open an issue for feedback, errors and proposals.
If you prefer email: notices@esqcopilot.com with "OLIP feedback" in the subject. This is the sponsor's published contact address. Please include the page or section, what you expected, and what you found. Do not send real client or case information. Security problems go to Security instead, never to a public channel.
Step-by-step guides:
- Report an error
- Propose a change to the protocol
- Test your own implementation
- Publish your conformance results
Contributing changes
The licenses were granted by the initial sponsor on 2026-11-07 (decision D-11). Contributions are made under the same license as the part of the project they change:
| You contribute to | Your contribution is licensed under |
|---|---|
| specification text, schemas, status machine, taxonomy | Creative Commons Attribution 4.0 International (CC-BY-4.0), with the OWFa 1.0 patent commitment |
| reference endpoints, clients, adapters, conformance suite, this website's source | Apache License 2.0 (Apache-2.0) |
| fictional examples and test fixtures | CC0 1.0 Universal (CC0-1.0) |
The name OLIP is not licensed by any of the above. No trademark registration is claimed. See Licensing for the exact terms.
Rules (they apply in the public repository and to emailed proposals):
- Open an issue first for any normative change, with: problem, proposal, compatibility impact, test plan.
- Every normative change ships with a schema update, a conformance test and an example.
- Never add real client, lawyer or firm data. Fictional data only (
.testdomains,TEST-license numbers). - Sign off commits under the Developer Certificate of Origin (
git commit -s).
Code of conduct
The project adopts the Contributor Covenant 2.1. Be respectful, assume good faith, keep discussion on the technical and policy merits, and never publish anyone's personal or case information. Reports go privately to notices@esqcopilot.com with "OLIP conduct" in the subject.
Decision process
Until an independent group exists, the sponsor edits the specification and records every decision with its reason in the decision log. The proposed process for later (lazy consensus for editorial changes, comment periods and votes for normative ones) is on Governance.
Roadmap
| Next | Why |
|---|---|
| Independent security review | Gate before any production use |
| A first implementation by another organization | Proves independent interoperability; see the invitation |
| Counsel review of policy rules | Gate before production write traffic |
| Proposals O-01 to O-08 | See Proposals |
| Hosted sandbox | Only once it can be operated safely with fictional data. Until then: the local kit and the browser simulation |