Files
typewriter/docs
Julien Calixte c535864ee7 feat(editor): add .typoena.toml prefs and palette settings (v0.5 slice 4)
Git-tracked editor preferences read at boot and toggled live on-device:

- Prefs type (line-based TOML parse/serialize, no crate on xtensa) held on
  Editor; firmware reads /sd/repo/.typoena.toml before the first render and
  falls back to per-key defaults. Keys: save_on_idle, format_on_save,
  line_numbers (bool) + auto_sync (string, schema/default only until v0.7).
- line_numbers applied live (gutter_cols -> 0 when off).
- Palette > command mode toggles the three bools; the list stays open so
  several flip in one visit, and :settings opens it directly. Each toggle
  applies live and queues Effect::SavePrefs (host atomic-writes the file,
  which rides the next :sync).
- save_on_idle honoured host-side as a silent, unformatted idle auto-save.
- to_toml is newline-free; save_path now appends exactly one terminator
  unconditionally so buffers round-trip byte-for-byte (trailing blanks kept).
- Firmware 0.4.0 -> 0.5.0; new docs/typoena-toml.md reference. Also refreshes
  the slice-3 macroplan status (delete fix was confirmed on device).
2026-07-12 01:48:10 +02:00
..

Docs

The design record for Typoena — the decisions, specs, and bench write-ups behind the writing appliance. Start with the ADRs for the load-bearing choices, or the v0.1 specs for what the first release actually does.

Project overview: ../README.md.

Decisions & specs

Doc What's in it
adr.md Architecture Decision Records — the load-bearing technical choices and why.
v0.1-mvp-product.md v0.1 product design — boot, type one file, Ctrl-S to save, Ctrl-G to publish.
v0.1-mvp-technical.md v0.1 technical design — single Rust binary on esp-idf-rs, modules, threads, bring-up order.
macroplan.md Version-by-version plan; each release is a usable artifact, not a checkpoint.
typoena-toml.md .typoena.toml reference — the git-tracked editor preferences (auto-save, format-on-save, line numbers, auto-sync).
hardware.md Part choices for the bench build and the rationale behind them.

Quality method

Doc What's in it
qfd.md Quality Function Deployment — turns user-facing requirements into technical HOWs; §3 is the filled 14 WHATs × 14 HOWs House of Quality.
quality-house-empty.md The House chassis, blank — for re-scoring from scratch.

Bench work

Area What's in it
spikes.md Rendering & UX spikes — display/UX risks proved outside the hardware stack.
postmortems/ Bring-up debugging write-ups: what broke, the root cause, and the decisions that came out of it.
notes/ Longer-form essays on the thinking behind specific choices — e.g. where the ~16 s cold :sync goes.
tradeoff-curves/ Cost-vs-knob curves behind chosen defaults — energy, latency, memory.