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

GOVERNANCE / NAMED RESPONSIBILITY

Founder-led.Publicly accountable.

Open participation does not dissolve decision rights. Responsibility for direction, boundaries, releases, access and identity remains visible and reviewable.

Current authority
01
Decision areas
06
Participation paths
04
Rights classes
04

01 / CURRENT AUTHORITY

Responsibility stays named.

Rajko Majcen currently carries the project’s product direction, component boundaries, release decisions and public/private governance boundary.

Model
Founder-led. Publicly accountable.
Public role
Founder and maintainer
Read the maintainer record

01 / PROJECT DIRECTION

Product direction

Authority
Founder / Product Lead
Decision right
Sets product direction and the order in which project work is pursued.
Boundary
Public discussion can inform direction; it does not transfer final responsibility.
Public record
Project roadmap

02 / COMPONENT BOUNDARIES

Scope and readiness

Authority
Founder / Product Lead
Decision right
Approves component scope, current boundary, access state and readiness gate.
Boundary
A named or documented component is not thereby public, released or available.

03 / RELEASE + PUBLICATION

Public status changes

Authority
Founder / Product Lead
Decision right
Approves releases, evidence publication and other public status changes.
Boundary
A date, plan or implementation does not change public status without evidence and approval.

04 / MAINTAINER + GOVERNANCE

Appointments and authority

Authority
Founder / Product Lead
Decision right
Appoints maintainers and approves changes to the decision-rights boundary.
Boundary
Maintainer status follows sustained judgement and trusted work; it is never automatic.

05 / PRIVATE DEVELOPMENT

Access decisions

Authority
Founder / Product Lead
Decision right
Controls access to private code, documentation, evidence artefacts and credentials.
Boundary
Private access is granted only for a bounded purpose and creates no decision rights.

06 / BRAND + IDENTITY

Project identity

Authority
Founder / Product Lead
Decision right
Protects the OpenLegalCore name, visual identity and public project representation.
Boundary
Brand rights remain separate from code, data and documentation rights.

PARTICIPATION / BOUNDED PATHS

Participation does not equal control.

OpenLegalCore welcomes specific work and bounded collaboration. Each path has a real purpose, and each stops before rights it does not create.

  1. 01

    Contributor / community

    Entry
    Public issues, documentation, synthetic test cases, focused pull requests or reviewed RFCs.
    Purpose
    Improve bounded public work through specific, reviewable contributions.
    Does not create
    A contribution does not create maintainer or decision rights.
    Open this path
  2. 02

    Maintainer

    Entry
    Sustained contribution, sound judgement, trusted review and explicit appointment.
    Purpose
    Carry an expressly assigned review or decision responsibility.
    Does not create
    Status is earned and appointed; it is not produced by volume or a single contribution.
    Open this path
  3. 03

    Partner / funder

    Entry
    A scoped review, integration, pilot, public bounty or other agreed support.
    Purpose
    Support a defined public or private outcome within an explicit scope.
    Does not create
    Funding does not buy governance, private access or maintainer status.
    Open this path
  4. 04

    Private access

    Entry
    An explicit agreement for a bounded development need.
    Purpose
    Provide only the private scope required for that agreed work.
    Does not create
    Access does not transfer ownership, maintainer status or decision rights.

Contributions, funding or access to private development do not create maintainer or decision-making rights.