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

OLC LEGAL COGNITIVE WORKSPACE

OLC LegalWorkspace

Work through the matterin conversation.Keep every legal stepunder review.

OLC Legal Workspace is the planned first-party work surface for OpenLegalCore. Conversation leads the work while documents, legal sources, facts, evidence gaps, deadlines and decisions remain connected in one controlled matter record. Reviewed work can then move into a controlled legal document.

OLW‑3.2 EDITORIAL RECONSTRUCTION / VIEW 01 — CONVERSATION + MATTER CONTROLNOT A RELEASED PRODUCT
Status
Planned
Design baseline
OLW‑3.2
Delivery
Web first
Desktop
Windows · macOS · Linux
Product code
Not started

01 / WORKSPACE

Conversation moves the work.The matter keeps the record.

OLC Legal Workspace is a legal cognitive workspace—not a generic chatbot or a collection of disconnected tools. Conversation moves the work; the matter keeps documents, sources, candidate and reviewed facts, evidence gaps, deadlines, decisions and review states connected.

01 / CONVERSATION

Ask, analyse, direct and draft.

Work in one continuous, matter-aware surface.

02 / MATTER MEMORY

Keep the legal record connected.

Documents, notes, facts, sources and decisions remain linked.

03 / MATTER CONTROL

Make the boundary visible.

Separate missing inputs and blockers from analytical suggestions.

04 / REVIEWED OUTPUT

Prepare controlled legal documents.

Move accepted work toward named human approval.

The same matter model is intended for lawyers and legal teams in law firms, notarial offices, companies, organisations, institutes and public administration—and for people managing their own legal affairs where a controlled legal record is appropriate.

02 / CONVERSATION

Ask naturally.Work structurally.

The lawyer can instruct, question a source, compare facts, record a decision and request a draft without leaving the matter. Each next step retains its source and review context.

USED SOURCES

See what supports the work.

Documents and legal authorities remain visible beside the answer or draft.

NEEDS ACTION

Surface what is missing.

Unconfirmed facts, absent evidence and open deadline controls stay explicit.

PROPOSALS

Keep suggestions provisional.

Model output remains a proposal until legal review accepts or rejects it.

NEXT STEP

Continue without losing context.

Unresolved conditions travel with the workflow.

Conversation is the work surface, not the record of truth.

A material fact, source, warning, date, note, decision or draft change does not become part of the reviewed matter record merely because it appeared in conversation. Explicit human action determines what is accepted, corrected, rejected or carried forward.

AI Notes follows the same rule.

Source media, transcript, synthesis, corrections and the approved note remain separate records, with explicit permissions for recording, retention and access.

03 / MATTER CONTROL

Make the gaps visible.Control what moves next.

Matter Control keeps three states beside the conversation: what can move, what must stop and what still requires a lawyer’s judgment.

OLW‑3.2 EDITORIAL RECONSTRUCTION / VIEW 02 — MATTER OVERVIEW + FACTS & EVIDENCENOT A RELEASED PRODUCT

DETERMINISTIC CONTROL / BLOCKING

A defined condition with a verifiable state.

If a required service date is missing, a dependent deadline calculation remains blocked until the input is supplied and linked to a source.

ANALYTICAL SUGGESTION / REVIEW REQUIRED

A model-generated observation, not a fact.

If two documents appear to state conflicting dates, the conflict remains a proposal for legal review—not an automatic blocker.

Evidence gap

Referenced evidence is absent, incomplete or unlinked.

Fact conflict

Source-linked assertions differ and need legal review.

Deadline control

Trigger, selected rule and calculation remain inspectable. A proposed date becomes controlled only after human confirmation.

Source control

Exact source, version or valid-as-of identity, and the cited passage remain available.

The intended interface may calculate, compare and propose. It may not accept facts, confirm working deadlines, approve legal analysis or release a document on the lawyer’s behalf.

04 / WORKFLOW

From client instructionto a lawyer-reviewed document.

One representative legal task moves from instruction to export preparation. Source links, open limitations, deadline controls and human approvals remain visible at every step.

01

Instruction captured

The legal task enters the matter through conversation.

02

Documents reviewed

Relevant files are identified; missing attachments remain visible.

03

Facts linked

Candidates retain exact references and an explicit review state.

04

Deadline confirmed

Trigger, selected rule and date remain reviewable before human confirmation.

05

Sources attached

Applicable authorities stay linked to the analysis and draft.

06

Draft reviewed

Coverage, deadline control and disclosed limitations are checked.

07

Lawyer approval recorded

Exact version is prepared for export; nothing is sent, signed or filed automatically.

OLW‑3.2 EDITORIAL RECONSTRUCTION / VIEW 03 — REVIEWED DRAFT + EXPORT PREPARATIONNOT A RELEASED PRODUCT
What OLW‑3.2 demonstrates

It closes one complete interaction path in a functional wireframe. It demonstrates the intended workflow architecture—not a released application, production performance or an automated legal conclusion.

05 / DELIVERY

Distinct components.One legal workflow.

OLC Legal Workspace brings distinct OpenLegalCore components into one reviewable legal process without erasing their boundaries. Inputs, outputs and human decisions remain visible within the matter.

INTENDED SYSTEM RELATIONSHIPS / NOT CURRENT PRODUCTION INTEGRATIONS

LEGAL OCR PIPELINE

Reviewable document intake

Ordered material from image-based sources.

LEGAL SOURCE PIPELINES

Maintained legal sources

Legislation and case law for research and analysis.

LEGAL FACT EXTRACTOR

Source-linked candidates

Source-linked proposals that remain candidates until human review.

OLC ENGINE

Orchestration and analysis

Retrieval, analysis and controlled drafting orchestration.

WORD CONNECTOR

Controlled document extension

A separate public source-only beta for bounded legal-source research inside Word. Any future Workspace integration remains an intended relationship, not a current production integration.

OLC LEGAL WORKSPACE

One human-controlled work surface

Conversation, matter state, review and the human decision boundary.

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 + service model
Not yet decided