field notes codename
12 notes filed under FLINT, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.
A small service here does two jobs on one timer. It restates, every cycle, that its node is still the one in charge, because the record it maintains expires if it goes quiet. It also tells a human when that status changes. For a long time…
elsewhere
Each codename is a project. The theme is the class of problem the note is about — the same theme recurs across projects, which is usually the interesting part.