# blog/ — the long-form devlog 📓

Narrative notes on building L'Armada — the *documentary* layer above the terse
[`armada/tasks/`](../armada/tasks/) Captain's Log. Where the task log answers
"what landed," these answer **"what happened, what surprised us, what we learned."**
Raw material for blog posts, devlog videos, and talk material.

## Convention

- One file per story beat / session arc: `NN-slug.md` (`NN` = zero-padded sequence).
- Write it like you'd want to *read* it months later with no memory of the work:
  the problem, the approach, the **surprise**, the numbers, the fix.
- Honesty over polish. A finding that *didn't* work (stem-aware lost to whole-mix
  on n=5) is better blog material than a clean win — it shows the reasoning.
- Concrete artifacts: commit hashes, file paths, measured numbers, screenshots.
- These are drafts/notes, not published posts — they capture the *texture* while
  it's fresh. Editing into final posts happens later.

## Index

- [01 — The machine that learned it was too warm](01-emotion-calibration.md) —
  building a CLAP emotion engine, discovering it over-feels "playful," and
  teaching it humility with affine calibration.
