News / public record

Checking
  1. Update / Component / Status · CheckingLegal Studio: technical profile confirmedLegal Studio 0.1.0 is in active development, preparing for the MVP. Its code remains private, with the same individually agreed partnership terms as Legal Workspace.
  2. 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.
  3. 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.
  4. 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.
  5. 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?
  6. 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.
  7. 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.
  8. 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 bounded research into Slovenian legal sources through OLC Engine, returning source-linked answers without changing the document.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. Update / Project · CheckingPrivate security reporting is now availableOpenLegalCore now provides a monitored project-wide private channel and a canonical security-reporting policy.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
Let’s talk
Menu
Let’s talk

Slovenian jurisdictionOpenLegalCore’s legal foundation

Slovenian law. Connected sources, a traceable foundation.

Engine uses legislation and case law when working with Slovenian law. We build this legal foundation by regularly acquiring, organising and maintaining collections. Links to original records and information about versions of legislation over time are preserved.

The Legal sources family contains the prepared legislation and case-law datasets. Their linked acquisition and maintenance tools belong to Document processing; each tool remains connected to its dataset.

01 / Connected sources

Two paths. One legal foundation.

01 / Legislation

Legislation from PISRS

Acquisition links legislative texts to their original records, structure and versions over time. We maintain a data and search foundation built from this material for subsequent use.

What we preserve alongside the text

  1. Original record and link to the source

  2. Structure of the legal text

  3. Versions of legislation over time

The tool and the prepared dataset

The ingestion pipeline belongs to Document processing and acquires and maintains legal sources. Its prepared dataset belongs to Legal sources and remains a private foundation for search and legal work.

02 / Case law

Slovenian case law

Publicly available decisions are organised with case metadata and links to original records. The maintained collection supports search and the use of decisions in legal analysis.

What we link to each decision

  1. Text of the court decision

  2. Case metadata

  3. Link to the original record

Tool source code · BUSL-1.1Datasets · PARTNERSHIP TERMS

The tool and the prepared dataset

Related bibliographic records

The case-law data pipeline also includes related bibliographic records of legal literature. Their scope and the availability of full text are explained in the detailed dataset record.

For legislation, we preserve the origin, structure and versions of the text over time.

For case law, we link the decision, case metadata and original record.

Use and access

Tools and datasets can be used independently or as Engine’s legal foundation.

The legislation and case-law ingestion components belong to Document processing and can run independently or with Engine. Their source code is public under BUSL-1.1. The datasets in Legal sources remain private and are available under agreed partnership terms.

Explore Engine

02 / Preparation pathway

Acquisition and curation

Acquisition obtains content from a source. Curation prepares it for use: texts are linked to document metadata, source references are preserved, and technical consistency and successful refreshes are checked. This makes the path from the source to the prepared collection traceable.

03 / Measured state

Coverage and refreshes

We publish dated information on collection size, refreshes and the checks performed. This shows the measured state of the relevant collection; detailed records also explain its limits.