Skip to content
ORIX
Coming SoonMacProductivity

ORIX Docs

A native word processor for the Mac, engine first

Overview

ORIX Docs is being built to be a native word processor for macOS, aimed at writing, academic work and structured documents. Its architecture is a thin SwiftUI and AppKit application on top of an engine package whose targets do not import SwiftUI, so every engine can be built and tested from the command line.

Today only the engine exists. The committed code covers the document model, a numbering resolver and a defensive ZIP container. Further engines are in progress in the working tree: editing and tracked changes, Word document import, a native file container, Markdown and plain text, bibliography parsing, document comparison and a template library. The app folders are still empty and there is no icon.

Page layout and the document auditor have only just been started; PDF publishing, automation and the command-line tool are planned in the architecture but not written yet. This page describes the state of the code today.

Key features

  • 01

    Document model

    Documents are values made of blocks, paragraphs, runs and inline objects, with tables, page setup, notes, comments and bibliography data, plus named styles with inheritance. Engine code, committed; there is no interface yet.

  • 02

    Numbering in one pass

    A resolver computes list labels, heading numbers, caption sequences, note numbers and citation order in a single pass over the document. Labels are computed, never stored in the text. Engine code, committed.

  • 03

    Defensive ZIP container

    A minimal ZIP reader and writer (stored and deflate) underpins the Word and native containers and treats its input as hostile. Engine code, committed with its tests.

  • 04

    Editing engine with tracked changes

    Text operations on a document and a selection, table editing, accepting and rejecting tracked changes, comments, and find and replace are written as engine code with test files. In progress, not yet committed.

  • 05

    Word document import

    A WordprocessingML importer reads content, styles, tables, pictures and tracked changes, and reports what it cannot carry over as warnings. Engine code in progress; export is not written.

  • 06

    Document comparison

    A comparison engine aligns blocks, diffs paragraphs word by word, compares tables and produces a change list and a report. Engine code with a test file; in progress, not yet committed.

  • 07

    Bibliography parsing

    Parsers for BibTeX, BibLaTeX and RIS map entries to CSL types and decode LaTeX markup in field values. Engine code in progress.

  • 08

    Template library

    Sixteen templates are defined in code with English and French names, from a blank document to an academic paper, a thesis, an invoice and a newsletter. Engine code with a test file; no interface presents them yet.

A closer look

An engine that never imports the interface

The architecture document describes eleven engine targets, from the document model to automation, none of which imports SwiftUI. The package has no network access anywhere, and its only third-party dependency is SwiftMath for math typesetting.

Importers that never drop content silently

A stated convention of the project is that importers treat input as hostile and report everything they cannot carry over as a format warning. The same types are shared by every importer and exporter.

A native format that is the model

The native .orixdoc file is a single ZIP container holding a manifest with SHA-256 checksums and the JSON-encoded model, with schema migrations applied before decoding. Word documents remain an import and export format.

Decisions recorded with their evidence

The project includes a technology evaluation and a competitive analysis that label each statement by how it was checked. The competitive analysis states that no competitor was tested hands-on and that ORIX Docs has no measured results yet.

Technical specifications

Platform
Mac (macOS)
Minimum OS
macOS 15.0
Architectures
Not verified yet
Current version
Not released
Release date
Not released
Download size
Not verified yet
Permissions
None
Offline
Not applicable yet: there is no app. By design the engine package has no network access anywhere.
Languages
Not verified yet
Dependencies
One third-party dependency: SwiftMath, for math typesetting. The engine package declares macOS 15 as its minimum.
Source
Not published

Downloads

macOS disk image

No release yet. Nothing has been signed, notarized or published, and there is no download.

Coming Soon

Not on the App Store yet.

Release history

No release has been recorded yet.

Privacy

There is no app yet. The engine package is designed without any network access.

  • No network access anywhere in the engine package, as stated in the architecture document.

Verification status

Not yet validated on a physical device

Unreleased, and no app exists. The only commit (2026-11-21) covers the document model, the numbering resolver and the ZIP container, with 5 container tests. Uncommitted test files for editing, review, comparison and templates are present in the working tree. The Word import test corpus is empty. No test was run to prepare this page.

Most engines are uncommitted work in progress and change from hour to hour. Layout and audit have only first source files; automation and the command-line tool are placeholders. There is no project file, app code, icon or screenshot in the project.

Questions

When will it be available?

No date has been announced. The app is unreleased: there is no build to download and no public repository.

Can I try it?

No. Only the engine package exists; the app folders are empty and there is no build or download.

Will it open Word documents?

Word import and export are part of the planned architecture. An importer is being written as engine code; export is not written yet, and nothing has been tested against real-world files in the repository.

What is planned but not written?

The application itself, PDF publishing, and automation with the command-line tool. Page layout and the document auditor have only just been started.

What is the native file format?

A single-file ZIP container with the extension .orixdoc, holding a manifest, checksums and the document model as JSON.

See the full catalog
  • Coming Soon

    ORIX Sheet

    A native macOS spreadsheet in early development: the calculation engine exists, the app does not yet.

    MacProductivity
  • ORIX Scan iconBeta

    ORIX Scan

    Scan paper into clean, searchable PDFs: capture, enhancement, text recognition and export all run on your iPhone or iPad.

    iPhoneiPadProductivityv1.0.0
  • ORIX Monitor iconIn Development

    ORIX Monitor

    A native macOS system monitor with local history, alerts and reports, in development.

    MacSystem