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 register

COMPONENT / 07 · SYSTEM CORE

OLC Engine

FROM LEGAL LANGUAGE TO LEGAL REASONING

Artificial intelligence should not only write like a lawyer.It must also think like one.

System map / 09 componentsOLC EnginePRIVATE · v0.1.0

Component relationships · not a release sequence

OLC Engine brings the cognitive discipline of a lawyer into a software process: identify what matters, organise the case, check the law and evidence, test opposing positions, develop a strategy and prepare the appropriate legal document.

It connects a universal method of legal work with the sources and rules of a specific jurisdiction and the material of an individual case. The foundations, results and open questions of that work can be reviewed.

For the individual lawyer and the whole team.

The model provides generative capability. Engine gives it a legal method.

Current build
PRIVATE · v0.1.0System core
Current jurisdiction
Slovenia
Licence
PARTNERSHIP TERMSBy individual agreementsales@openlegalcore.org
Client
OLC Legal Workspace

01 / A NEW PARADIGM

The next legal tool is not a faster typewriter.

01 /PEN

The pen preserved legal thought.

02 /TYPEWRITER

The typewriter made it faster to put that thought into writing.

03 /COMPUTER

The computer enabled the search, reproduction and digital processing of legal material.

04 /GENERATIVE AI

Today, generative AI can produce convincing legal text in seconds.

01Threshold / generative capacity

Each of these steps changed how we work with legal material. Generative AI raises the next question: how can its capability be connected to the judgment that produces a well-founded legal work product?

02Before the text / decisions

Before the text comes a series of decisions.

Who made the assertion? What supports it? Which legislation was in force at the relevant time? Which judgment is comparable? What would the opposing party challenge? Does a missing document change the assessment? What result does the procedural position require?

A fluently written appeal may rely on the wrong historical version of a statute. An opinion may treat a party’s assertion as an established fact. A recommendation may overlook an adverse judgment or an exception on which the outcome depends. The quality of the work product therefore also depends on how the case was handled.

03Engine premise / disciplined method

OLC Engine connects generative capability with a structured legal method. It clarifies the task, determines the work required, uses the appropriate material and sources, tests possible interpretations and checks how far the underlying material supports a conclusion.

Legal text is the result.Legal judgment is the path to it.

03 / System core

One core. Connected legal work.

OpenLegalCore connects legal sources, document processing, the state of a matter and the user workspace. Maintained legislation and case law databases provide the legal foundation. Engine processes case material, guides analysis and connects the results. OLC Legal Workspace enables users to work in Conversations and Matters.

Document processing is included in Engine. Its Worker handles the import and preparation of text, PDF files, office documents and images, including OCR and the preservation of links to individual pages. Engine extracts statements and legally relevant facts from the prepared material and links them to supporting passages.

For each task, Engine uses the relevant case material and execution settings tailored to the required result. A structured plan defines the necessary stages, the components involved and the connections between their results.

Two forms of memory. One connected method.

Legal memory consists of maintained legal sources: legislation, case law, record identities and their versions over time.

Case memory preserves the participants, statements, evidence, contradictions, questions and changes in an individual matter. Across Conversations and Matters, it provides continuity for further work.

Engine connects both foundations. A legal source acquires meaning in relation to the specific facts of a matter; a statement or piece of evidence is also assessed against the law applied. The identity of the source, its legal role and its version over time remain part of this connection.

Eight tasks in the legal process

Attention

Clarify the task, participants, procedural position, objective and missing information.

Case model

Organise events, statements, evidence, findings and contradictions, and preserve the connections between them.

Authoritative sources

Retrieve the relevant legislation and case law, with source identities, citations and the relevant temporal basis.

Hypotheses

Compare possible legal characterisations and test them against facts, evidence and sources.

Testing opposing positions

Consider adverse sources, objections, exceptions and the conditions under which a conclusion would fail.

Strategy

Compare procedural options, consequences, risks, alternative paths and next actions.

Expression

Prepare the required form of legal text from the validated analytical foundation.

Review

Check the support for conclusions, citations, coverage of the material, the type of text and unresolved questions.

04 / Matter and documents

A matter must be organised before we can trust the answer.

A legal matter involves people and their roles, events and dates, statements and denials, documents and evidence, claims and objections, procedural actions, contradictions and questions that remain open. For further work, these categories need to retain their meaning and their connections to one another.

From document to usable assertion

Document processing is included in Engine. Its Worker handles the import and preparation of text, PDF files, office documents and images. For scanned material, OCR converts the content into text and preserves links to individual pages. Extracted assertions are linked to supporting passages so that their source can be revisited.

The path from document to legal work product preserves five levels:

  1. Original file — the material on which the work is based.

  2. Prepared text — content with preserved links to pages and source material.

  3. Extracted assertions — proposals with precise references to supporting passages.

  4. Matter records — selected items with their source, status and connections.

  5. Analysis and text — further work that draws on this foundation.

The coverage record shows the scope addressed and the remaining gaps. For large case files, a controlled, multi-stage review preserves continuity of evidence and records stopping conditions.

Case memory across Conversations and Matters

Persistent Case Memory provides continuity of work across sessions and clients, respecting identity and permissions. It operates in Conversations and Matters: it enables work to continue and connects material and findings in a structured register.

