NS-2: uniform/evolving protocols that persist and grow

Protocols that survive iteration. Not one-off solutions — living conventions that accumulate learning over time and don’t get abandoned when a session ends.

NS-3: clear critical-path infrastructure today

Specifically: forgejo, the HDD, backups and cataloguing of spaces when cleanup phases hit, clear protocols that just work and are understood for any repetitive or persistent convention, cycle, etc., the llm wiki.

NS-4: organizational etiquette

So things like FJ, wikis, HDD dirs don’t become tangled messes. Naming conventions, directory hygiene, clean separation — the physical structure of the work should never become the problem.

NS-5: collaborative protocol

When a docker is offered via SSH or Tailscale for a shared surface to work — how is it configured? How is it clear in terms of how it needs to be worked on? How are collaborators invited? How do all agents from all collaborators understand how to operate?