News / public record

Checking
  1. Update / Component / Readiness · CheckingOpenLegalCore Word Connector public launch is completeThe Apache-2.0 v0.1.0-beta.1 source-only release now has a complete public component record, homepage feature, Roadmap outcome and discovery path.
  2. Update / Component / Release · CheckingOpenLegalCore Word Connector v0.1.0-beta.1 is publicThe Apache-2.0 source-only beta brings verified Slovenian legal-source research into Word for the web through OLC Engine, directly or through Open WebUI.
  3. Article · CheckingLegal RAG Can Fail Before the Model AnswersA genuine provision can still support the wrong answer. This article shows how collection scope, document splitting, filters and ranking determine which sources a legal AI model ever sees.
  4. Article · CheckingWhen a Correct Citation Leads to the Wrong LawA genuine provision and an official link do not prove that the right law was applied. This article explains why legal AI must preserve temporal versions, transitional rules and the source-selection path.
  5. Update / Project · CheckingPublic project foundation gate is completeOpenLegalCore has completed its public project foundation gate: core public routes, bounded participation channels and publication controls are operating.
  6. Article · CheckingAn Audit Trail Is Not a Log: What a Digital Legal Process Must PreserveAn audit trail is useful when it permits a reasonable reconstruction of the particular process while remaining purpose-bound, appropriately protected and subject to retention rules.
  7. Article · CheckingArticle 86 of the AI Act: Does the right to explanation already apply to Annex III systems?The legal question remains open. The technical capacity to provide an intelligible explanation should not.
  8. Update / Project · CheckingPrivate security reporting is now availableOpenLegalCore now provides a monitored project-wide private channel and a canonical security-reporting policy.
  9. Update / Component / Release · CheckingSlovenian Case Law Pipeline v0.1.7 is publicOpenLegalCore has published the production-verified Slovenian case-law ingestion component as a source-available BUSL-1.1 release.
  10. Article · CheckingA Result Is Not a Method: Why Visible Methods Matter in Legal AIWhy legal AI needs inspectable sources, provenance and human review: a legal and technical analysis of the EU Artificial Intelligence Act and GDPR.
  11. Update / Component / Release · CheckingSlovenian Legislation Pipeline v0.1.0 is publicOpenLegalCore has published the production-verified PISRS legislation-ingest component as a source-available BUSL-1.1 release.
  12. Update / Component / Release · CheckingLegal OCR Pipeline v0.1.2 is publicThe first public OpenLegalCore component is available with code, tests, offline review tooling and a bounded acceptance record.
Explore the code
Menu
OLC Legal Workspace

COMPATIBLE CLIENTS / INTERIM ACCESS

The Workspace is planned. One client path is verified today.

If you already operate or have authorised access to an OLC Engine deployment, Open WebUI builds 0.9.5 and 0.11.3 are the only client builds currently verified for text-only, multi-turn use. They provide one interim conversational path—not the matter-aware OLC Legal Workspace.

Verified builds
Open WebUI 0.9.5 + 0.11.3
Profile
Text-only · multi-turn
Latest confirmation
2026-09-04
Access
Engine endpoint + credentials required

01 / AVAILABLE TODAY

Open WebUI is the verified reference path.

OLC ENGINEOPEN WEBUI 0.9.5 and 0.11.3TEXT-ONLY CONVERSATION

VERIFIED

Client builds
Open WebUI 0.9.5 + 0.11.3
Latest confirmation
2026-09-04
Acceptance
Two named client builds · passed

COVERED BY THE RECORDED PASS

  • Two consecutive turns
  • Elliptical follow-up
  • Refreshed source lookup
  • Linked source output
  • Streaming
  • Aggregate usage

OUTSIDE THE VERIFIED PROFILE

  • File upload
  • Multimodal input
  • Tools or function calling
  • Persistent CaseMemory
  • Complete Open WebUI coverage
  • Universal OpenAI API coverage
See the verified setup Open WebUI 0.11.3 release Visit Open WebUI

02 / VERIFIED SETUP

The configuration that was actually tested.

These settings reproduce the recorded client path once an engine operator has supplied the endpoint and credentials. This page does not provide a public hosted endpoint or publish credentials.

01 / ACCESS

Obtain operator access.

An available OLC Engine endpoint and operator-issued credentials are required.

02 / CONNECTION

Add the engine endpoint.

Use a dedicated OpenAI connection with API base <ENGINE ORIGIN>/v1and API type Chat Completions.

03 / MODEL

Select the recorded model.

Use the current test identifier lexai-engine-local, enable usage and leave unsupported overrides unset.

TESTED ENGINE SURFACE

01GET /v1/models02POST /v1/chat/completions03Bearer auth04SSE streaming · heartbeat events · non-streaming
Technical reproduction details
Connection
Dedicated OpenAI connection
API base
<ENGINE ORIGIN>/v1
API type
Chat Completions
Base model
lexai-engine-local
Usage
Enabled
Status updates
Optional · opt in
Extension header
{"X-LexAI-Extensions":"workflow-status-v1"}
System prompt
Empty
Advanced parameters
No unsupported overrides

MODEL PLACEMENTlexai-engine-local is a base/provider model configured under Admin Panel → Settings → Models. It does not need to appear under Workspace → Models.

03 / UNDER EVALUATION

Four named clients. No compatibility claim yet.

LibreChat, Jan, Onyx and LobeChat / LobeHub are evaluation paths, not working integration claims.

Compatibility here means a recorded test—not presumed support based on a logo or API label.

ClientPossible routeEvidence still requiredStatus
LibreChat Candidate custom endpointNamed client build + capability matrix pendingUNDER EVALUATION
Jan Candidate custom endpointNamed client build + capability matrix pendingUNDER EVALUATION
Onyx Candidate provider adapterAdapter fit + capability matrix pendingUNDER EVALUATION
LobeChat / LobeHub Evaluation route not yet fixedNamed client build + capability matrix pendingUNDER EVALUATION