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 registerComponent 08 / planned · functional wireframe

PLANNED WEB AND DESKTOP WORKSPACE

OLC LegalWorkspace

For a quick question.For the whole matter.From the first documentto a legal draft.

OLC Legal Workspace is the planned web and desktop interface for OLC Engine. Ask a question or add a document. For work that develops over time, create a matter with connected documents, conversations, notes and drafts. Engine 0.1.0 finds legal sources, analyses material and prepares drafts. The planned Workspace will provide the environment in which you review findings and decide what comes next.

INTERFACE CONCEPT / 01 — CONVERSATION IN A MATTERNOT A RELEASED PRODUCT
Status
Planned
Design baseline
OLW‑3.2
Delivery
Web first
Desktop clients
Windows · macOS · Linux
Product code
Not started

01 / WORKSPACE

Start with a conversation.Let the matter connect the work ahead.

A standalone conversation will support a quick question or an individual document without creating a matter. For longer work, a matter will connect documents and their versions, conversations, notes, legal sources, findings and drafts. Engine 0.1.0 preserves case memory across Conversations and Matters so work can continue from existing material and findings. Workspace’s client availability remains separate.

01 / CONVERSATION

Ask a question or add a document.

A standalone conversation for an explanation, analysis, legal research or a draft.

02 / MATTER

Continue where you left off.

A lasting matter context connects material, versions, conversations and previous findings.

03 / MATTER CONTROL

See what needs attention.

Missing documents, conflicting assertions, unresolved deadlines and suggestions for further work.

04 / REVIEWED OUTPUT

From findings to a draft.

Legal drafting with linked sources, corrections and approval of the final version.

The workspace is intended for legal professionals in law firms, notarial offices, companies, institutions, other organisations and public administration, as well as individuals managing their own legal affairs.

02 / CONVERSATION

Ask, compare, research.Build a basis for the next step.

In conversation, you will be able to request an explanation of a contract, a comparison of documents, research into legislation and case law, or a legal draft. Engine carries out research and analysis; the planned Workspace will show the sources used, open questions and suggested next steps alongside the response.

USED SOURCES

Open the source beside the finding.

Documents, statutory provisions and court decisions used in the work should be accessible beside the response or draft.

NEEDS ACTION

Check what is still missing.

The analysis should highlight missing material, inconsistencies and information needed to assess a deadline.

PROPOSALS

Assess the proposed approach.

You will be able to review, correct, accept or reject a proposed analysis or draft.

NEXT STEP

Continue without losing context.

Within a matter, the next task should build on earlier findings and retain open questions.

You decide what has been reviewed and accepted.

A conversation and its proposals may be retained in the matter, but a retained record does not by itself mean approval. Facts, findings and drafts must show what awaits review, what you have corrected and what you have accepted.

AI Notes: from recording to reviewed note.

AI Notes will turn an audio or video recording of a consultation or meeting into a transcript and a note containing important facts, agreements, open questions and next steps. You will be able to review and approve the note for inclusion in the matter. The original recording, transcript, proposed note and approved note will remain separate; recording, processing, retention and access will require appropriate permissions.

03 / MATTER CONTROL

See what is missing.Decide what comes next.

Beside the conversation, the matter overview should show missing documents, conflicting assertions and deadlines that need checking. From a warning, you will be able to reach the linked source and decide whether you need additional material, a corrected record or further analysis.

INTERFACE CONCEPT / 02 — ASSERTIONS AND SOURCESNOT A RELEASED PRODUCT

MISSING INPUT / CALCULATION BLOCKED

No calculation without the required input.

If calculating a deadline requires the date of receipt, the calculation cannot proceed without it. The date, supporting evidence and rule applied must be checked first.

CONFLICT IN THE MATERIAL / REVIEW NEEDED

Check the difference against the sources.

If Engine identifies different dates for the same event in two documents, it should show both passages. The lawyer assesses whether they conflict and how that affects further work.

Evidence gap

Which evidence is missing and which document refers to it.

Conflicting assertions

Who asserts what, where it is recorded and what is disputed.

Deadline control

The event that starts the deadline, the rule applied and the calculation for the lawyer to review and confirm.

Source control

The document or legal source used, its version or validity as of a given date, and the cited passage.

Engine analyses material and proposes results; the planned Workspace will support source review and recorded decisions. Confirming facts, deadlines, legal analysis and the final document version remains the lawyer’s responsibility.

04 / WORKFLOW

From material and a questionto a reviewed legal draft.

The illustration follows a contract termination dispute. Engine compares the claim, response and termination notice, then prepares a draft letter requesting the missing evidence. The parties give different dates of receipt, Annex 2 is missing and the deadline remains unresolved. The lawyer reviews the letter before approving a version for export.

01

Instruction

The lawyer describes the task and specifies what the letter should address.

02

Material review

The review covers the claim, response and available annexes, identifying missing material.

03

Facts and assertions

Records of events and the parties’ assertions are linked to passages in the documents.

04

Unresolved deadline

The date and rule for the calculation still need checking; the deadline remains unresolved.

05

Linked sources

The claim, the response and the termination notice are linked to the findings and draft.

06

Draft review

The lawyer checks the draft’s content, source references and stated limitations.

07

Approval and export

The approved version is ready for DOCX or PDF export. Sending, signing and filing are separate steps.

INTERFACE CONCEPT / 03 — REVIEWED LETTERNOT A RELEASED PRODUCT
What this design illustrates

The views illustrate the planned workflow from conversation to a reviewed draft. They are static representations of the OLW‑3.2 design; a working application is not yet available.

05 / DELIVERY

In the browser and on the desktop.With the same way of working.

The web client is planned first, with document upload or import. Later desktop clients for Windows, macOS and Linux are intended to work directly with files and folders you explicitly authorise. Both forms should use the same approach to organising matters, linking sources and reviewing results. Access to local files does not imply offline Engine operation.

COMPONENT ROLES IN THE PLANNED WORKSPACE

LEGAL OCR PIPELINE

Text from scanned material

OCR and document preparation are included in Engine 0.1.0, with links to source pages. The separately released Legal OCR Pipeline retains its own release record.

LEGAL SOURCE PIPELINES

Legislation and case law

Acquiring and preparing legal sources for Engine to retrieve during legal research and analysis.

LEGAL FACT EXTRACTOR

Records for Case Memory

Structured extraction is included in Engine 0.1.0. Extracted assertions remain review candidates and retain links to source passages. The standalone Legal Fact Extractor retains its separate private component record.

OLC ENGINE

Legal research, analysis and drafts

Engine 0.1.0 connects maintained legal sources, document processing, persistent case memory, analysis, strategy, legal drafting and review.

WORD CONNECTOR

Legal sources in Word

A separate public beta, distributed as source code, for legal-source research within a defined scope in Word. A connection with Workspace is planned and has not yet been implemented.

OLC LEGAL WORKSPACE

Your workspace

The interface for conversations, documents, notes, reviewing findings and drafts, and recording your decisions.

Interaction architecture
Recorded
Functional wireframe
OLW‑3.2 recorded
Product code
Not started
Web client
Next target
Desktop clients
Later · Windows · macOS · Linux
Public application
Not available
Licence
PARTNERSHIP TERMS