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

Component / Release / VERIFIED RECORD

OpenLegalCore Word Connector v0.1.0-beta.1 is public

The 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.

RECORD FACTS

Published
6 September 2026
Verified
7 September 2026
Validation
Passed
Artefact access
Public
Change
Release
Version
0.1.0-beta.1

PUBLIC RECORD / WHAT CHANGED

OpenLegalCore has published Word Connector v0.1.0-beta.1 as an Apache-2.0 source-only beta. The repository contains the bilingual Microsoft Word task pane, gateway contract, tests, deployment guidance and public evidence for the verified Word for the web path.

The connector supports two partner-controlled deployment topologies. Its minimal path sends a question without document context or explicitly selected text directly to OLC Engine. An optional mediated path sends the same bounded request through an Open WebUI deployment backed by OLC Engine. Open WebUI is an integration choice, not a required component or an alternative legal engine. Both paths return source-linked answers and leave the Word document unchanged.

The release boundary remains explicit. It includes no hosted OpenLegalCore service, production backend, legal database, protected staging access, AppSource or Office Store listing, automatic provider fallback, credential sharing or document-editing workflow. Word for Windows and Word for Mac are not tested. Operators remain responsible for their chosen same-origin gateway, authentication, OLC Engine deployment and authorised legal-source access.