Understand the stack before you evaluate the APIs.

These pages turn the internal architecture notes behind Univer Runner into a readable system guide for engineers, architects, and technical decision makers.

The focus is not SDK API reference. It is the operating model behind local editing, Git-shaped review, hosted review truth, and remote workbook replay.

Start with the overview

Recommended paths

First Look

Read the one-page architecture summary, then jump into the system context.

Review Workflow

Follow how local work becomes hosted review, then origin replay.

System Boundaries

Use the subsystem guide when you need to know which surface owns which responsibility.

Pages

Architecture Overview

The architecture in one pass

Univer Runner is an offline-first spreadsheet collaboration stack that joins local editing, Git-shaped workflow, hosted review, and remote workbook sync.

6 min read

System Context

Where the system sits

Univer Runner is not one application. It is a coordinated set of local shells, hosted surfaces, and remote authority boundaries.

7 min read

Core Workflows

How work moves through the stack

The most important system behavior appears in the handoff between local editing, hosted review, and remote replay.

8 min read

Subsystem Boundaries

Which subsystem owns what

The architecture is easiest to operate when you keep shell responsibilities separate from kernel ownership and avoid reading command names as architecture.

8 min read

Glossary

The terms that matter

The architecture uses a tight vocabulary. Knowing which terms are durable truth and which are command language removes most confusion.

5 min read