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 / Release / VERIFIED RECORD

Slovenian Legislation Pipeline v0.1.0 is public

OpenLegalCore has published the production-verified PISRS legislation-ingest component as a source-available BUSL-1.1 release.

RECORD FACTS

Published
21 August 2026
Verified
26 August 2026
Validation
Passed
Artefact access
Public
Change
Release
Version
0.1.0

PUBLIC RECORD / WHAT CHANGED

OpenLegalCore has published Slovenian Legislation Pipeline v0.1.0 under BUSL-1.1. The repository contains the ingestion implementation, operating documentation, offline tests and reviewed systemd service and timer templates for maintaining Slovenian legislation from PISRS.

The component discovers act and consolidated-text catalogs, fetches selected consolidated legislative text, keeps PostgreSQL as the authoritative structured state, creates deterministic article-aware chunks and maintains pisrs_current as a derived Qdrant semantic index. The tagged source records controlled production acceptance on 19 August 2026 across discovery, persistence, embeddings, vector and payload writes, idempotent repetition, checkpointing, reconciliation and supervised and timer-triggered nightly operation. This is a bounded source record, not a benchmark or SLA.

The immutable release identity is the annotated v0.1.0 tag at commit 4f904f667cfd7703a046e9723612eea87a6e8929; the repository has no separate GitHub Release object. The tagged README still carries its pre-authorisation publication marker, while the signed 21 August 2026 main commit records public source availability. Current main is two commits ahead of the tag: its later change updates the development test dependency to pytest 9.0.3 and records the related CVE fix, but does not create a new component version or change the tagged runtime contract.

The publication boundary remains explicit. The source release includes no PISRS credentials, PISRS data, legislative text, PostgreSQL or Qdrant snapshot, managed infrastructure, source or embedding account, retrieval or ranking API, legal-analysis engine, user interface or legal advice. Any public legislation data snapshot remains subject to its own separate release gate, and the exact BUSL-1.1 text controls production use.