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

ROADMAP / GATES, NOT DATES

Progress is defined by what becomes true.

Dates can guide work. They do not release a component, complete a phase or change public status. Every transition requires a named gate and recorded evidence.

Gates
06
Complete
03
Active
01
Queued
02
Approved target dates
NONE

CURRENT RELEASE MAP

6 gates. 1 active boundary.

The map records present truth and the next evidence threshold. It is not a percentage-complete dashboard or a promise tied to a calendar.

Current gates
05
Complete
03
Queued
02
Target dates
NONE APPROVED

  1. PHASE 0 / BASELINE ADOPTED

    Identity and rules

    COMPLETE

    Project identity, release discipline, governance boundaries and the 02B design direction are adopted as the operating baseline.

    Target date
    NO APPROVED DATE
    Next readiness gate
    Baseline adopted and recorded in the canonical project contracts.
    Dependencies
    Project strategy · governance decisions · public information architecture · 02B design system
    Required evidence
    Recorded identity, governance, route, publication and visual contracts

  2. PHASE 1 / PUBLIC · v0.1.2

    First public OCR release

    COMPLETE

    The first public component, its offline review tooling and canonical acceptance method are published as one bounded release record.

    RECORDED OUTCOMELegal OCR Pipeline v0.1.2StatusPUBLISHEDAccessPUBLIC SOURCELicenceAPACHE-2.0
    Record
    Legal OCR Pipeline v0.1.2 is public

    The source repository and canonical acceptance record are public; the source filing and generated acceptance artefacts remain private and outside the package.

    Target date
    NO APPROVED DATE
    Next readiness gate
    Public package, component-specific licence and canonical acceptance record published.
    Dependencies
    Legal OCR Pipeline package · recorded acceptance campaign · deterministic human review
    Required evidence
    Tagged v0.1.2 package · APACHE-2.0 · canonical acceptance record

  3. PHASE 2 / FOUNDATION OPERATING

    Public project foundation

    COMPLETE

    The public website now connects canonical Roadmap, Governance and Deployment records with operational contribution and security channels and a verified publication workflow.

    Target date
    NO APPROVED DATE
    Next readiness gate
    Roadmap, Governance, Deployment, contribution paths, monitored security reporting and typed publication automation are operational.
    Dependencies
    Verified public records · documented deployment boundary · monitored reporting channel · typed publication controls
    Required evidence
    Canonical public routes · working contribution and security channels · derived publication records · passing whole-site verification · Product Lead approval

  4. PHASE 3 / EVIDENCE BEFORE EXPANSION

    Community and partnerships

    QUEUED

    Focused RFCs, contribution work and partner paths may expand only after review ownership and public triage boundaries are clear.

    Target date
    NO APPROVED DATE
    Next readiness gate
    Define focused RFC and contributor processes, maintained public triage channels and bounded partner participation.
    Dependencies
    Public project foundation · governance rules · reporting and contribution channels
    Required evidence
    Published contribution scope · review ownership · maintainer eligibility · bounded partner process

  5. PHASE 4 / ACTIVE · COMPONENT BY COMPONENT

    Selective opening

    ACTIVE

    Slovenian Legislation Pipeline v0.1.0, Slovenian Case Law Pipeline v0.1.7 and OpenLegalCore Word Connector v0.1.0-beta.1 are completed results inside this active gate. The pipeline releases do not publish their underlying legal data, and the Word release does not provide a hosted service or store distribution. No component release creates a project-wide release presumption.

    RECORDED OUTCOMESlovenian Legislation Pipeline v0.1.0StatusPUBLISHEDAccessPUBLIC SOURCELicenceBUSL-1.1
    Record
    Slovenian Legislation Pipeline v0.1.0 is public

    The source repository is public; PISRS credentials, legislative text and legislation data snapshots remain outside the package and behind separate access and release boundaries.

    RECORDED OUTCOMESlovenian Case Law Pipeline v0.1.7StatusPUBLISHEDAccessPUBLIC SOURCELicenceBUSL-1.1
    Record
    Slovenian Case Law Pipeline v0.1.7 is public

    The source repository is public; case-law records and data snapshots remain behind their separate release gate.

    RECORDED OUTCOMEOpenLegalCore Word Connector v0.1.0-beta.1StatusPUBLISHEDAccessPUBLIC SOURCELicenceAPACHE-2.0
    Record
    OpenLegalCore Word Connector v0.1.0-beta.1 is public

    The Apache-2.0 source-only beta, documentation, tests and Word-for-the-web evidence are public. It includes no hosted OpenLegalCore service, production backend, legal database, protected staging access or Office Store distribution; Word for Windows and Word for Mac remain untested.

    Target date
    NO APPROVED DATE
    Next readiness gate
    For the next Component: complete component-specific usefulness, rights, security, documentation, evidence and maintainability review.
    Dependencies
    Component-specific verification · release decision · rights and publication review
    Required evidence
    For the next Component: versioned package · licence · documentation · known limits · explicit approval

  6. PHASE 5 / LONGER-TERM DIRECTION

    Sustainable ecosystem

    QUEUED

    Stable releases, active maintainership, verified uses and accountable support must emerge from repeated public practice.

    Target date
    NO APPROVED DATE
    Next readiness gate
    Demonstrate repeatable public releases, active maintainership, verified uses and an accountable support model.
    Dependencies
    Community and partnerships · selective component opening · maintained public records
    Required evidence
    Versioned release history · maintained components · verified uses · accountable support record