OpenLegalCore is developing a legal AI engine tailored to the law of a given jurisdiction, along with supporting components for legal analysis and drafting. It brings 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 ↗, OFFICIAL SOURCE / SUPREME COURT OF THE REPUBLIC OF SLOVENIASlovenian case lawSlovenia's authoritative national public case-law collection, published through the judiciary's official service administered by the Supreme Court of the Republic of Slovenia. It is the complete public corpus available through that service; statutory publication rules do not require every decision issued by every Slovenian court to appear.Open the official collection ↗ and private documents together in controlled, traceable workflows whose operation and results remain open to human review.
The central partially open OLC Engine shows four linked functional layers: legal foundation and sources, case context and material, analysis and strategy, and drafting with traceable outputs. Professional review remains human-led. The Engine links legal sources, document processing and work environments.
An illustration of the system's composition, not a depiction of actual infrastructure.
Who OpenLegalCore is for
The same legal method.Different ways to use it.
Legal work takes place in different environments. A law firm may need an organised workspace for matters and documents. An insurer, bank or public institution wants to integrate the legal method into a system it already uses. OpenLegalCore therefore separates the legal core, workspace, jurisdiction-specific foundation and integrations. We connect them according to the workflow, deployment approach and rules for handling data.
01Legal workLegal Workspace · Active development · preparing the MVP
A workspace for legal professionals
Bring conversations, matters, documents and notes into one clear workspace. Legal Workspace is designed for independent lawyers, legal teams and law firms. It is being developed to support shared and private spaces, helping you review findings, drafts and decisions as the work progresses.
02Integration into an organisationOLC Engine 0.1.0 · private · active development
The legal method within your workflow
We can integrate Engine and the relevant legal foundation into your application or a specific step in your workflow. Together, we define the scope of implementation, connections to existing systems and how material is handled. Under a partnership agreement, we can adapt the working environment to your organisation and brand.
OLC Engine connects three groups of components: legal sources, document processing, and workspaces and connectors. The groups differ in purpose, development stage and access terms.
01
Legal core
Engine
0.1.0 · private · active development
The legal core connects case material, legal sources, analysis and drafting in a traceable workflow.
Open code is only the beginning.Legal infrastructure must preserve an inspectable record from source to use: what entered the system, how it was transformed, which limits apply, what human review covered and who remains responsible.
The standard /
An answer is not enough.
For OpenLegalCore, a legally material result is incomplete unless its sources and transformations can be traced, its method reviewed, its stated limits challenged, its human-review status recorded and responsibility for its use kept explicit. That inspectability is an engineering requirement—not a claim that open software makes the result correct.
The accountability record / five elements
01Source
02Transformation
03System limits
04Human review
05Responsibility
Across the record / four obligations
Four obligations turn openness into an operating discipline.
01Evidence
Inspect before trust
Code, methods, source handling and the scope of each claim must remain examinable within their stated access boundaries. Openness does not prove correctness; it makes unsupported claims easier to detect.
02Control
Control the operating boundary
Institutions must be able to choose their infrastructure, models and deployment boundary instead of making legal documents and system behaviour dependent on one opaque service.
03Infrastructure
Build reusable infrastructure
We build infrastructure that can be inspected, tested and developed. Public document-processing and ingestion tools, private legal datasets and Engine have distinct roles and terms of use. OCR and fact extraction also support work within Engine.
04Responsibility
Keep responsibility visible
Legally material output must remain traceable, reviewable and contestable. A system may support a decision; the person or institution making it remains responsible.
Required outcome /
Every legally material claim must remain connected to its sources, transformations, stated limits, review status and responsible person or institution.
Version 0.1.0 focuses on Slovenian law. Engine connects maintained legal sources, document processing, persistent Case Memory, analysis, strategy, legal drafting and review. The core remains private; commercial licensing and terms of use are agreed individually with each partner. Human review remains essential.
The diagram shows the connected functions of Engine 0.1.0.
Maintained legal sources → controlled legal work
01
Legal sources
PISRS, Slovenian case law and controlled matter documents.
02
Matter context
Persistent Case Memory across Conversations and Matters.
03
Legal functions
Rules, retrieval and specialist legal functions.
04
Analysis + strategy
Legal analysis and comparison of available paths.
05
Controlled drafting
Legal drafting connected to the analytical foundation and review.
06
Client or process
OLC Legal Workspace or an embedded Engine service.
Case foundation
Documents and memory
Document processing, OCR and structured extraction
Persistent Case Memory
Source-linked assertions and evidence
Legal reasoning
Analysis and strategy
Legal analysis
Procedural strategy
Specialist legal functions
Legal work product
Drafting and review
Task-appropriate legal drafting
Review of the result and its foundation
Human responsibility remains explicit
03 / USE AND INTEGRATION
The legal method where your work happens.
We can integrate OpenLegalCore into your legal department’s work or a selected organisational workflow. We start with a specific task: drafting or reviewing a contract, handling a claim, assessing a legal question or drafting a decision. The responsible team must review the material and results.
Legal work in different organisations
01Companies with legal departments
Contracts and legal opinions
Reviewing contractual questions and drafting contracts and legal opinions. Material may include contract versions, supporting documentation and the company’s internal rules. The scope of analysis is tailored to the specific task.
02Banks and financial institutions
Contractual relationships and complaints
Legal assessment of contractual relationships, complaints or a specific regulatory question. We connect the matter documentation and the institution’s internal rules with the relevant legal sources.
03Hospitals and healthcare institutions
Procurement, suppliers and employment relationships
Legal questions involving public procurement, supplier contracts and employment relationships. For the selected matter, we define the question, documentation and material needed by the legal department or management.
04Insurers and law firms
Compensation claims
Handling a compensation claim brings together documentation, relevant rules and legal assessment. For the selected workflow step, we define the scope of analysis, drafting and review of results.
05Public administration and public institutions
Draft decisions
Drafting decisions and other legal material within a defined procedure. The sources and material underlying the draft remain identifiable. Review of the draft and responsibility for the final decision remain with people.
06Universities and research institutions
Research collaboration and licensing
Reviewing agreements on research collaboration, licensing and rights to research results. We consider contract and project documentation and the relevant legal sources. The institution’s responsible department reviews the drafts.
These examples illustrate possible uses; they are not client references or evidence of completed production deployments. We agree the scope of implementation according to the task and available components.
Your documents.Your workflow.
Material, sources and access
We connect your documents, previous matters, internal rules and databases to OLC Engine and the relevant legal sources.
We prepare material for processing with AI, organise data connections and search, and define who may access each part of the material.
Workflow, interface and review
We adapt implementation to your systems and workflows. OLC can run within an existing system’s backend; reviewing results remains part of your work.
If the task needs an interface, we can choose ,, a Word add-in tailored by agreement, or another existing or purpose-built interface.
· Public source-code beta
Components can be combined or integrated individually, including without a new interface. We agree the scope and terms of use.
How we connect material, legal sources and your systems
← Swipe horizontally to explore the illustration →
A dashed connection marks planned source ingestion. For each task, we assess the sources’ legal status, terms of use and relevance.
What we define before implementation
Integration and access
We can integrate selected OpenLegalCore components, tools and legal data collections into an organisation’s business processes, individually or in combination, and connect them to existing systems. Integration and access arrangements are tailored to the organisation’s needs, taking into account the availability and licensing terms of the selected solutions.
We agree the scope of legal sources and search, data flows, how to connect to the model provider, human review of results and responsibility for operation.
Security depends on the whole operating environment:
access controls
updates
protection of login credentials and other secrets
backups
network isolation
how the system connects to the model provider
Technical connections
Technical integration can connect datasets, document stores, relational and vector databases, and systems for preparing and searching data.
WORKING ENVIRONMENT
Legal Workspace
Legal Workspace is an option when the task needs an interface. It is awaiting MVP approval.
A legally material result is incomplete unless the system can show its authoritative source, applicable version, retrieved passage, model and provider route, stated limits and human-review status. Together, these elements form its chain of custody.
Reference model
Source layer
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 ↗ · OFFICIAL SOURCE / SUPREME COURT OF THE REPUBLIC OF SLOVENIASlovenian case lawSlovenia's authoritative national public case-law collection, published through the judiciary's official service administered by the Supreme Court of the Republic of Slovenia. It is the complete public corpus available through that service; statutory publication rules do not require every decision issued by every Slovenian court to appear.Open the official collection ↗ · controlled documents
Legislation, case law and matter documents serve different roles. Each source must retain its provenance, applicable version and access conditions. The model must connect its claims to named sources. Traceability alone does not make a matter document a legal rule or an established fact.
01 / Sources
Primary authority
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 ↗
Judicial material
OFFICIAL SOURCE / SUPREME COURT OF THE REPUBLIC OF SLOVENIASlovenian case lawSlovenia's authoritative national public case-law collection, published through the judiciary's official service administered by the Supreme Court of the Republic of Slovenia. It is the complete public corpus available through that service; statutory publication rules do not require every decision issued by every Slovenian court to appear.Open the official collection ↗
Public legal sources are acquired and prepared within the Slovenian legal foundation. Engine processes uploaded documents, including OCR when needed. Every transformation must preserve input identity, execution path and validation result.
Retrieval must return more than relevant text. It must preserve the named source collection, applicable date, source identifier, selection path and search limits. It must clearly distinguish a search with no hits from material that was never searched.
The engine orchestrates. It does not become the authority.
Engine 0.1.0 connects maintained legal sources, document processing, persistent Case Memory, analysis, strategy, legal drafting and review. It focuses on Slovenian law and remains private.
The interface is a client, not the legal AI engine.
OLC Legal Workspace is the first-party environment for Conversations and Matters, in private active development and preparing for the MVP. Legal Studio supports document work and review within Legal Workspace, independently with OLC Engine, or in your own system. Word Connector is a separate public source-only beta for legal questions and research, optionally using explicitly selected text as context; it does not edit documents. Engine can also serve an embedded workflow.
An identified person remains responsible for the final decision.
Review is a human decision, not a client capability. Review surfaces can expose output, cited material, corrections and limits; an identifiable human records the method, findings and final status.
Featured component / OpenLegalCore Word Connector/ PUBLIC BETA / SOURCE CODE · v0.1.0-beta.1
W OpenLegalCore Word Connector
Legal research without leaving the document.
Ask freely—or start with exactly what you selected.
Word Connector returns source-linked analysis beside your draft. Review the answer and its sources; nothing changes in the document without your approval.
The add-in source code is public; access to OLC Engine is not included.
Status
PUBLIC BETA
Host
WORD FOR THE WEB
Engine path
DIRECT / BETA TEST RECORD
Licence
APACHE-2.0
Document
USER-CONTROLLED
05 / ROADMAP ·
How we are developing OpenLegalCore
Engine already brings together legal method, case material and Slovenian legal sources. We are developing Legal Workspace, broadening the legal foundation and preparing to use the system in other jurisdictions.
From clarifying the task to analysis, procedural strategy and legal drafting. Engine uses case material and persistent case memory, and includes OCR, pagination and document import.
It connects a universal method of legal work with the sources and rules of a specific jurisdiction and the material of an individual case. The foundations, results and open questions of that work can be reviewed.
OLC Engine is a privately developed legal core. Licensing and terms of use are agreed individually with each partner.
Today
The Slovenian jurisdiction
Open record +Close record −
Slovenian legislation and case law already form Engine's legal foundation. We acquire, curate and regularly maintain the sources in datasets, preserving links to the original records.
For work with Slovenian law, Engine uses legislation and case law. We build this legal foundation by regularly acquiring, curating and maintaining sources. We preserve links to the original records and information about legislation's versions over time.
We prepare the acquired material for use in datasets and search. Curation includes organising texts and document metadata, preserving source references, and checking the technical consistency of the data and whether refreshes have succeeded.
The software tools are publicly available under BUSL-1.1. Partnership terms apply to access to the prepared and maintained datasets.
In development
Legal Workspace
Open record +Close record −
Conversations, matters, files and notes in a working environment connected to Engine. We are developing it for work in a personal space and collaboration among members of an organisation.
Status
in development.
We are developing Legal Workspace as an environment for conversations, matters, files and notes, and for working with Engine. It is designed for work in a personal space and collaboration among members of an organisation.
Our focus is on preparing an environment for day-to-day legal work, where an individual answer can form part of the broader work on a matter.
EU law and additional legal sources
Open record +Close record −
We plan to include EU law and the case law of the Court of Justice of the EU and the European Court of Human Rights. The expansion also includes searching the publicly available decisions and opinions of the Information Commissioner.
Planned release
November 2026.
We plan to broaden the legal foundation with European Union law and the case law of the Court of Justice of the European Union and the European Court of Human Rights. This expansion will also include searching the publicly available decisions and opinions of the Slovenian Information Commissioner.
We will connect the individual groups of sources with Engine's legal method, taking account of their origin, the appropriate version over time and their role in legal judgment.
These periods are development targets. When the releases are ready, we will also publish information about their availability and terms of use.
In testing
Other jurisdictions
Open record +Close record −
Engine's cognitive method remains the same. For other jurisdictions, we are preparing local legal sources, establishing the rules governing their use and checking the results.
Status
in testing.
Planned release
December 2026.
Engine's cognitive method remains the same, while the legal foundation is adapted to each jurisdiction. Local sources, their versions over time and the rules governing their use need to be established for each one.
These periods are development targets. When the releases are ready, we will also publish information about their availability and terms of use.
06 / GOVERNANCE ·Governance / Operating truth
Open code does not meanhidden responsibility.
OpenLegalCore begins with founder-led governance. Public discussion is welcome; product direction, access, releases and the project identity retain clear accountability.
01
Public foundation
Useful on its own.
Working software, documentation, tests, synthetic examples, evaluation tools and review methods are released only after the relevant readiness gate.
No deliberately crippled teaser repositories
02
Private incubation
Protected while incomplete.
Unfinished components, sensitive integrations and production evidence remain private until rights, limits and release conditions are resolved.
No promised opening date
01 / MODEL
Founder-led
Maintainer rights are earned through sustained judgement and trusted work.
02 / LICENCE
Component decisions
Code, data, documentation and brand rights are handled separately. Each component’s licence and access terms are stated in its own record.
03 / PRIVACY
Synthetic public data
Private legal documents, evidence packages and credentials stay outside public repositories.
04 / SECURITY
Private reporting path
Suspected vulnerabilities now have a monitored project-wide private channel. Public issue trackers must not be used for security reports.
Public code can enable inspection without proving control of the whole system. Follow versions, provenance, data sovereignty, exit and regulatory roles in legal AI.
08 / CONTRIBUTE · From public record to shared work
Build the legal infrastructurethat should exist.
Tell us what you want to achieve. We can discuss using or integrating the system, contributing expertise or development work, and partnerships or funding.
Describe the problem and how you could contribute. Code, tests, documentation, review of the legal method and knowledge of sources are good starting points. You can also contribute directly in the public repositories.
Tell us about your idea for using the system, a pilot or integration, adaptation for your organisation, or a partnership or funding opportunity. A goal and an outline of the scope are enough to begin.
Work brief / Contribution
Tell us where you can contribute.
Describe the problem, the relevant part of the system and the expertise you can bring.
■ Work brief / Received
Thank you. The work has a starting point.
Your Work Brief has been sent to OpenLegalCore. If we reply, we will use the email address you provided.
Delivery record
Path
Contribution
Part of the system
Not sure yet
Delivery
Email sent
Storage
No website database
The submission is delivered by email and is not retained in a separate website database.
Access boundaryPrivate access is scoped to agreed work. It does not create ownership, maintainer status or decision rights.
A concrete problem is enough to begin.
09 / RESPONSIBILITY · Project accountability
Responsibility has a name.
Open participation broadens the work without blurring who is accountable for project direction, releases and public–private boundaries.
FOUNDER · MAINTAINER
Rajko Majcen
Rajko Majcen is a technology founder, technical project leader and product builder with more than three decades of work across security engineering, electronic banking, telecommunications, enterprise systems, open-source infrastructure and applied AI. He founded OpenLegalCore to bring that systems experience to transparent, verifiable legal technology.