{"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":11,"pdf_page":29,"physical_index":29,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"2bc1bd9f9c62f565e5fe86f989c8ecff521db5cc63ce7663b27f75f244a71cd0"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"The architecture of this model treats these overlapping layers, claims, and networks not as exceptions to the normal rule but as the basis of an emergent order. The Stack, as examined here, comprises six interdependent layers: Earth, Cloud, City, Address, Interface, User. Each is considered on its own terms and as a dependent layer within a larger architecture, and each is drafted from the superimposed image of the geographic and computational machines we now inhabit and the ones we might yet make. Each layer is understood as a unique technology capable of generating its own kinds of integral accidents, which, perhaps counterintuitively, may ultimately bind that larger architecture into a more stable order. These layers are not just computational. As much as it is made from computational forms (multiplexed fiber-optic cables, data centers, databases, systems standards and protocols, urban-scale networks, embedded systems, universal addressing tables), The Stack is also composed of social, human, and concrete forces (energy sources, gestures, effects, self-interested maneuvers, dashboards, cities and streets, rooms and buildings, physical and virtual envelopes, empathies and enemies). These hard and soft systems intermingle and swap roles, some becoming relatively “ harder ” or “ softer ” according to seemingly arcane conditions. <sup>9</sup> The Stack comes from both equilibrium and emergence, one oscillating into the other in undeciphered and unaccounted-for rhythms, stabilizing and destabilizing the same component for sometimes mismatched purposes. What is its state condition, and, literally for governance, what kind of machine that is a state does it provide for?\n\nIntroduction\n\n11","previous_page":10,"next_page":12}