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
Local editing shell
agent-sheet is no longer the truth owner
It is the local editing shell and daemon bridge, but workspace truth belongs to workspace-substrate.
Workflow shell
sheet-git coordinates the workflow
It consumes workspace, review, sync, and runtime kernels to present repo, proposal, and origin commands.
Hosted boundary
review-host renders, review-core owns
The human-facing hosted UI is separate from the canonical hosted review store and command surface.
Kernel owners
Workspace truth
workspace-substrate
Owns local workbook entries, local change batches, origin state, and other persistent facts under `.agent-sheet`.
Repo and workflow truth
sheet-git-kernel
Owns commits, refs, workflow truth, replay runs, pull projections, and the durable model behind proposal-shaped commands.
Hosted review truth
sheet-review-core
Owns reviews, revisions, comments, deliveries, handoffs, and hosted projections.
Decision policy
git-shaped-sync-core
Owns readiness, pull decision, replay planning, and projected changeset transforms without acting like a persistence layer.
Runtime seam
univer-runtime-sdk
Owns the stable runtime contract used by shells that need to invoke workbook execution safely.
Shell surfaces
Local editing
agent-sheet
CLI shell, tool semantic kernel, daemon bridge, auth, logging, and shell-native presentation for local editing.
Git-shaped workflow
sheet-git
CLI and flow orchestration for stage, commit, proposal, hosted review publishing, fetch origin, pull origin, and push origin.
Hosted shell
review-host
HTTP routes, HTML rendering, and human-facing review interactions backed by sheet-review-core.
Runtime app
apps/univer-runner
Execution-facing app surface used to host the runtime seam in a stable way.
Story harness
qa-harness
Runs realistic end-to-end stories so the team can validate behavior across local, hosted, and remote boundaries.
Ownership matrix
| Surface | Owns | Does not own |
|---|---|---|
| agent-sheet | Local editing shell behavior, daemon control, auth, logging, presentation | Workspace truth, repo truth, hosted review truth, runtime seam ownership |
| sheet-git | Workflow orchestration across repo, review, and origin commands | Workspace persistence, hosted review store, runtime seam ownership |
| review-host | Hosted HTTP routes, HTML renderer, human-facing interactions | Hosted truth ownership itself |
| git-shaped-sync-core | Readiness and replay policy | Durable repo or workspace persistence |
| univer-runtime-sdk | Stable runtime contract | Business workflow truth |
Integration rules that keep the system stable
Rule of thumb
When ownership feels unclear, ask who has the last word on the state transition. That package or service is the owner, even if another shell triggers the action.
- agent-sheet consumes workspace-substrate instead of exporting substrate truth from its own shell surface.
- sheet-git consumes sheet-review-core through public contracts instead of reaching through old hosted internals.
- review-host should read and write hosted truth through review-core public surfaces only.
- Sync policy decides readiness. Collaboration runtime materializes and applies changesets. Those are different responsibilities.
Overview
Return to the high-level truth model before diving back into package ownership.
Terms
Use the glossary to decode proposal, review session, pull projection, and related concepts.
Previous
How work moves through the stack
The most important system behavior appears in the handoff between local editing, hosted review, and remote replay.
Next
The terms that matter
The architecture uses a tight vocabulary. Knowing which terms are durable truth and which are command language removes most confusion.