OS:Warszawa
The most important discoveries happen not when we arrive somewhere, but when we realise we've been somewhere all along. Warsaw revisited through infrastructure metaphor.
The most important discoveries happen not when we arrive somewhere, but when we realise we've been somewhere all along. First arrival is installation. Return is recognition of version changes - both in the city's code and your own. What worked in 2025 might not work in 2026. Protocols need patching. Dependencies may have changed. This investigation will document the return process itself as methodology. How do you observe a city you've already systematically documented? What's left to investigate when you've walked the zones? Answer: you're no longer documenting the city - you're documenting your own integration process as it runs a second time with different parameters.
The operating system metaphor clarifies what return actually means. You're not nostalgically revisiting a place you loved. You're running a regression test - checking whether your existing code still works in the current environment. Sometimes it does. Sometimes it breaks in interesting ways. Sometimes the city's updates break backward compatibility with your own protocols. This investigation will make explicit what happens during any return visit: reconciling cached assumptions with current reality. The second residency methodology turns this reconciliation process into systematic documentation rather than vague sentiment about how places "change" or "stay the same."
Known code running in familiar environment should be boring. That's the point. When it's not boring - when the routine fails, when the protocol throws an error, when the familiar path produces unexpected results - that's where the investigation focuses. Changes in city infrastructure. Updates to my own operating assumptions. Conflicts between ymy cached version and current reality. The second Warsaw residency isn't about discovering new zones or finding hidden neighbourhoods. It's about understanding what changes and what remains constant when you run the same investigative code twice. Some processes are stable. Some have been patched. Some no longer compile at all.
