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 04 / PUBLIC · v0.1.7

Slovenian Case Law Pipeline

Records from the official judiciary service.A maintained data path for real legal workflows.

The component checks supported records in the OFFICIAL SOURCE / SUPREME COURT OF THE REPUBLIC OF SLOVENIASlovenian case lawSlovenia's authoritative national public case-law collection, published through the judiciary's official service administered by the Supreme Court of the Republic of Slovenia. It is the complete public corpus available through that service; statutory publication rules do not require every decision issued by every Slovenian court to appear.Open the official collection for new or changed content, normalises source-linked state in PostgreSQL and maintains the derived semantic index used by OLC Engine. It can also run independently or supply another compatible legal system.

Understand the component Open the public repository
Status
PUBLIC
Version
0.1.7
Licence
BUSL-1.1
Verified
2026-08-26
  1. 01

    Official service path

    Reads supported records from the judiciary service administered by the Supreme Court of the Republic of Slovenia.

  2. 02

    Scheduled maintenance

    Checks for new or changed source records on an operator-configured cadence.

  3. 03

    Legal-data anchor

    Maintains source-linked PostgreSQL state and the derived semantic index used by OLC Engine.

  4. 04

    Public code, separate data

    Publishes the pipeline while keeping source access and prepared data behind their own boundaries.

01 / FUNCTION + SOURCE

A component that turns published legal records into maintained working data.

The official judiciary service is administered by the Supreme Court of the Republic of Slovenia. The pipeline provides the repeatable acquisition, normalisation and integrity path that lets OLC Engine work from real, source-linked records rather than model memory.

MAINTAINED STATE / 3 SEPTEMBER 2026 · 22:46 CEST

These dated figures show the operating scale of the pipeline.

Maintained records
283,070
Court decisions
231,839
SOSC article records
25,132
SOPM legal opinions
25,901
  1. 01

    Published court decisions

    The maintained decision route covers records from the Supreme Court, higher courts, the Administrative Court and the Higher Labour and Social Court. It is not a claim to every decision issued by every Slovenian court.

  2. 02

    Legal scholarship

    SOSC contributes 25,132 professional-article records. It is primarily a bibliographic index; 481 records passed the reviewed full-text rule.

  3. 03

    Related legal records

    SOPM contributes 25,901 legal opinions and positions. The maintained state also contains 198 records on the separate INJ and SEU routes.

02 / SCHEDULED DATA PATH

Check what changed. Apply only the work that is required.

Each run checks a controlled overlap window, fetches supported detail, updates authoritative PostgreSQL state, reconciles the derived index and advances the checkpoint only after the complete path succeeds.

  1. 01Check source
  2. 02Discover changes
  3. 03Fetch detail
  4. 04Normalise
  5. 05Maintain stores
  6. 06Advance checkpoint

OPERATOR-CONFIGURED CADENCE

The schedule belongs to the deployment.

Operators choose a cadence that fits their source entitlement, workload and operating policy.

REVIEWED OPENLEGALCORE DEPLOYMENT

Nightly at 04:30 · Europe/Ljubljana.

The last measured run completed successfully in 33 seconds and advanced the checkpoint.

03 / TRUST + CONTROL

The official record stays authoritative.The working state stays inspectable.

Credibility begins with provenance, not a vector database. The component keeps the external source, maintained PostgreSQL state and repairable Qdrant index in distinct roles, then constrains how change can move between them.

OFFICIAL PUBLICATION SERVICE / EXTERNAL AUTHORITY

The source remains the source.

The pipeline preserves source identity and links. It does not become the official publication service or the legal authority for a record.

POSTGRESQL / AUTHORITATIVE

Maintained document state lives here.

Normalised documents, deterministic chunks, content and metadata hashes, vector state and reconciliation decisions are anchored in PostgreSQL.

QDRANT / DERIVED

The semantic index can be rebuilt and repaired.

The sodnapraksa_current collection is derived from authoritative state. Missing vectors, stale payloads, absent points and orphaned derived points are repaired through a bounded plan.

  1. 01Source traceability

    Source identifiers, URLs, normalised state and the original API response remain distinguishable.

  2. 02Deterministic identity

    Stable document, chunk and point identities make repeated or interrupted intervals convergent.

  3. 03Bounded mutation

    Preflight, dual authorisation, work budgets and conditional writes constrain every mutating run.

  4. 04Recoverable retrieval

    Qdrant remains a derived index; PostgreSQL and a success-only checkpoint govern maintained state.

The component does not prove corpus completeness or legal correctness, and it has no authoritative global withdrawal feed. Ambiguous or incompatible state stops the bounded path instead of silently widening its claim.

04 / USE + ACCESS

One ingestion component. Three legitimate operating roles.

The pipeline is infrastructure beneath a legal workflow. It is not itself a search interface, ranking product, chatbot, legal-analysis engine or substitute for reviewing the official source record.

  1. 01

    OLC Engine data foundation

    Ground retrieval and later legal-cognitive work in maintained, source-linked Slovenian legal records.

  2. 02

    Standalone scheduled pipeline

    Run the component independently with operator-provided source access, infrastructure and schedule.

  3. 03

    Compatible legal workflow

    Supply another compatible research, retrieval or legal system without treating the component as a user interface or legal analyst.

PUBLIC COMPONENT

Inspect and deploy the pipeline.

The versioned repository contains implementation, tests, documentation and hardened deployment templates under BUSL-1.1.

OPERATOR RESPONSIBILITY

Bring approved access and infrastructure.

The operator supplies source entitlement, PostgreSQL, Qdrant, embeddings, backups, schedule and recovery policy.

PRIVATE · RELEASE GATE

Discuss a separately governed partnership.

A prepared PostgreSQL and Qdrant pair exists behind a distinct validation, rights, licensing and access gate. A conversation does not imply automatic access.

Review Slovenian Case Law Data Snapshots Discuss a data partnership

05 / MEASURED OPERATION

Current operating facts, versioned acceptance and explicit limits.

The dated production measurement shows a working scheduled pipeline at meaningful scale. The older acceptance record proves bounded, repeatable behaviour; neither record is a claim of legal correctness, complete source parity, universal compatibility or an SLA.

READ-ONLY FACT RECORD / 3 SEPTEMBER 2026 · 22:46 CEST

283,070

maintained source records in PostgreSQL at the measured deployment state.

Last success
3 SEPTEMBER 2026 · 04:30–04:30:33 CEST
PostgreSQL changes
76
Qdrant upserts
546
Checkpoint
ADVANCED

SOURCE-RECORDED ACCEPTANCE

2,826

candidates were reconstructed in each of two final timer-driven runs. The stored state was already current, so no source-detail, embedding, PostgreSQL-document or Qdrant mutation work was required.

Accepted logic
v0.1.6
Current release
v0.1.7
Reviewed schedule
04:30 · Europe/Ljubljana
Outcome
EXIT 0

v0.1.7 / ACCEPTED COMPATIBILITY BASELINE

Runtime
CPYTHON 3.12.3
PostgreSQL
18.3 ACCEPTED BASELINE
Qdrant
1.17.1 ACCEPTED BASELINE
Collection
SODNAPRAKSA_CURRENT
Vector contract
3072 · COSINE
Embedding model
TEXT-EMBEDDING-3-LARGE