Pattern
Promote findings
When a log holds something worth keeping, write down what is still true, once, where the next reader will look.
When to use it
A run has turned up a fact about the code, or a result, that will still matter after the run is over. A log records one run with everything that happened in it, so the finding belongs in a README, a header or a collection instead.
Steps
- Read the log for what is still true.
- Write that down once, in your own words, where the next reader will look: a README, a header, or a doc in a collection.
- Cite the ids, and let the log expire.
Copy, or distill
# copies every run, noise included
$ cp .memex/logs/playtest/*.md docs/playtests/
# writes down the one thing still true
# crates/namer/README.md
Hashes are stable across runs; see NAME-001.