field notes codename
12 notes filed under TROUPE, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.
The decision that shaped everything else was to give each autonomous worker its own system container rather than a process inside a shared host. A process boundary is cheap, and it is also porous. A crew of workers that can see each other's…
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.