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

Slovenian Case Law Pipeline

Slovenian case-law data, prepared for use.For OLC Engine or another compatible system.

The component retrieves supported records from 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 and checks for changes. It organises the data in a SQL database, maintains a vector index for searching by meaning and preserves links to the source. It can run independently or serve as a data foundation for OLC Engine.

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

    Retrieval from the official source.

    Retrieves supported records from the portal administered by the Supreme Court of the Republic of Slovenia.

  2. 02

    Scheduled updates.

    Checks for new and changed records on a schedule chosen by the operator.

  3. 03

    Data for downstream use.

    Maintains structured records and a derived search index for OLC Engine or another compatible system.

  4. 04

    Public code, separate data terms.

    Source code is publicly available under BUSL-1.1. Source access and prepared data are governed by separate terms.

01 / FUNCTION + SOURCE

From published records to data for legal applications.

The case-law portal is administered by the Supreme Court of the Republic of Slovenia. The component retrieves and organises supported records while preserving their identifiers and source links. This lets OLC Engine or another compatible system work with data whose origin remains identifiable. The component is not an official judiciary service and does not replace checking the source documents.

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

Retrieving new and changed records.

Each run checks a defined time interval that overlaps the previous retrieval and fetches supported record details. It then updates the SQL database and reconciles the derived vector index. The checkpoint for the next retrieval advances only after the complete process 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

Traceable sources and controlled processing.

The source portal, structured records in the SQL database and derived vector index have different roles. The component preserves the links between them and supports checking changes and rebuilding the index. Technical data checks are not a legal review of the content.

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.

SQL DATABASE / AUTHORITATIVE

Maintained document state lives here.

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

VECTOR DATABASE / DERIVED

The semantic index can be rebuilt and repaired.

The sodnapraksa_current collection is derived from maintained, source-linked 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

    A vector database remains a derived index; a SQL database and a success-only checkpoint govern the 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

For OLC Engine or independent use.

The component prepares and maintains data for downstream use. It can supply OLC Engine or another compatible system. It does not itself provide an end-user search interface, chatbot, legal analysis or managed service. The operator provides appropriate source access and compatible infrastructure and complies with the applicable terms of use.

  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, SQL database, vector database, embeddings, backups, schedule and recovery policy.

PRIVATE · RELEASE GATE

Discuss a separately governed partnership.

A prepared SQL data layer with a derived vector index 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

What the measurements and tests show.

The measurement dated 3 September 2026 records the reviewed deployment. A separate, earlier acceptance record describes the verified behaviour of v0.1.6. Public version v0.1.7 updates documentation and release metadata, not the ingestion implementation. These records do not establish legal correctness, complete portal coverage, compatibility with every environment or a service-level commitment.

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

283,070

maintained source records in a SQL database at the measured deployment state.

Last success
3 SEPTEMBER 2026 · 04:30–04:30:33 CEST
SQL database changes
76
vector database 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 retrieval, embedding, record or vector update 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
SQL database
18.3 ACCEPTED BASELINE
vector database
1.17.1 ACCEPTED BASELINE
Collection
SODNAPRAKSA_CURRENT
Vector contract
3072 · COSINE
Embedding model
TEXT-EMBEDDING-3-LARGE