Files
typewriter/docs
Julien Calixte e967773bd6 feat(editor): add v0.5 file palette (Cmd-P) with fuzzy match
Cmd-P opens a modal transient palette over the writing column: a bare
fuzzy-search input, the ranked file list, and the selected row in reverse
video. A pure host-testable fuzzy_score (subsequence + word-boundary and
consecutive-run bonuses) ranks results; an in-core MRU floats recently
opened files first and is shared with :e (both route through open_path).
The host feeds the file list once at boot (enumerate_files over /sd/repo
and /sd/local). Ctrl-n/Ctrl-p navigate the list; Enter opens via the same
park/evict path as :e; Esc closes.

Ctrl-n/Ctrl-p also become down/up line motions in Normal and View (vim
CTRL-N/CTRL-P, count-aware), which is why the palette opener is Cmd-P
alone. No `>` prefix on the file input — `>` is reserved for the command
palette (slice 4).

112 editor + 28 keymap tests; the no-git firmware binary builds clean.
2026-07-12 00:11:33 +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.
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.