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 02 / PUBLIC · v0.1.0

Slovenian Legislation Pipeline

Slovenian legislation data, prepared for use.From PISRS to OLC Engine or another compatible system.

The component retrieves act records, unofficial consolidated texts and authentic electronic editions of the Official Gazette from 1 March 2026 through GOVERNMENT WEBSITE / GOVERNMENT OFFICE FOR LEGISLATIONPISRS — Legal Information System of the Republic of SloveniaA government website providing access to legislation, case law and other legal information from Slovenia and the EU. It is administered by the Government Office for Legislation. Unofficial consolidated texts make legislation easier to consult, but are not official publications. PISRS also provides access to authentic electronic editions of the Official Gazette of the Republic of Slovenia from 1 March 2026.Open PISRS . It organises the data in a SQL database and a vector database, preserves links to the source and can run independently or supply OLC Engine or another compatible legal system.

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

    PISRS source path

    Enumerates configured act endpoints and the consolidated-text catalogue through operator-provided access.

  2. 02

    Structured text processing

    Preserves stable act and document identities, source text, article-aware structure and deterministic chunks.

  3. 03

    Maintained operational state

    Uses a SQL database to govern component state and a vector database as a derived, repairable semantic index.

  4. 04

    Public code, separate data

    Publishes the pipeline while keeping source access and prepared data under their own terms.

01 / FUNCTION + SOURCE

From PISRS records to data for legal applications.

The component retrieves and organises supported PISRS records while preserving source identifiers and links. It provides source-linked data for OLC Engine and other compatible legal applications. It does not replace checking the official publication.

MAINTAINED STATE / 4 SEPTEMBER 2026 · 17:11–17:18 CEST

These dated figures show the operating scale of the pipeline.

Act records
64,924
Consolidated texts
71,372
Structural blocks
13,576,374
Semantic chunks
278,146
  1. 01

    Act records and source metadata

    The maintained state contains 64,924 act records with stable register identities and retained source provenance. This is a measured deployment count, not a claim of complete numerical parity with PISRS.

  2. 02

    Consolidated-text versions

    The component holds 71,372 source-linked consolidated-text versions. It distinguishes 57,558 technically latest versions from 13,814 historic versions without treating technical recency as legal validity.

  3. 03

    Structured retrieval material

    Deterministic parsing produced 13,576,374 structural blocks and 278,146 semantic chunks. Article headings and technical version flags describe parser and pipeline state, not legal review.

02 / SCHEDULED DATA PATH

From retrieval to a successful update.

Each run establishes a processing interval, enumerates configured PISRS catalogues and retrieves supported texts. It then updates the SQL database and the vector database. The checkpoint advances only when the complete process succeeds.

  1. 01Check source
  2. 02Enumerate catalogues
  3. 03Fetch supported text
  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 03:00 · Europe/Ljubljana.

This is the reviewed deployment schedule, not a fixed requirement of the component.

03 / TRUST + CONTROL

Traceable sources.Inspectable processing.

Source data, processed records and the vector database serve different roles. The SQL database stores structured data and links to the source. The vector database supports searching by meaning while preserving the document’s origin and type.

PISRS + OFFICIAL PUBLICATION / EXTERNAL AUTHORITY

The source remains the source.

The pipeline preserves source identifiers, content and links. It does not become an official PISRS service or the legal authority for a record.

SQL DATABASE / AUTHORITATIVE

Acts, versions, articles and chunks are anchored here.

The compatible pisrs schema owns the structured document state, identities, hashes, chunk records and upload state used to plan each run.

VECTOR DATABASE / DERIVED

pisrs_current is a repairable semantic index.

The fixed 3,072-dimension Cosine collection is derived from a SQL database and the text-embedding-3-large contract. It is not an independent legislative source.

  1. 01Source traceability

    Raw provenance, normalised state and derived retrieval material remain distinguishable.

  2. 02Deterministic identity

    Stable act, document, block, chunk and point identities make repeated work convergent.

  3. 03Bounded mutation

    Preflight, work budgets, shared locking and conditional writes constrain mutating runs.

  4. 04Success-only currentness

    The checkpoint advances only after success; failed work cannot silently redefine the maintained interval.

The component does not prove complete PISRS parity, legal correctness or the legal validity of a version. Ambiguous, incompatible or incomplete state stops the bounded path instead of widening its claim.

04 / USE + ACCESS

For OLC Engine or independent use.

The component prepares a data foundation for downstream work. It can be used with OLC Engine or another compatible system. It does not itself provide an end-user search interface, chatbot, legal analysis or managed service.

  1. 01

    OLC Engine data foundation

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

  2. 02

    Standalone scheduled pipeline

    Run the component independently with operator-provided source access, compatible infrastructure and an operator-chosen 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 PISRS entitlement, SQL database, vector database, embeddings, backups, schedule and recovery policy.

AVAILABLE TO APPROVED PARTNERS

Discuss a separately governed data partnership.

A prepared SQL database data layer and derived vector database index are available to approved partners. Attribution, intended use, delivery and support are defined in each partner agreement; the software licence does not govern those data terms.

Review Slovenian Legislation Data Snapshots Discuss a data partnership

05 / MEASURED OPERATION

What the measurements and tests show.

The measurement dated 4 September 2026 records the reviewed deployment. The latest successful scheduled run recorded at that measurement completed on 3 September 2026. The v0.1.0 tests confirm the described technical behaviour in the reviewed environment; they do not establish legal correctness, complete PISRS coverage, compatibility with every environment or a service-level commitment.

READ-ONLY FACT RECORD / 4 SEPTEMBER 2026 · 17:11–17:18 CEST

64,924

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

Last success
3 SEPTEMBER 2026 · 03:00–03:02:46 CEST
Duration
166 SECONDS
Imported
3 DOCUMENTS · 0 FAILURES
Checkpoint
ADVANCED

SOURCE-RECORDED ACCEPTANCE

PASSED

The v0.1.0 source record covers the controlled path from catalogue discovery and source fetch through SQL database persistence, embedding work, vector database writes, reconciliation, idempotent repetition and success-only checkpoint advancement.

Accepted logic
v0.1.0
Accepted on
19 AUGUST 2026
Release tag
v0.1.0
Outcome
PASSED

v0.1.0 / ACCEPTED COMPATIBILITY BASELINE

Runtime
CPYTHON >=3.12,<3.13
SQL database
COMPATIBLE PISRS SCHEMA
vector database collection
PISRS_CURRENT
Vector contract
3072 · COSINE
Embedding model
TEXT-EMBEDDING-3-LARGE
Nightly timer
03:00 · EUROPE/LJUBLJANA