News / public record

Checking
  1. Update / Component / Scope · CheckingOLC Engine: a renewed presentation of legal workThe bilingual Engine page now presents the approved version 0.1.0 scope, its legal-work method and the boundary between current capabilities and planned expansion.
  2. Article · CheckingA Server in the Office Is Not a Security StrategyWhy an office server, cloud service, email route or encrypted backup must be assessed through capabilities, responsibility and evidence—not location alone.
  3. Article · CheckingWho Controls the Legal AI Stack?Public code can enable inspection without proving control of the whole system. Follow versions, provenance, data sovereignty, exit and regulatory roles in legal AI.
  4. Article · CheckingConfidentiality Does Not End at the Chat WindowConfidentiality is a property of the complete data path, not the chat window. What do DPAs, de-identification and local deployment solve — and why is the OLC gateway still only a concept?
  5. Article · CheckingWhen a High Score Hides a Critical Legal ErrorA high benchmark score does not establish that legal AI is dependable for every problem. This article explains how to measure critical errors, retrieval, abstention, evaluators and the path to a legal answer.
  6. Update / Component / Readiness · CheckingWord Connector public presentation 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.
  7. Update / Component / Release · CheckingOpenLegalCore Word Connector v0.1.0-beta.1 is publicThe Apache-2.0 source-only beta provides a verified Word for the web path for researching Slovenian legal sources through OLC Engine, directly or through Open WebUI.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. Update / Project · CheckingPrivate security reporting is now availableOpenLegalCore now provides a monitored project-wide private channel and a canonical security-reporting policy.
  14. 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.
  15. 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.
  16. 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.
  17. 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 provides a verified Word for the web path for researching Slovenian legal sources 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. The minimal path sends either a standalone question without document context or a request based on 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.