{"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":318,"pdf_page":332,"physical_index":332,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"2177d94d3e172a2b6d62fc90d754d12f21025b4b310efdc30d4ab20fbadb0350"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"As the following section on the City layer-to-come will explore, we are not lacking utopian visions; we are instead drowning in their surplus. It is increasingly unlikely that for each and every state, each layer of The Stack would somehow resolve inside of each national boundary, which would then, as similar units, cooperate in a universal and global constitutional federal order. “ The right of the state ” to “ control the Internet inside its borders ” is very difficult to enforce when its borders are on the Internet and are themselves, in one of several ways, outside their own terrestrial geography. Today this option is nevertheless floated by regimes (some if not most authoritarian) hoping to fix themselves against the tides, withdrawing into national islands, while disallowing entrance and exit to their own Users and citizens (the state monopoly turns ugliest when its ability to cohere citizens is challenged and undermined). We assume that not only is there no conventionally cosmopolitan resolution forthcoming around the bend but perhaps that there cannot be, and should not be. Isn ’ t the “ state condition ” of software and sovereignty going forward one in which each of us is already claimed by multiple jurisdictions at the same time, and in which we already manage multiple formal claims on our social identities and economic agency? Geodesign must draw on that entanglement, not problematize it as a “ contradiction ” to be solved. The outgoing Secretary of State Clinton was right in this regard: the Cloud polities to come — State into Cloud platforms and platforms into states — do need new architectures. <sup>41</sup>\n\n318\n\nThe Stack to Come","previous_page":317,"next_page":319}