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

COMPONENTS / MODULAR LEGAL INFRASTRUCTURE

One architecture. Use only what you need.

OpenLegalCore is designed as a coherent system for legal work and as a set of independently useful components. Start with one capability, or connect components in a scoped, partner-controlled deployment.

Current partner path
OLC Engine 0.1.0 · maintained Slovenian legislation and case-law data · individually agreed integration
Components
09
Public
04
Private
04
Planned
01
  1. 01 / STANDALONE

    Start with one component.

    Run a public pipeline or OCR workflow independently, use a maintained legal-data foundation through a partnership, or evaluate a private component inside an existing product.

  2. 02 / ASSEMBLED SYSTEM

    Assemble a working system now.

    Partners can connect the private Engine and maintained legal data within an individually agreed legal or administrative workflow.

  3. 03 / FIRST-PARTY WORKSPACE

    Planned—not required.

    OLC Legal Workspace is the first-party user environment for Conversations and Matters; its client release and access remain separately governed. Word Connector is an independently released public source-only beta for bounded legal-source research in Word.

SYSTEM ROLE GROUPS

04

01 / SYSTEM ROLE

Processing and intelligence

Processing, extraction and orchestration layers that turn controlled inputs into reviewable legal work.

Records
03

07 / PRIVATE · SYSTEM CORE

OLC Engine

General-purpose legal cognition engine · system core

OPEN COMPONENT RECORD

A private legal AI core connecting maintained legal sources, case material, case memory, analysis, strategy and drafting for Slovenian law.

Current boundaryVersion 0.1.0 focuses on Slovenian law. Engine connects document processing, persistent Case Memory, analysis, strategy, legal drafting and review. OLC Legal Workspace provides the user environment for Conversations and Matters. The core remains private; commercial licensing and terms of use are agreed individually with each partner. Additional legal-source groups are planned for November 2026. Other jurisdictions are in testing, with a release planned for December 2026. These plans do not establish current availability outside Slovenia or public access to the source code.

02 / SYSTEM ROLE

Legal data pipelines

Acquisition and ingest paths for maintained Slovenian legal sources.

Records
02

02 / PUBLIC

Slovenian Legislation Pipeline

Legislation acquisition + ingest

OPEN COMPONENT RECORD

A source-available ingestion and integrity-maintenance pipeline that discovers and structures PISRS legislation in maintained, source-linked SQL database state and maintains a derived vector database semantic index.

Current boundaryVersion 0.1.0 is publicly released under BUSL-1.1. The release includes code, documentation, tests and deployment templates. It does not include PISRS credentials, source data, legislative text, SQL or vector database snapshots, managed infrastructure, retrieval interfaces or user interfaces.

04 / PUBLIC

Slovenian Case Law Pipeline

Case-law acquisition + ingest

OPEN COMPONENT RECORD

A component for retrieving and maintaining source-linked Slovenian case-law data. It can run independently or provide a data foundation for OLC Engine.

Current boundaryVersion 0.1.7 is public under BUSL-1.1. The repository contains code, documentation, tests and deployment templates, but no source credentials, court decisions, source records, embedding-provider access, managed infrastructure, retrieval interface or legal advice.

03 / SYSTEM ROLE

Data releases

Data packages for SQL and vector databases with separate publication gates.

Records
02

03 / PRIVATE

Slovenian Legislation Data Snapshots

SQL and vector databases release

OPEN COMPONENT RECORD

A carefully curated and regularly maintained Slovenian legislation data foundation for semantic search, legal portals, research workflows and OLC Engine, available as a private download to approved partners.

Current boundaryThe maintained SQL database state and derived vector database index are offered only through a scoped data partnership. They are not published on GitHub or offered as an anonymous public download; PISRS and the official publication remain authoritative.

05 / PRIVATE

Slovenian Case Law Data Snapshots

SQL and vector databases release

OPEN COMPONENT RECORD

Prepared Slovenian case-law data and a derived search index for compatible applications. Private packages are available to approved partners under agreed terms.

Current boundaryThe coordinated package of SQL and vector-database data is refreshed after each successful nightly synchronisation and offered only through a scoped data partnership. It is not published on GitHub or offered as an anonymous public download, and the official source remains authoritative.

04 / SYSTEM ROLE

Interfaces and connectors

First-party work surfaces and document-process connectors.

Records
02

09 / PUBLIC

OpenLegalCore Word Connector

Microsoft Word legal-source connector

OPEN COMPONENT RECORD

The public v0.1.0-beta.1 bilingual Microsoft Word connector sends the user's question, with optional explicitly selected text, and returns source-linked answers without changing the document. Its recorded direct and Open WebUI beta routes are historical tested scope, not a claim of Engine 0.1.0 client support.

Current boundaryThe Apache-2.0 v0.1.0-beta.1 release is source-only beta software verified in Word for the web. 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.