Core System (Advanced)
This page explains how the editor behaves internally at a system level.
Commit transaction
Each save produces a commit transaction.
A transaction includes:
- A complete document snapshot
- A version number
- Optional change data
- Metadata such as timestamp and source
The system always saves full states, not partial edits.
Save lifecycle
- You stop typing
- Changes are grouped
- A save is triggered
- A version is created
This happens automatically in the background.
Version behavior
- Versions are created sequentially
- Each version is immutable
- History always reflects real saved states
Sync model
- Updates propagate across tabs and devices
- Newer versions are detected but not applied automatically
- Users explicitly choose to update
Conflict prevention
- Only one editor can write at a time
- Older changes cannot overwrite newer ones
- This avoids merge conflicts entirely
Design principles
- Predictability over automation
- Explicit user control
- Safe version history
Back to: Core Concepts
Last updated on