{"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":60,"pdf_page":78,"physical_index":78,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"835f461dffcc1042948c600b859cbf1ef18e668d4300e9c2377d2c78ba1935e0"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"in the communication between parts and components and freely available to be reprogrammed for specific implementations. Taken as a whole, TRON was considered at one point “ the most popular operating system in the world. ” <sup>28</sup> Its success, however, has been limited by the insularity of the Japanese technical ecology, and the contiguity, coherency, and delimitation of the Japanese state system. <sup>29</sup> The ultimate boundary of its walled garden would prove to be as unambiguous as an island ’ s border, and so the growth of TRON was both enabled and curtailed by Japan ’ s Garapagosu-ka or “ Galapagos syndrome. ”\n\nSakamura ’ s stack was constituent and curatorial; Beer ’ s was constitutive and generative. Beer ’ s model posited a nested series of socioeconomic scales, from worker to nation, through which regulated information would be reported, analyzed, and governed. Sakamura ’ s model distributes operations among widely dispersed components sharing data directly or indirectly for separate uses (e.g., industrial, civic, interpersonal) and so lubricating intermodal communication between people and people, people and things, and things and things. Beer ’ s and Sakamura ’ s visions are asymptotic. Both sought to design a platform infrastructure that would integrate a national society by integrating its material economies into a master computational system, but each is animated by a different conception of that task. Beer ’ s assignment was to help engineer a new nation into being through cybernetics, and so the key diagrams of his stack depict the socioeconomic scales that would come to participate through that system. For Sakamura ’ s Japan, the program of his stack is to intensify a national and cultural equilibrium already established, and so his images depict not a new social order (as Japan ’ s organic stability could be presumed) but the technical network layers that would be made to serve it. Beer ’ s diagram was of the macrosocial emergent effect of platform sovereignties, and Sakamura ’ s was the inverse, a technical harmonization of a social foundation. The constitutive design imagined the social and the cultural as an effect of the technical intervention, and the constituent design imagined the technical as a function of the social and cultural, and so here, both sides of software as language and software as technology dichotomy are exemplified and mirrored. For The Stack, the essential forces of the generative and the regulatory, equilibrium and emergence, constitutive and constituent force, remain equally foundational for one another. The Stack freezes, radicalizes, and reinforces models of governance and macroeconomics at the same time as it dismantles them, builds geographies above and below them, and undermines their ability to reproduce themselves. Sometimes it accomplishes one by doing the other.\n\nThe ongoing design of The Stack is for an architecture that is equally technical and conceptual, drawn by both its diffuse instrumentality and its physicalized abstractions. It is well suited to reflect even politico-theological aspirations and can easily synthesize an ideal liturgy of preferred signals and echo them back at specific Users (as discussed in the Interfaces chapter), even as its ability to absorb and revalue new content (toward inflation or deflation) is programmed to be agnostic and omnivorous as strategy dictates. As we conceive possible futures for The Stack platform, in what way might the generative aspiration of Cybersin do more work for more Users than the curatorial aspiration of TRON, or vice versa? As ideal types, TRON is designed to optimize coherent divisions, whereas Cybersin introduces communication across the boundaries of scale. Cybersin focuses on the flow and valuation of goods and actions taken, and TRON on the embedded intelligence of infrastructure and equipment. Cybersin seeks to enroll all actors in the economy into its ongoing planning and evolution, while TRON seeks to allow steering authority a more transparent chain of command. Beer and Sakamura would likely agree, however, that any platform architecture will succeed not through the premeditated ingenuity of its original schemes that will always prove too brittle, but through how it is taught to accommodate and validate unforeseeable new programs, and to do so as simply as possible.\n\n60\n\nPlatform and Stack, Model and Machine","previous_page":59,"next_page":61}