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 05 / PRIVATE · RELEASE GATE · v0.1.0

Slovenian Case Law Data Snapshots

Prepared Slovenian case-law data for your applications.

The data package combines structured, source-linked records in a SQL database, a derived vector index and a record of the package contents. It can provide a data foundation for a legal portal, research environment, another compatible application or OLC Engine.

The package is private and available to approved partners under agreed terms. It is refreshed after each successfully completed nightly synchronisation. Before integrating it into their system, partners can inspect the package's data watermark, record counts and package validation status.

Request partner access Review the curation pipeline
Status
PRIVATE · RELEASE GATE
Partner download
AVAILABLE
Refresh
SUCCESSFUL NIGHTLY SYNC
Public download
NOT OFFERED
  1. 01

    Curated for legal use

    Source-linked records are normalised, structured, checked and kept traceable.

  2. 02

    Maintained nightly

    The partner package advances after each successfully completed nightly sync.

  3. 03

    Standalone by design

    Use it for an independent portal, research workflow, legal product or OLC Engine.

  4. 04

    Private partner delivery

    Approved partners receive the coordinated data pair without a public repository dump.

01 / VALUE

A data foundation without repeating the initial retrieval.

The package contains data that has already been retrieved and structured, together with a prepared vector index. The receiving team can focus on application integration, search and the user experience. Use is not tied to OLC Engine; it requires a compatible environment and agreed access terms.

STANDALONE DATA PRODUCT

Use the foundation without adopting the whole OpenLegalCore system.

The coordinated pair can serve an independent portal, an existing legal product, a private research environment or OLC Engine. Its value is the maintained legal-data layer itself—not dependency on one interface or application.

Delivery
PRIVATE DOWNLOAD
Audience
APPROVED PARTNERS
Maintenance
NIGHTLY
Integration
STANDALONE OR OLC

02 / USES

For legal portals, research and OLC Engine.

The data foundation can support an independent portal, an existing legal application or an internal research environment. The partner remains responsible for its application, retrieval and ranking behaviour, and the conditions under which it is used.

  1. 01

    Launch a semantic case-law portal

    Start from a maintained corpus and retrieval index while concentrating product work on search experience, ranking and editorial context.

  2. 02

    Add case law to a legal product

    Integrate source-linked Slovenian decisions into an existing legal research, knowledge or professional workflow.

  3. 03

    Support private legal research

    Operate a controlled internal corpus for semantic retrieval, exploration and evidence-led legal analysis.

  4. 04

    Bootstrap OLC Engine

    Restore a prepared legal-data foundation beneath a compatible OLC Engine deployment and verify the package manifest before use.

03 / CURATION

How the data is organised and maintained.

Slovenian Case Law Pipeline retrieves supported records, preserves source links, structures data fields and prepares search segments. It checks for changes and reconciles the SQL database with the derived vector index. This does not mean that a lawyer has reviewed every decision or that the collection contains every record on the official portal.

  1. 01Official source

    Published Slovenian case law

  2. 02Case Law Pipeline

    Acquire · normalise · maintain

  3. 03Maintained data pair

    SQL database · vector database · manifest

  4. 04Partner system

    Portal · product · research · OLC

  1. 01

    Source-linked acquisition

    Supported routes retain source identity and provenance instead of becoming an anonymous text dump.

  2. 02

    Stable record identity

    Normalisation, content hashes and deterministic identifiers make changed records reviewable.

  3. 03

    Structured legal fields

    Decision metadata, dates, institutes, legal basis and body content remain separately usable.

  4. 04

    Deterministic chunks

    Search units are derived reproducibly rather than being created as an opaque one-off index.

  5. 05

    Nightly change maintenance

    Successful scheduled runs advance the maintained SQL database state and its partner package.

  6. 06

    Bounded reconciliation

    The derived vector database layer is checked against maintained, source-linked state and remains rebuildable.

Review the Slovenian Case Law Pipeline Inspect the public pipeline source

04 / CORPUS

What the measured collection contains.

The figures below describe the reviewed deployment on 3 September 2026. Each partner package records its own data watermark. The restore test dated 16 August 2026 is separate evidence of restoring the package tested on that date.

Maintained records
283,070
Court decisions
231,839
Scholarship and legal-opinion records
51,033
vector database points
1,422,596

CORPUS COMPOSITION

Decision route · DOC
231,839
Scholarship and legal-opinion records · ART
51,033
Other route · INJ
155
Other route · SEU
43

FIELD COVERAGE / MAINTAINED SQL DATABASE STATE

Coverage is measured on the maintained SQL database state. It describes populated fields, not legal completeness, correctness of every source record or parity with the official portal.

Identity + content state
100%
Title
99.98%
Source URL
99.93%
Decision / session date
99.93%
Main body
99.92%
Institutes
99.99%
Legal basis
98.08%
ECLI within decisions
>99.99%
Department within decisions
>99.99%

05 / DATA PAIR

Records and a search index in one coordinated package.

The SQL database stores structured records and links to their origin. The vector index is derived from those data and can be rebuilt. The package brings them together with a record of its contents and checks so that the receiving team can inspect their consistency. Neither data layer replaces the source portal or legal assessment of the documents.

SQL DATABASE / STRUCTURED RECORDS

The maintained legal-data state.

Source-linked records, normalised legal fields, content hashes, change state and deterministic chunks remain anchored in the database archive.

SQL database archive

VECTOR DATABASE / DERIVED INDEX

The corresponding semantic retrieval state.

Vectors and payloads accompany the package for semantic search while remaining a repairable derivative of the maintained, source-linked SQL database state.

Vector database snapshot

DATED RESTORE PROOF + CURRENT PACKAGE CONTRACT

Evidence first. Manifest with every hand-off.

On 16 August 2026, a coordinated pair with 282,556 records and 1,411,649 vector database points passed 40,096 checks with 0 failures. Current partner packages move forward after each successful nightly sync and therefore carry their own watermark, counts and validation state.

Package watermark
LATEST SUCCESSFUL NIGHTLY SYNC
Source watermark
RECORDED
SQL database archive
INCLUDED
vector database snapshot
INCLUDED
Schema + versions
RECORDED
Record + vector counts
RECORDED
Checksums
INCLUDED
Access + terms
PARTNERSHIP-SCOPED
Validation state
RECORDED

The 16 August pair is dated restore-test evidence, not the watermark of the current partner package. Partner download is private, refreshed after each successful nightly synchronisation and governed through a scoped partnership; no anonymous public download is offered.

06 / ACCESS

Access through a partnership agreement.

Describe how you intend to use the data and the environment in which it will operate. We then agree the scope, technical compatibility and access terms. Private downloads are available to approved partners; anonymous public downloads are not offered.

FROM ENQUIRY TO DOWNLOAD

  1. 01

    Describe your deployment

    Tell us what you are building, how the data will be used and where it will operate.

  2. 02

    Review fit and terms

    We review technical compatibility, rights, attribution, operating expectations and support needs with you.

  3. 03

    Receive partner access

    Once scope and terms are agreed, the current private package is made available for download.

CURRENT ACCESS STATE

Status
PRIVATE · RELEASE GATE
Partner download
AVAILABLE TO APPROVED PARTNERS
Public download
NOT OFFERED
Refresh
AFTER EACH SUCCESSFUL NIGHTLY SYNC
Terms
PARTNERSHIP TERMS

The partner package is refreshed after each successfully completed nightly synchronisation. If a run does not complete successfully, the latest successful package remains the current download.