Operations Room Hangar

From titipi
Revision as of 17:03, 13 July 2023 by FS (talk | contribs) (→‎TITiPI)
Jump to navigation Jump to search

An Operations Room at Hangar

During 4 days, a group of people gathered around an object of study in Hangar, Barcelona to do

Fundamentals

Operators

  • Aggeliki (TITiPI, researcher)
  • Anna (Hangar, director)
  • Antonio (Hangar, head of research)
  • Donald (pre-recorded contribution)
  • Femke (TITiPI, co-director)
  • Helen (TITiPI, co-director)
  • Jara (TITiPI, Hangar InfraMaintainance Fellow)
  • Jorge (Hangar, web-developer)
  • Laila (Hangar, administrator)
  • Matteo (Hangar, system-administrator)
  • Miriyam (TITiPI, co-director)
  • Seda (TITiPI, co-director) (pre-recorded contribution)

Guest: Jaume (external accountant)

Documentation

[Antonio adds]

Hangar

[include diagram?]

LaaS

SaaS, Software as a Service, is a business model where an organisation develops a software product and makes it available to customers online. The software is hosted in the cloud and the user accesses it remotely for a subscription (monthly, yearly, etc.). The so-called “cloud” is built on deeply extractive, exploitative and exclusionary log(isti)cs. In political-aesthetic terms, it is a regime that prescribes what is feasible and thinkable, flattens and standardizes everyday experience, rigidifies the material conditions of possibility in the sharing of experience with the technological, and imposes logistically mediated conditions of subjectivity and coexistence.

The relational logistics of the category of life (Life as a Service, LaaS) needs to be studied in a broader framework. Despite the necropolitical mandate of the cloud, and against the cloud but from within, what would be the practices and positionalities that could make room for ontological and epistemic disobedience, providing palliative care towards its eventual abolition?

More on LaaS: https://hangar.org/en/fellowship/laas-life-as-a-service-de-jara-rocha-primer-fellowship-hangar/

TITiPI

(Miriyam)

TITiPI brings together activists, artists, engineers and theorists (Seda Gürses). Together with different kinds of communities we articulate and re-imagine what computational technologies in the “public interest” and activate/militate be around these actualities (“in-the-making”) where possible. In terms of activism, epistemology and our main paradigms, we are inspired by knowledge, praxis, legacies, archives and tools from feminisms, queer theory, computation, intersectionality, anti-coloniality, disability studies, historical materialism and artistic practice to generate new vocabularies and methodologies. Sense of urgency – sneaky moments – an important layer in our analysis related to capitalist/imperial temporalities. E.g. Lebanon infrastructural destruction the port explosion+financial collapse. But also seen as governments have started to adopt Big Tech framings for crisis, such as considering its populations through the prism of scale, collapsing contexts instead of exploring approaches that serve different publics, and linear technocratic solutions for complex problems. This process accelerated in the last few years when immunity certificates or COVID passport apps where introduced, and lockdowns increased dependency on digital platforms.

Public institutions are cast as inefficient, backward and “bureaucratic” in contrast with the suave agile modes of start-ups and tech consultancies. In the process, it digital bureaucracy had to be deployed on a massive scale to enforce policies, from managing risky exemptions for so-called front line workers, to extending border control into everyday environments. It paved the way for handing over core operations to global consultancy firms, in fact govtech business is booming and process of outsourcing government policy to consultancy companies has been going on for a while. But, the current connection between consultancy companies such as Deloitte, Mckinsey and Accenture and cloud services is relatively new. Companies almost full-circle, closing the loop: they set the conditions; manage computational infrastructure, develop software algorithms: and deliver the tools for their execution, whilst auditing said services. The shift is typically framed as a technical matter, which effects only internal operations, but as the racist and capitalist extractivist cases show, the automation of internal operations are social in fundamental ways, and have crucial external consequences. In one of our projects Decolonial Operations, the way tech/infrastructures change the what, who, and how of public institutions. These algorithms being developed by commercial companies means that the mode of production of digital transformation is not part of the public policy sphere but delegated to the capitalist sphere of profit accumulation. Three (political/ethical) anchors Computational infrastructures as part of operations: Dialectical approach (mediation between social relations and existing contradictions), but in terms of temporality we distinguish between past, present and future as a conceptual necessity to see how operational systems are manifested across different timespans related to tech-development. A crucial aspect of operations is scale, such meta systems can be used to enforce policies across populations in a decontextualized and paradoxical – both coercion/consent, latent/manifest - manner. To overhaul the system requires radical change also because public policy is co-opted by profit. Making this cooptation and transformation concrete is part of the need to hold accountable those parties, ministers, groups that are responsible for these transformational operations.

Decolonial/Anti-colonial: Racial capitalism. Allows to ask how is this mapped onto a long history of thinking and scholarship that categorizes people, and on to existing logics and power relations. Historicizing creates space to rethink existing approaches and reconnect differential struggles. Deliberate inequalities as colonial inheritance. Walter Rodney describes infrastructural under-development as a key aspect of dependency. Especially in terms of climate and energy we see that the separate spacing of big-tech and decolonial politics is artificial. Abolition, e.g., the undoing a racist system is not a mythical moment where everything collapses at once. You need to start brick by bricks and starts now. This auditing could be part of that.

