Skip to main content

OLIP specification

Current versionOLIP 2.0 (2026-11-14): the legal-client lifecycle after the handoff, built on OLIP 1.0
Previous versionOLIP 1.0 (2026-11-10): Part 1: Core plus Part 2: Additions
StatusPUBLISHED OLIP 2.0, the sponsor's current release. STABLE OLIP 1.0, text frozen 2026-11-11 (frozen file list); not adopted by any standards body and not independently reviewed
Canonical textOLIP 2.0; OLIP 1.0 Part 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, signed for OLIP 1.0 (Licensing)
EditorThe initial sponsor (Digital Crossings Inc.) until an independent editorial group exists
Released versionsOLIP 2.0, 2026-11-14; OLIP 1.0, 2026-11-10. No standards body has adopted any version.

Read​

  1. Status: exactly what is written, tested and not built.
  2. OLIP 2.0: conflict-aware intake, consultation, firm-confirmed engagement, ongoing communications and matter closure.
  3. OLIP 1.0 overview: the two parts, wire identifiers, and what 1.0 means.
  4. Part 1: Core: normative requirements (MUST, SHOULD, MAY per RFC 2119 and RFC 8174).
  5. Part 2: Additions: key bindings, signed status webhooks, intake capability card.
  6. Security considerations and the threat model.
  7. Status machine: every state and allowed transition.
  8. Versioning and compatibility.
  9. Proposals and open questions: what is being considered for later versions.

Download​

All files and checksums: Downloads.

Provenance​

OLIP 0.1 was written on 2026-11-06 from the sponsor's earlier work on agent-to-lawyer intake (its open protocol workstream, "V7"), then revised on 2026-11-07 for publication (schema identifiers moved to https://olip.ai/spec/0.1/schemas/; a quickstart walkthrough added). On 2026-11-10 the sponsor published both parts together as OLIP 1.0 (decision D-16), with no change to any requirement. Every change is in the changelog.