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 register

COMPONENT 05 / PRIVATE · RELEASE GATE · v0.1.0

Slovenian Case Law Data Snapshots

A carefully curated and regularly maintained case-law data foundation.

Start with source-linked legal records already normalised in PostgreSQL and indexed in Qdrant. The inspectable Case Law Pipeline keeps this foundation current for independent legal products or OLC Engine. Approved partners receive a private coordinated package after each successful nightly sync.

Each delivery keeps the authoritative PostgreSQL state, the rebuildable Qdrant index and the package manifest together, so the receiving team can inspect its watermark, counts and validation state before integration.

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

Begin with legal data already made operational.

Building useful case-law search begins long before the search box. This data product removes the need to repeat the initial acquisition, normalisation, structuring, chunking and embedding run—and keeps that foundation maintained afterwards.

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

Build the legal experience on top of a maintained corpus.

The same prepared foundation can support a public-facing product or a controlled internal workflow. Partners retain responsibility for their application, retrieval behaviour, user experience and legal operating context.

  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

Curated means a controlled, inspectable data process.

Curation here is operational: source-linked acquisition, supported-route selection, stable identity, structured legal fields, deterministic chunks, field checks, change maintenance and bounded PostgreSQL–Qdrant reconciliation. It does not claim that a lawyer has reviewed every decision or that the corpus exactly mirrors the official portal.

  1. 01Official source

    Published Slovenian case law

  2. 02Case Law Pipeline

    Acquire · normalise · maintain

  3. 03Maintained data pair

    PostgreSQL · Qdrant · 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 PostgreSQL state and its partner package.

  6. 06

    Bounded reconciliation

    The derived Qdrant layer is checked against authoritative state and remains rebuildable.

Review the Slovenian Case Law Pipeline Inspect the public pipeline source

04 / CORPUS

A substantial maintained state, measured and bounded.

The current fact record measures authoritative PostgreSQL state separately from the dated restore test. Counts below were read on 3 SEPTEMBER 2026 · 22:46 CEST; each partner package records its own latest successful nightly watermark.

Maintained records
283,070
Court decisions
231,839
Literature records
51,033
Qdrant points
1,422,596

CORPUS COMPOSITION

Decision route · DOC
231,839
Literature route · ART
51,033
Other route · INJ
155
Other route · SEU
43

FIELD COVERAGE / MAINTAINED POSTGRESQL STATE

Coverage is measured on the maintained PostgreSQL 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

Authoritative records and a rebuildable semantic index.

PostgreSQL and Qdrant travel as one coordinated package, but they do not have the same authority. PostgreSQL remains the source of maintained legal-data state; Qdrant is the derived retrieval layer that can be reconciled or rebuilt.

POSTGRESQL / AUTHORITATIVE

The maintained legal-data state.

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

PG_DUMP · CUSTOM FORMAT

QDRANT / DERIVED

The corresponding semantic retrieval state.

Vectors and payloads accompany the package for semantic search while remaining a repairable derivative of the authoritative PostgreSQL state.

COLLECTION SNAPSHOT · 3072D COSINE

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 Qdrant 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
PostgreSQL archive
INCLUDED
Qdrant 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

Private access begins with a data partnership.

The current coordinated PostgreSQL–Qdrant package is available to approved partners as a private download. Partnership review aligns the intended deployment, technical fit, rights, attribution, terms and any required support. The maintained database is not distributed through GitHub or as an anonymous public download.

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.