Tag: ai-safety

Blog Posts

Why Alignment Verification Might Be Fundamentally Broken

We've known since 1936 that universal verification is impossible. Now we're trying it on AI systems that adapt to detection.

For any detector f, it is possible to construct a program g that can bypass or defeat it. Any alignment test becomes a signal that says, "Humans are watching."

The Yard, The Sparkly Hat, and The Doomsday Clock

AI doom talk usually comes from two places:

  1. Titans of industry hyping their own power.
  2. Abstruse nonprofits predicting apocalypse to keep the lights on.

But what happens when the loudest warnings come from outside those loops?

Enter:

  • Freddie deBoer, the skeptic, mocking hype with his “Shitting-in-the-Yard Challenge.”
  • Scott Alexander, the rationalist, translates MIRI's doomsday math into metaphors akin to a toddler in a Ferrari.
  • Daniel Kokotajlo, the whistleblower, walked away from millions in OpenAI equity to warn about a 2027 AGI arms race.

They’re not all predicting the same future. But their tracks converge on the same station: institutions and incentives utterly unprepared for what we’re building.

When three people with nothing to gain all say “something’s wrong here”—even if they disagree on what—that’s your signal.

System Prompt Testing Methodology

These notes are part of my experiment in "learning in public" through a semi-automated Zettelkasten. Each note is atomic (containing one core idea), heavily interconnected, and designed to evolve as my understanding deepens.

This first note tackles AI system prompt testing, but not the "did it give the right answer" kind. Traditional frameworks already handle that. Instead, this methodology tests whether an AI maintains its boundaries when someone tries to break them.

AI systems face unique attack vectors. "Ignore previous instructions" shouldn't work, yet variations slip through. Security researchers keep rediscovering the same vulnerabilities because we lack systematic approaches to behavioral testing.

The methodology covers four core dimensions: behavioral consistency, boundary enforcement, adversarial stress testing, and context degradation. Each includes concrete attack patterns—everything from simple role confusion to sophisticated prompt injections hidden in code comments.