The same documents that ship with the source, readable without leaving the site.
Every page here is generated at build time from the Markdown in the repository, so the site and the source can never drift apart.
01pages
Start with the features, then read the reasoning behind them.
- Every feature
Features
The complete surface of Skriuw: the editor, journal, tasks, search, history, import and export, sync, AI, and the mobile app.
- How it is built
Architecture
The Rust domain layer, SQLite as canonical storage, the operation pipeline, and the boundaries that keep navigation off the disk.
- What we promise
Performance contract
The interaction budgets Skriuw is held to, how each one is measured, and what happens to a change that breaks them.
02decision records
Recent architecture decisions.
- ADR-00622026-11-11
The on-screen keyboard sends keystrokes to the focused editor
People who cannot use a physical keyboard, or who work on a tablet or with a pointer or eye tracker, need a way to type into the note.
- ADR-00612026-11-09
Early workspace read and a deferred raw editor chunk
Desktop startup measured on a 582-note workspace spends its time in the web view, not in Rust: the shell's setup takes about 7 ms.
- ADR-00602026-11-06
A bounded note renders its viewport first and grows its window when idle
ADR-0020 renders a note above 192 top-level blocks as a 192-block window of one canonical document.
- ADR-00592026-11-06
One native sync runtime, platforms supply the IO
skriuw-sync owned the cycle, the coordinator thread and the HTTP status rules, but each platform drove a session its own way: