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

Jurisdictions / Legal foundation

A legal method needs the right legal foundation.

Engine currently uses the Slovenian legal foundation. EU law, additional sources and other national jurisdictions are separate development directions.

We connect the same legal method with the relevant sources, their versions over time and the rules governing their use.

01 / Current foundation

Slovenia

The Slovenian legal foundation brings together legislation from PISRS and case law. Alongside the sources themselves, preparation, refreshes and traceability matter: from the original record to the material Engine uses in legal work.

Legislation · Case law · Acquisition and curation

Explore the Slovenian legal foundation

01 / Legislation

Legislation from PISRS

Texts, their structure and versions over time.

02 / Case law

Publicly available decisions

Decisions, case information and source references.

From the original record to the material Engine uses in legal work.

02 / Development directions

Broader sources. New jurisdictions.

Other jurisdictions

In testing

What a new jurisdiction requires
  1. Prepare local legal sources for Engine’s shared cognitive method.

  2. Prepare versions of the sources over time and the rules governing their use.

  3. Check results in the relevant legal environment.

Expected release:

Other jurisdictions on the roadmap

03 / Foundation and transparency

What to check in a legal foundation

Coverage
Which collections and periods are covered, and which checks have been performed.
Source and traceability
Who issued the material and how it links to the original records on which legal work is based.
Refreshes
How material is acquired, prepared, organised and maintained, and how collections and their versions over time are refreshed.
Terms of use
The access arrangements and rules governing the use of each tool or data delivery.
Review the Slovenian legal foundation

04 / Collaboration

A legal foundation for your work

Do you need a particular collection of sources, or want to collaborate on a legal foundation for another jurisdiction? Tell us about the area, intended use and scope of the collaboration.

Propose a collection or jurisdiction