{"resolved":true,"match_type":"uuid","source_type":"original_book","book_id":"24410bf1-91f1-4e6b-9613-e64f0132d341","title":"The Stack On Software and Sovereignty","author":null,"edition":null,"publisher":null,"year":null,"isbn":"9780262029575","requested_by":"printed_page","book":{"source_type":"original_book","book_id":"24410bf1-91f1-4e6b-9613-e64f0132d341","id":"24410bf1-91f1-4e6b-9613-e64f0132d341","uuid":"24410bf1-91f1-4e6b-9613-e64f0132d341","title":"The Stack On Software and Sovereignty","normalized_title":"thestackonsoftwareandsovereignty","author":null,"edition":null,"publisher":null,"year":null,"isbn":"9780262029575","isbns":["9780262029575"],"parsed":true,"ai_readable":true,"document_type":"book","page_count":517,"navigation_url":"https://workshop.closeclaw.top/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341","title_url":"https://workshop.closeclaw.top/ai/title/The%20Stack%20On%20Software%20and%20Sovereignty","fixed_page_url_template":"https://workshop.closeclaw.top/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341/page/{printed_page}","path_api_url_template":"https://workshop.closeclaw.top/api/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341/page/{printed_page}","read_url":"https://workshop.closeclaw.top/api/ai/read/24410bf1-91f1-4e6b-9613-e64f0132d341","page_url":"https://workshop.closeclaw.top/api/ai/books/24410bf1-91f1-4e6b-9613-e64f0132d341/page","search_url":"https://workshop.closeclaw.top/api/ai/books/24410bf1-91f1-4e6b-9613-e64f0132d341/search"},"page":{"printed_page":313,"pdf_page":327,"physical_index":327,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"82371345fd04eb7b1a56e52614e6a43b6fe8a7f26560e7fe936b356379361b51"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"The more valuable point he makes (almost offhandedly) is one that does not require the geographic region of Silicon Valley to redraw lines on the map as such. “ That ’ s the thing about exit is: you can take as much or as little of it as you want. You don ’ t have to actually go and get your own island; you can do the equivalent of dual-booting or telecommuting. You can opt out, exit at whatever level [emphasis mine] you prefer. ” Especially if we take “ level ” to correspond strongly or weakly with the layers of The Stack, he is correct but perhaps not entirely aware of the cascading implications of this observation. As I discussed at length above, different Users may initiate columns up and down The Stack from many different positions and will be interpolated by the geoscopic interests of different Interfaces, will make use of what those interests are able to Address, will be situated within the interfacial envelopes of a given City, variously interiorizing and exteriorizing his location, will be enrolled by one or many competing Cloud platforms and supporting energy systems of varying interoperability. Different Users will have different columns available and unavailable to them, by definition, according to the determinant strength of one of more governing layers activated. The City layers of Pyongyang and Palo Alto will curtail or enable such very different possibilities for the other layers in The Stack that the City layer may have final leverage over the others. Or, in a perfectly walled garden, the platform coherence of the Cloud layer may be so closed and perfected that the Interface, Address, and User layers, are decided within a very small margin of variance. That is, for any real column up and down The Stack, there is a range between the strong incorporation of the sovereign operations of all layers together into complete vertical systems and the strong modularity of the layers into separate and counterprogrammable components. That range is not equally distributed to all Users everywhere, and the most important variations may be possible for some Users but not for others, and so exit is never available equally to and from all platform Users.\n\nThe Stack to Come\n\n313","previous_page":312,"next_page":314}