The March of Code: When Infrastructure Becomes Empire

The same infrastructures that scaled commerce are now marching in lockstep as instruments of power. This poster is a mirror for the boardroom: when code becomes empire, accountability must follow. Publish contracts. Audit the cloud. Rebuild the commons.
The March of Code: When Infrastructure Becomes Empire

The code that built the world is burning us — and it’s time the boardroom took responsibility

When software stopped being an instrument and became infrastructure, we all cheered. We built tools to connect people, accelerate science, and scale commerce. But what happens when that same infrastructure is repurposed to help plan, speed or hide violence at industrial scale? The Gaza catastrophe has made what many feared undeniable: the commercial tech stack — the cloud, the models, the maps, the telemetry — can be (and is being) applied to operations that cost human lives.

We must be crystal clear: this is not a conspiracy theory. Open-source autopilots have been linked to lethal drone strikes on state targets. Cloud and AI partnerships with defence organisations are not theoretical either — they are large, documented contracts underpinning logistics, targeting pipelines and operational decision systems.

The moral contagion has a vector: permissive code, permissive procurement, and permissive boardroom thinking. Code licensed without ethical guardrails becomes a tool that any actor — state or corporate — can weaponise. That’s not an accident; it’s a design choice baked into decades of “open” norms and commercial incentives. The result is a commons that can be harvested to harm. The ethical response is overdue.

Executives: the mirror you’re avoiding shows this pattern clearly. In the past, employee and public backlash forced re-examination — remember the Project Maven protests and the broader debate over tech’s role in defence? Those moments showed the limits of warm PR and abstract ethics statements. Surface commitments don’t cut it anymore; scrutiny will.

So what must happen now? Here’s a practical, non-violent roadmap—demanded in public, audited in private, enforced in law:

  1. Full transparency of defence & government contracts. Boards should publish an annual, independently audited register of all contracts and pilots with security, intelligence, and defence organisations — the counterfactual being secrecy that permits plausible deniability. (Procurement disclosure is not charity; it’s accountability.)

  2. Adopt enforceable ethical licensing & usage controls. Move projects and corporate contributions toward licences that forbid human-rights-abusive uses (ethical source / Hippocratic style licences) where feasible, and implement contractual use restrictions for proprietary components. Developers must have mechanisms to limit misuse.

  3. Independent forensics & red-teams on product misuse. Allocate budget to continuous, third-party audits that model how systems can be repurposed for surveillance, targeting, or forced displacement — then fix the systemic vulnerabilities they reveal.

  4. Procurement reform and human-rights gating. No cloud certification or AI procurement without a human-rights assessment signed off at C-suite and board level. If the assessment flags potential abuses, procurement must pause until mitigations exist.

  5. Developer & maintainer reparations. The communities whose labour built these stacks deserve a seat at the table: funding, governance roles, and revenue shares for projects whose code is used by large corporations and governments.

  6. Whistleblower protections and safe exit channels. Employees who raise credible concerns about misuse must be protected, and their claims independently investigated.

  7. Build resilient, decentralised alternatives. Support OSS projects designed with governance and access controls that prevent stealth weaponisation: auditable, accountable, and privacy-preserving systems (and the public funding to scale them).

This is a program of constructive rupture, not anarchic destruction. When I say “tear down the walls,” I mean dismantle the secrecy, the perverse incentives, and the governance architectures that allow code to be pointed at civilians and called “utility.” The goal is to replace capture with accountability — to make the technology ecosystem safe for the human beings it’s supposed to serve.

If you run a company that’s profiting from opacity, this is your clear call to action: publish your contracts, open your audits, fund transitions to safe licence terms, and stop treating ethics as marketing. If you’re an investor, demand these fixes before you write the cheque. If you’re a developer, refuse the forgetfulness: insist on usage covenants and governance seats for communities.

We can do this without violence. We must do this without violence. The alternative — surrendering public infrastructure and public life to proprietary, unaccountable control — is itself a slow, technical form of dispossession. Executives will be judged by history for whether they acted when they still could.

— Steven Joseph

#TechEthics #AuditTheCloud #OpenSourceResponsibility #HumanRights #ResponsibleProcurement #DamageBDD


No comments yet.