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

Slovenian Legislation Pipeline

Maintained, source-linked legislation.The PISRS data path beneath OLC Engine.

The component uses OFFICIAL SOURCE / GOVERNMENT OFFICE FOR LEGISLATIONLegislation (PISRS)Slovenia's national legal information system, maintained by the Government Office for Legislation. It provides legislation and other public legal documents, including unofficial consolidated texts, local acts and draft regulations, alongside selected European legal sources.Open PISRS to enumerate the configured act endpoints and consolidated-text catalogue. It fetches supported text, 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.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 PostgreSQL to govern component state and Qdrant 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

A component that turns PISRS records into maintained legislation infrastructure.

PISRS and the official publication remain the external authoritative sources. The pipeline provides the repeatable acquisition, normalisation and integrity path that lets OLC Engine work from source-linked legislation rather than model memory.

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

Enumerate. Apply required work. Advance after success.

Each run fixes a controlled source interval, enumerates the configured PISRS catalogue routes, fetches supported consolidated text, updates PostgreSQL, maintains compatible Qdrant state and advances the checkpoint only after the complete path 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

The official source 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.

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.

POSTGRESQL / 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.

QDRANT / DERIVED

pisrs_current is a repairable semantic index.

The fixed 3,072-dimension Cosine collection is derived from PostgreSQL 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

One ingestion component. Three legitimate operating roles.

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

  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, PostgreSQL, Qdrant, embeddings, backups, schedule and recovery policy.

AVAILABLE TO APPROVED PARTNERS

Discuss a separately governed data partnership.

A prepared PostgreSQL data layer and derived Qdrant 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

Dated operating facts, versioned acceptance and explicit limits.

The read-only fact record captures the reviewed deployment on 4 September 2026. The last successful scheduled run completed on 3 September. The v0.1.0 acceptance record proves bounded behaviour—not legal correctness, complete PISRS parity, universal compatibility or an SLA.

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

64,924

maintained act records in PostgreSQL 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 PostgreSQL persistence, embedding work, Qdrant 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
PostgreSQL
COMPATIBLE PISRS SCHEMA
Qdrant collection
PISRS_CURRENT
Vector contract
3072 · COSINE
Embedding model
TEXT-EMBEDDING-3-LARGE
Nightly timer
03:00 · EUROPE/LJUBLJANA