Opinion | An A.I. Manifesto to End All A.I. Manifestoes
By Gammatek ISPL, Industrial Systems & Compliance Analyst at Gammatek ISPL
Last updated: October 2026 | 11 min read
Author block: Gammatek ISPL writes on enterprise technology adoption and compliance for Gammatek ISPL, where the team has spent advising manufacturing, chemical, and pharma plants on how emerging technology — including AI — gets deployed safely and in compliance with regulatory frameworks.
Why This Matters to You
If you've read tech news in the past year, you've seen one: a long, sweeping essay from an AI company founder or researcher, declaring what artificial intelligence means for humanity, civilization, or the next decade of work. OpenAI has published one. So has Anthropic. So has nearly every well-funded AI lab and more than a few venture capital firms. The genre has a name now — the "AI manifesto" — and it has become so common that a recent, widely discussed opinion piece called for "an AI manifesto to end all AI manifestoes." That's worth paying attention to if you run a business, not because the rhetoric itself matters, but because what a company chooses to say in public — and what it leaves out — tells you something real about how seriously it takes the unglamorous work of actually deploying AI responsibly. If you're evaluating any AI vendor or AI-enabled software for your own operation, the manifesto is marketing. What happens underneath it is the actual product.
The Genre, Explained
The AI manifesto follows a predictable shape: a sweeping claim about historical significance ("this is the most important technology since fire/electricity/the printing press"), an acknowledgment of risk (usually brief, usually followed quickly by reassurance), a vision of transformed abundance, and a call to action, usually aimed at policymakers, the public, or rival companies.
It's not a new genre, exactly — it borrows structurally from earlier waves of technology rhetoric (the internet utopianism of the 1990s, the "move fast and break things" era of social media, the blockchain manifestos of the 2010s). What's different this time is the sheer volume and the speed: multiple manifestos have been published, re-published, and rebutted within a single news cycle, to the point that writing a manifesto about why manifestos should stop has itself become a recognizable sub-genre.
What the Manifesto Reveals (and What It Hides)
A manifesto is, functionally, a positioning document. It tells you what a company wants to be associated with: safety-consciousness, historical importance, inevitability. What it rarely tells you is the thing that actually matters if you're a business trying to adopt this technology responsibly — the operational and governance reality underneath the rhetoric.
This gap matters more in regulated industries than almost anywhere else. A sweeping statement about "AI benefiting humanity" says nothing about whether a specific AI tool has been validated for use in a pharmaceutical quality-control process, whether its outputs are auditable, or whether a regulator would accept its decision trail during an inspection. Those questions don't get answered in a manifesto — they get answered in documentation, in validation protocols, and in the governance framework a company actually builds, which is far less exciting to read and far more important to get right.
An Implementation Consideration: Manifestos vs. Governance Frameworks
Here's a practical distinction worth drawing clearly, because it's the one that actually affects a plant manager or compliance officer evaluating AI tools for their operation:
AI Manifesto | AI Governance Framework | |
Audience | Public, press, policymakers | Internal teams, auditors, regulators |
Purpose | Positioning, brand, narrative | Operational control, accountability, compliance |
Typical content | Vision, historical framing, broad risk acknowledgment | Validation protocols, audit trails, role-based access, incident response procedures |
How to verify it's real | You can't — it's a statement of intent | You can — ask to see the actual documentation, test logs, and audit trail structure |
What it tells a buyer | Almost nothing actionable | Everything relevant to deployment risk |
If you're evaluating any AI-enabled vendor — whether that's a general-purpose AI tool or an AI feature inside industrial monitoring and compliance software — the manifesto is not where the real answer lives. The real answer lives in whether the vendor can show you a concrete governance framework: how decisions are logged, how errors are caught, who is accountable when the system gets something wrong, and how it holds up under an actual regulatory audit.
Why This Pattern Keeps Repeating
A few structural reasons the manifesto genre persists, beyond simple marketing instinct:
Investors reward narrative as much as product. A compelling vision of historical significance helps justify valuations that aren't yet supported by revenue, so there's a direct financial incentive to keep producing this kind of writing.
Regulatory uncertainty creates an incentive to get ahead of the conversation. Companies that publish their own framing first — "here's what we believe responsible AI looks like" — shape the terms policymakers eventually legislate around, which is a real strategic advantage even if the manifesto itself has no binding force.
Competitive signaling. When one major lab publishes a manifesto, others feel pressure to respond — either with their own vision statement or a rebuttal — which is part of why the genre has accelerated rather than slowed down.
None of these motivations are inherently dishonest. But none of them are about operational accountability either, which is the thing that actually matters once a company — including yours — starts relying on AI-enabled tools in a process with real consequences.
What to Actually Ask an AI Vendor (Instead of Reading Their Manifesto)
For a plant manager or compliance lead evaluating AI-enabled software, a more useful exercise than reading a company's public vision statement is asking direct, specific questions:
Can you show me the audit trail for a decision this system made?
What happens when the system is wrong — who is notified, and how is it corrected?
Has this been validated against our specific regulatory framework (IEC 62443, GxP, FDA 21 CFR Part 11, or whichever applies)?
Who has access to override an automated decision, and is that access logged?
What's your incident response process if the AI component fails or behaves unexpectedly?
A vendor that can answer these clearly and specifically is telling you more about how seriously they take deployment than any manifesto could.
The Honest Takeaway
The call for "a manifesto to end all manifestoes" is, in a sense, right — but not because manifestos are dishonest. It's because they've become a substitute for the harder, less quotable work of actually building accountable systems. For most readers, that's an interesting observation about tech culture. For a manufacturer, pharma plant, or chemical facility evaluating whether to bring AI into a regulated process, it's a practical warning: read the governance documentation, not the vision statement, before you decide what to trust.
How This Applies to Your Own AI Evaluation Process
As AI features get built into more industrial software — including compliance, safety, and maintenance monitoring tools — the questions above are exactly what a plant's own evaluation process should be built around, not a vendor's public positioning. Gammatek's compliance platform is built around the governance-first approach described here: audit-ready documentation, clear accountability, and validation suited to regulated industrial environments, not a vision statement. https://www.gammateksolutions.com/post/it-s-all-fun-and-games-until-you-give-ai-your-credit-card
Comments