{"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":144,"pdf_page":160,"physical_index":160,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"2e3ffb75d0861f16dad68c8be8320e5092074c670c5669bdd98f34cbf8994713"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"Just as the overlaid geographies of the Cloud layer are generative of its most interesting future developments (and this geometric dissensus should be recognized as such), the same superimpositions will give structure to the pathways and limits of our own individual lives. In relation to software and sovereignty, each person, each plot of land, each addressable object, will be claimed by multiple incompatible jurisdictional authorities at the same time. Each such authority is in its way complete and “ universal ” within the limited domain that it can see and move, even if it is invisible to the others. The management of this multiplicity therefore works not in spite of overlapping claims, but because of their claims of exclusivity. We will see that finally, it is the mutual exclusivity and closure between delimited sovereign spaces that allows multiple universal claims to coexist in different dimensions, even as they claim the same person or site as a subject. Perhaps, as we will discuss in the following chapters, the most critical secondary accidents of the Cloud layer are those that automate the architecture of exclusion between territorial planes according to violent hierarchies of absorption and extraction. It may also be our hope, however, that the same operations bring with them their own generative accidents, ones that introduce unexpected and uncontrollable forms of spatial access and practical mobility for those otherwise curtailed by its intended predicaments. That is, the flip side of producing platform User identity when none is wanted is that it is also produced for Users regardless of how other systems may otherwise try to exclude them. By their normalization of exceptional reversibility, urban and infrastructural scale interfaces that once kept them out now let them in, automating sovereignty where states had decided alienation. To consider this in more detail, we ’ ll have to examine how the Cloud drives and animates the next layer up in The Stack, the one inside of which we all live: the City layer.\n\n144\n\nCloud Layer","previous_page":143,"next_page":145}