Skip to main content

OLIP 1.0

Stable release

The current release is OLIP 2.0, which builds on OLIP 1.0 without changing it. OLIP 1.0 is the sponsor's stable release. The text is frozen, and later 1.x versions will not break anything built on it. It has not yet been independently implemented or security reviewed; that comes with a later "OLIP 1.0 reviewed" label.

VersionOLIP 1.0
StatusThe sponsor's stable release. Not adopted by any standards body, bar or regulator; not independently reviewed
Published2026-11-10, by the initial sponsor (Digital Crossings Inc.) as editor
Frozen2026-11-11 (decision D-28). The 45 normative files and their SHA-256 values: OLIP-1.0-SHA256SUMS.txt (SHA-256 of the list: b1e7339790ae0fc0a1f1029ec13f2a1137e89dec98ee9f1064bc3f6da6c7fb80)
PartsPart 1: Core and Part 2: Additions
Normative machine-readable filesJSON Schemas, OpenAPI 3.1, status machine, taxonomy
LicenseCC BY 4.0 with the OWFa 1.0 patent commitment (Licensing)
Patent commitmentDigital Crossings Inc. has signed the OWFa 1.0 patent and copyright agreement for OLIP 1.0: signed execution page (PDF)
Kitolip-1.0-kit.zip: text, schemas, reference endpoints, MCP adapter, conformance suite and tests

What OLIP 1.0 contains​

Part 1: Core (full text). Six modules: professional evidence, intake eligibility, CaseBrief, consent and authorization, authenticated delivery, and status lifecycle. It also covers operations, the policy gate, errors, versioning, bindings (HTTPS with OpenAPI 3.1, MCP and A2A) and conformance. 16 JSON Schemas and 14 fictional examples. First published 2026-11-06 as version 0.1.

Part 2: Additions (full text). Three optional features: key bindings, signed status webhooks and the intake capability card. It also records how implementer feedback (CR-01 to CR-09) was handled. 5 JSON Schemas and 5 generated examples. First published 2026-11-07 as version 0.2.

An endpoint that implements Part 1 is conformant to OLIP 1.0 Core. Part 2 features are optional: when they are missing, their checks report as skipped, not failed.

Wire identifiers stay the same​

OLIP 1.0 changes no requirement, schema or example from the two parts. So that existing software keeps working and published hashes stay valid:

  • Messages keep olip_version values "0.1" (Core) and "0.2" (Additions).
  • Schema $id URLs stay at https://olip.ai/spec/0.1/schemas/ and https://olip.ai/spec/0.2/schemas/.
  • Endpoint paths (/olip/v0.1/…, /olip/v0.2/…) and supported_versions values are unchanged.

From 1.0, the versioning rules apply in full: a minor version only adds optional members, adds states only with an adapter mapping, and adds error codes only. Breaking changes need a new major version.

What 1.0 means, and what it does not​

1.0 means the sponsor, as editor, considers the text complete and stable enough to build against, has frozen it, and commits to the compatibility rules above. Any change to a file on the frozen list is a new version, never an edit to 1.0.

It does not mean any of the following, and this site will not claim them:

  • Adoption by a standards body, bar, court or regulator. None has adopted OLIP.
  • Independent implementation or independent security review. Neither is done yet: both reference endpoints have the same author. Both come with a later "OLIP 1.0 reviewed" label.
  • Counsel review of the reference jurisdiction policy rules. Not done; those rules stay illustrative and marked pending_counsel_review.
  • Certification. There is no certification program, by design.

Current facts for each item: Status. Nothing on this site is legal advice.

Check your copy​

The kit includes the frozen list (OLIP-1.0-SHA256SUMS.txt, also downloadable on its own). After unzipping the kit, run (Linux; on macOS use shasum -a 256 -c):

cd olip-1.0
grep -v '^#' OLIP-1.0-SHA256SUMS.txt | sha256sum -c

Every line must say OK. The paths are relative to the kit folder.