The register preserves participants and authorisations, statements with their sources, evidence, contradictions, corrections and revisions. It shows who made an assertion, what a document states, what remains disputed and what was later corrected.

An organised record also preserves disputed issues. A matter may contain differing statements and conflicting evidence. Their status and history remain important after the first answer has been produced.

Persistent findings also include unresolved questions, evidentiary gaps, procedural risks and next actions. They carry references, severity levels and a history of changes.

05 / Analysis, strategy and expression

Retrieval provides the material. Legal work begins when we test it.

In a complex matter, facts, documents and legal sources form the foundation for several connected tasks. Analysis establishes what that foundation supports. Strategy compares ways forward. Drafting shapes the result into the legal work product required by the task.

06 / Practical work

From case file to legal work product.

The scope of work adapts to what you want to accomplish.

  1. Legal question

    — clarification of the question, sources used, a reasoned explanation and remaining uncertainties.

  2. Complex matter

    — a review of facts and evidence, legal questions, alternatives, opposing positions, risks and gaps.

  3. Procedural decision

    — a comparison of options, objectives, strengths, vulnerabilities and next actions.

  4. Opinion, contract or submission

    — drafting from an analytical foundation, with a structure and scope suited to the task.

  5. Large case file

    — a controlled review of material with a coverage record, connections between evidence and findings, and stopping conditions.

Deadlines with calculations and a legal basis

Determining a deadline requires attention to the legal characterisation of the triggering event, the version of the rule in force at the relevant time, the method of counting and any exceptions. A disputed fact may also affect the calculated date.

Engine shows the calculation and the legal basis used. It highlights assumptions, missing information and disputed facts that may change the result.

Jurisdiction with a transparent decision path

When determining subject-matter and territorial jurisdiction, Engine connects the relevant information with the rules used. It shows the reasons for determining jurisdiction and highlights conflicting rules and missing information.

Quality throughout the process

Quality checks cover consistency between the result and its analytical foundation, support for conclusions, coverage of the material, any incomplete or truncated content and the suitability of the type of text. When an error is detected, Engine returns a report or stops execution.

A reviewable result also includes its limits: what has been addressed, which questions remain open and what foundation is needed to continue.

07 / Legal Workspace and collaboration

Legal work has a space of its own.

In Legal Workspace, users manage Conversations and Matters, organise material and review results. Behind the scenes, Engine connects legal sources, documents and case memory, carries out analysis, develops strategy and prepares texts.

Individually or together.

Engine also supports teamwork in Legal Workspace. Members of an organisation can collaborate in the same Conversations and Matters and use shared notes and files. Each member can also have a separate private space.

A shared matter enables work to continue from the same foundation: material, findings to date and open questions remain connected to the matter. Access to shared or private material determines what is available to each user for further work.

The workspace and the legal core.

Legal Workspace enables interaction, organisation of material and review of results. Engine guides the legal work, connects the necessary functions and checks the resulting work product.

Users thus work in a clear environment, while the legal method connects the individual steps into a whole — from the initial question to a reasoned legal work product.

Integration into a partner’s process.

Partnership starts with the specific work: who carries it out, what material they use and what result they need.

Together, we define the legal tasks, access to material, the way of working together and review of results. We adapt the scope of integration and the division of responsibilities to the organisation’s agreed process.

08 / Next expansion

The same legal method. New legal environments.

Version 0.1.0 focuses on the Slovenian jurisdiction. The next expansion will bring additional groups of legal sources and the use of Engine in other jurisdictions.

A broader legal foundation

The planned expansion includes European Union law, the case law of the Court of Justice of the European Union and the European Court of Human Rights, and search across publicly available decisions and opinions of the Slovenian Information Commissioner.

Each group of sources requires appropriate treatment: who issued the source, the period for which it applies and its legal weight. These distinctions must remain clear when sources are used in analysis and in the reasoning supporting the result.

Planned release: November 2026.

Other jurisdictions

Clarifying the task, assessing the facts, testing opposing positions and preparing a reasoned result form a shared cognitive method. Its legal foundation, however, belongs to the individual jurisdiction.

Engine is designed to connect the same method with different national legal databases. For each new jurisdiction, local sources, language and the rules governing their use must be put in place, and the results must be tested in that specific legal environment.

The shared method thus draws on the law applicable to the matter under consideration.

Status: in testing. Planned release: December 2026.

09 / Collaboration and licensing

We are building a method, not just a model.

Developing a legal method brings together legal, research and technical expertise. Legal professionals contribute their knowledge of sources, evidence, procedures and ways of doing legal work. Technical partners connect Engine with an organisation’s working environment. When expanding into other jurisdictions, we work with experts who know the local legal system and its sources.

Licensing by agreement.

OLC Engine is a privately developed legal core. Licensing and terms of use are agreed individually with each partner.

The agreement starts from specific needs: the purpose and scope of use, the working environment, the necessary integrations and support for integration into the organisation’s legal process.

Let’s discuss your legal process.

Tell us about your working environment, tasks and expectations. Together, we can define an appropriate scope for using Engine and a way of working together.

For licensing and partnership enquiries:

sales@openlegalcore.orgGet in touch →
10 / 10 · Public principle
  1. 01Source
  2. 02Record
  3. 03Reason
  4. 04Review

The law is too importantfor black-box systems.

Inspect what is public. Challenge what is claimed. Help build what is missing.