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 09 / PUBLIC BETA · v0.1.0-beta.1

OpenLegalCore Word Connector

Legal research without leaving the document.

Ask freely—or start with exactly what you selected.

OLC Engine returns source-linked analysis beside your draft. Review the answer and its sources; the document stays unchanged.

See the workflow Inspect the public source
Status
PUBLIC BETA
Host
WORD FOR THE WEB
Engine path
OLC ENGINE DIRECT · OPEN WEBUI OPTIONAL
Licence
APACHE-2.0
Document
UNCHANGED

01 / THE WORKING CONTRACT

The document remains the working surface.

Legal teams already draft, compare and review in Word. The connector adds a controlled OLC Engine research workflow beside the document: it sends only the context you choose and never edits the document automatically.

  1. 01

    ASK IN PLACE

    Question, answer and sources stay beside the draft.

  2. 02

    SEND DELIBERATELY

    Send no document text—or only the passage you select.

  3. 03

    DECIDE AFTER REVIEW

    Compare the answer with its sources; nothing is inserted into the document automatically.

02 / TWO WAYS IN → ONE REVIEW PATH

Two ways in. One source-linked answer.

Start with a standalone question, or select the exact passage that needs analysis and add your question. In both cases, the chosen context, active request, answer, sources and next action remain visible.

ENTRY ANO DOCUMENT CONTEXT

Ask a standalone legal question.

Choose No document context. Word stays open, but no document text is included in the request.

EVIDENCE 01 / NO CONTEXTENLARGE +
EVIDENCE 01B / QUESTION READYENLARGE +

OR

ENTRY BSELECTED TEXT

Send only the passage that matters.

Select the passage, choose Selected text and add your question. The selection is captured when you start the search; Cancel remains available while it runs.

EVIDENCE 02 / SELECT TEXTENLARGE +
EVIDENCE 03 / START SEARCHENLARGE +

BOTH ROUTES RETURN

SHARED RESULTREVIEW & CONTINUE

Compare the answer with its sources.

Review inline references and the source list in the task pane beside Word. Copy answer, Refine question and New search continue the work without editing the document automatically.

EVIDENCE 04 / REVIEW ANSWERENLARGE +
EVIDENCE 05 / CONTINUEENLARGE +

03 / SYSTEM PLACEMENT

Two OLC components can be enough.

The direct path joins the familiar working surface to the legal capability. Open WebUI is available as an optional mediation layer only where an operator already needs it for access, sessions or model routing.

Word Connector → OLC Engine

The Word Connector system contractThe primary route runs from Word Connector through the same-origin gateway directly to OLC Engine. An optional mediated route branches after the gateway through Open WebUI and rejoins before OLC Engine.WORKING SURFACEWord ConnectorSAME-ORIGIN GATEWAYLEGAL CAPABILITYOLC Engine01PRIMARY / MINIMAL OLC SYSTEM02OPTIONAL / MEDIATED PATHOPEN WEBUI06DOCUMENTED AS STATE 06IN THE WORKFLOW GALLERYThe Word Connector system contractThe primary route runs from Word Connector through the same-origin gateway directly to OLC Engine. An optional branch passes through Open WebUI before rejoining the primary route.WORKING SURFACEWord ConnectorSAME-ORIGIN GATEWAY01PRIMARY /MINIMAL OLCSYSTEM02OPTIONAL /MEDIATEDPATHOPEN WEBUI06DOCUMENTED AS STATE 06IN THE WORKFLOW GALLERYLEGAL CAPABILITYOLC Engine
  1. Word Connector → OLC Engine
  2. Word Connector → Open WebUI → OLC Engine

These two OLC components can be the complete visible system for a bounded Word workflow: the connector provides the working surface; OLC Engine provides the legal capability.

Choose this path only where Open WebUI already belongs to the operator’s environment. It mediates access, sessions or model routing; it neither replaces OLC Engine nor becomes a connector dependency.

NEXT SURFACE / OLC OFFICE SUITE

The same visible contract is planned for LibreOffice.

A separately designed LibreOffice connector is intended to preserve the same pattern: an explicit question, bounded document context, source-linked OLC Engine output and no silent document change. This is a direction—not an available implementation or delivery commitment.

04 / CONTROL BOUNDARIES

Useful because the limits stay visible.

The connector is a focused research surface, not an invisible document agent. Each boundary answers a practical question: what leaves Word, what can change, who operates the service and where legal verification remains.

  1. 01

    WHAT LEAVES WORD?

    Nothing—or the exact selection.

    No document context sends no Word content. Selected text sends only the passage captured after an explicit search action; the question stays separate.

  2. 02

    WHAT CHANGES?

    Analysis beside Word, not mutation inside it.

    The beta has no Apply, rewrite, redline or automatic insertion action. Copy answer uses the clipboard; it does not edit the document.

  3. 03

    WHO OPERATES IT?

    The operator owns the service boundary.

    Identity, hosting, credentials, legal corpora, retention, logging and incident response belong to the chosen deployment.

  4. 04

    WHAT STILL NEEDS REVIEW?

    Sources remain the verification point.

    Compatibility does not prove corpus completeness or legal correctness. Material propositions, sources and applicable versions still require professional verification.

05 / PUBLIC BETA

Public source. Explicit deployment choices.

The Apache-2.0 repository publishes the task pane, tests, gateway contract and operating guidance. A working deployment still requires OLC Engine, authorised legal-source access, identity, hosting, security and retention choices.

Version
0.1.0-beta.1
Verified host
WORD FOR THE WEB
Untested hosts
WORD FOR WINDOWS · WORD FOR MAC
Verified
2026-09-07

EVALUATION / INTEGRATION / PARTNERSHIP

Bring OLC to the Word workflow your organisation already uses.

Discuss a bounded pilot, backend integration or operator-controlled deployment. The first conversation needs no confidential documents or credentials.

Microsoft and Word are trademarks of the Microsoft group of companies. Their use here identifies the supported host environment and does not imply sponsorship or endorsement.

RELEASE EVIDENCE

Microsoft Word for the web with OpenLegalCore connected to OLC Engine and No document context selected.

01 / 7