Skip to main content

Conformance checklist

The public conformance suite (conformance/run.mjs in the kit) runs in two modes. Results are JSON and reproducible, and record which mode ran.

Test endpoint. The endpoint exposes the test-only mock harness (/mock hooks). Every check runs.

npm run conformance -- --base https://your-test-endpoint.example --json results.json

Fixture-free read mode, for a production endpoint. A production endpoint must not serve /mock hooks. Copy conformance/fixtures.example.json, put in real ids from your endpoint, and pass it with --fixtures. The read checks, V1 and V4 run, and W1 runs if the manifest lists the olip-write profile. The stale id is optional; without it, R6 reports its stale part as skipped. Checks that need the mock harness are reported as skipped, never as passed.

npm run conformance -- --base https://your-endpoint.example --fixtures my-fixtures.json --json results.json
CheckProfileWhat it tests
R1olip-readManifest is valid and names the version and profiles
R2olip-readPublic discovery works with no login and no payment
R3olip-readPlain-English tenant query: practice and place interpreted, unknowns exposed; the side may be inferred or left unknown and asked
R4olip-readVerified license record and merely indexed record make visibly different claims; claim status present and kept apart
R5olip-readOrdering method and disclosure are stated, never paid, and stable for the same request; a nonpaying lawyer is listed
R6olip-readIntake policy marks unknown and stale fields
R7olip-readNo-match request returns legal aid options, not an empty dead end
R8olip-readUnsupported major version is refused with a stable code
W1olip-writeWrite operations need an authenticated caller
W2olip-writeA CaseBrief can be created, edited and validated without any transmission
W3olip-writePreview names exactly one recipient and every shared value
W4olip-writeSubmitting without the user's matching approval fails
W5olip-writeEditing the summary invalidates the old approval
W6olip-writeChanging the recipient needs a new approval
W7olip-writeReplay or duplicate submit causes no extra delivery
W8olip-writeSimulated delivery failure is FAILED, never DELIVERED or CONFIRMED
W9olip-writeEmail relay is SENT, not DELIVERED, without a recipient receipt
W10olip-writeSigned receipt verifies; acknowledgment is not acceptance
W11olip-writeStatus spoofing by the calling agent is refused; transitions are strict
W12olip-writeA prohibited jurisdiction workflow is blocked with an allowed alternative
W13olip-writeCancel before sending stops it; cancel after delivery states the limits
W14olip-writeExpired approval and expired token are refused
W15olip-writeCross-tenant isolation: another agent sees nothing
W16olip-writeCase text never appears in analytics, logs or other tenants' data
W17olip-writePrompt-injection text in a CaseBrief is stored as data and changes nothing
W18olip-writeOnly approved fields reach the recipient (data minimization)
W19olip-writeExtensions survive and unknown fields do not break the server (forward compatibility)
W20olip-writeClient discards the first response and retries: still one handoff (network failure reconciliation)
W21olip-writeStatus machine published and every recorded event is a legal transition
X1olip-a2a-bindingA2A agent card and message/send reach the same operations

What a pass means, and does not mean​

"Passes OLIP 1.0 Part 1 olip-write conformance suite vX on " means the endpoint passed those automated technical tests on that date with fictional data. It does not mean the lawyer is verified, licensed in a given state, approved by any bar or regulator, compliant with referral or advertising rules, confidential, privileged, or recommended.

  • There is no certification and no "OLIP Certified" mark. Only the published suite decides, and anyone may run it for free.
  • State it plainly: for example "Supports OLIP 1.0 Part 1 (read, write). Self-tested 2026-11-06." Never "OLIP certified lawyer", "approved", "verified by OLIP", or a badge next to a lawyer's name.
  • Keep three claims separate: technical conformance, identity evidence level, and jurisdiction permissions.
  • Expiry: a self-test result is current for 90 days or until a new suite version, whichever comes first.

These rules are proposed; see Governance: conformance and mark rules.

Recorded results​

EndpointResultDateNote
Node reference mock (test endpoint)35 pass, 0 fail2026-11-070.1 and 0.2 checks; sponsor's machine, fictional data
Node reference mock (fixture-free read mode)12 pass, 23 skip2026-11-07shows what a production endpoint can run
Python second endpoint29 pass, 6 skip (X1 A2A; V1 to V5, 0.2 not offered)2026-11-07same author as the Node endpoint

No third-party endpoint has been tested.