Insurgent intersectional: Possibilities and challenges for praxis/pedagogy both on a subjective level and who are our partners, who are the activists or engineers or historians or political economists who can do the critical analysis of these cases with us, from different angles to think through the multi-layered answers to these complex problems. We need to build coalitions to bring all those different strings together. But our objective is liberation-based change and thus we employ intersectional not as a conceptual or individual (subjectivity) way. We amplify its radical roots 1. collective 2. a tool rather than the aim. And so future oriented/insurgent.

Concretely:

How to bring this together concretely? for instance relate this to the link between profiling and cloud computation as a manifestation of "digital transformation". The racist algorithms used by national and local nation states to detect welfare fraud, “automated fraud prediction”. We draw a connection between core operations of public institutions shifting to cloud services, making legible the rise of consultancy companies specialised in technology for governments ("govtech") and the increase in algorithmic policy administration. But can governments still be and be held responsible for their policies once they have handed skills and expertise over to consultancies and tech companies?

These operational shifts have epistemological/cultural consequences. What happens when digital bureaucracies [abstracted as cloud’] can claim to act as arbiters of social conflicts and disparities. In the meantime, these software and policy processes systematically reduce possibilities for confronting inequalities collectively. So, in due course, instead of addressing the causes of oppression and systemic racism, sites for contestation and public encounters are at once replaced by technocratic processes and individualised. This critique of atomised/singular polity is important. The techniques are replicable from one context to the next, from one ministry to the next, and from the present to the future.

Finally, abolition = the oppressive systems we identify confront the marginalised [racialised, economic or sexual minorities] oppressed but are eventually be rolled out beyond oppressed populations.

Operations Room

[picture?]


An Operations Room is a situation designed to interrogate the impact of a specific computational infrastructure and its implementations on the operations of a (public) institution, organisation, or collective. Participants with divergent interests, and expertise across scales are invited to study an infrastructure that matters to them and to the (public) institution which deploys it. An Operations Room uses a mix of transdisciplinary methods such as code-inspection, decolonial critical discourse analysis, dependency mapping, creative experiments, and interface analysis. Participants can include engineers, organizers, activists, designers, labourers, accountants, policy people and other users. Together they utilize the prism of "operations" to arrive at an integrated understanding of how a technology manages operations, through what a technology currently does, might do in the future and how it does so. Examples of technologies that could be the subject of an Operations Room: a videoconferencing platform for higher education; a keycard system for managing transactions in refugee camps; a mobile health management tool; a protocol for registering and communicating vaccination status. An Operations Room lasts up to a day and could take place on-line but is ideally physically located in a space relevant to the institution that deploys the technology. Great care is taken in curating the group of participants and mix of methods, preparatory research, selecting tools for documentation, scenography of the room and overall hosting of the situation. An Operations Room can be proposed by an organisation, a concerned individual or follow from a Drop-in Clinic; an outcome of an Operations Room might be a bugreport or a proposal for further participatory research.


[more from Helen's intro]

[picture?]

Documentation system: audios, pics, pads, keywords and timestamps

Sage

[screenshot?]

[Femke]

Materials in the Room

[maybe put a picture?]

Books, pamphlets and references

[maybe put a picture?]

Other

[picture?]

  • Grid (Operations Room team)
  • 2 of 18 A0 posters, digitally printed and originally displayed on the streets of Dundee. Designed by Cristina Cochior, Batool Desouky for NEoN in the context of the Counter Cloud Action Plan (November 2022). https://neondigitalarts.com/from-cloud-to-crowd-poster-campaign/
  • So-and-sovereignty diagram, The Institute for Technology in the Public Interest x Martino Morandi (2023) You can find its current iteration here: https://titipi.org/diag/so-and-sovereignty.pdf
  • "la vida es demasiado corta como para andarse con hojas de cálculo" ("life is too short for spreadsheets", Sage corporate slogan), 17 index cards, TITiPI (2023)
  • image: Patent Edith Clarke
  • image: Microsoft Operations Room
  • image: Marie Neurath
  • image: Invoicing printing cliches, Barcelona 1970's (?)

Activation

Day 1

  • 14:30 Open doors to the Room, loose encounter with the Operations Room and its materials
  • 15:00 Fundamentals
    • Welcome (Antonio, Matteo, Jorge, Laila, Femke, Helen, Aggeliki, Miriyam, Jara, Anna)
    • Documentation system
    • Hangar and InfraMaintainance
    • Life as a Service (LaaS)
    • TITiPI, The Cloud Regime
    • Operations Room as a method
    • Why SAGE on-line accounting system with recorded insert
  • 17:30 Break
  • 18:00 Laila's tour through Sage; discussion and articulations of questions
  • 19:00 End

Day 2

Day 3

  • 10:00 Collective diagramming session: budgetting potentials, cracks, inventions and/or constrains
  • 11:30 Break
  • 12:00 Input guest: Jaume, Hangar's accountant
  • 13:00 Budget reading: closing the room for/with Hangar's team

Day 4 + Day 5: continued internal worksession

Retrieved from "https://titipi.org/wiki/index.php?title=Operations_Room_Hangar&oldid=3000"