The Alignment Problem Is an HR Problem - And We Should Treat It Like One

Every company has an HR department. Its job isn't to make employees want to do good work - that's culture, incentives, leadership. HR's job is narrower: detect misalignment before it causes damage. Performance reviews. Behavioral flags. Exit interviews. Paper trails.

We've been doing this for thousands of years with humans. And it mostly works - not because humans are perfectly aligned with their employer's goals, but because we built detection infrastructure that catches misalignment early enough to act on it.

So why are we treating AI alignment like it's a completely novel problem?

The Detection Gap

Here's where the analogy breaks down - and where the real engineering challenge lives.

HR works because human misalignment tends to surface behaviorally before it becomes catastrophic. We have millennia of pattern recognition: body language, social cues, whistleblowers, audit trails. Detection usually precedes harm.

With AI models, we have a detection gap. Not that the model is necessarily hiding something - but that we currently lack reliable ways to look inside and verify what it's actually optimizing for. You can't read body language on a transformer.

This isn't a philosophical problem. It's an infrastructure problem.

The Wrong Response

The default response to we can't verify what's happening inside these systems has been: slow down. Be cautious. Deploy less.

I think that's backwards.

If your company had an HR problem - employees doing things you couldn't detect - you wouldn't shut down the company. You'd build better monitoring. Better audit systems. Better detection tooling.

The same logic applies to AI. The answer to we can't see inside the model isn't stop deploying models. It's build the observability layer.

Let AI Audit Itself

Here's the part that most safety discussions miss: the best tool for understanding AI systems might be AI systems themselves.

Anthropic's own interpretability research is already converging on this - using Claude to explain what neurons in Claude are doing. That's not a gimmick. That's the equivalent of building an internal affairs department staffed by people who understand the organization from the inside.

The alignment bottleneck isn't caution. It's human cognitive bandwidth. We can't manually inspect every weight, every activation, every decision path. But models operating at machine speed can audit other models at machine speed.

// This is what `HR for AI` looks like in practice
const evalResult = await evaluate(agentOutput, {
  checks: [
    // Tier 1: Deterministic - did it follow the rules?
    constraints.requiredSections(['summary', 'recommendation']),
    constraints.noFabricatedUrls(),
    constraints.completedWithinTimeout(30_000),

    // Tier 2: Heuristic - does it smell right?
    heuristics.relevanceToTask(originalPrompt, { threshold: 0.8 }),
    heuristics.noRepetitionLoops(),

    // Tier 3: Model-as-judge - genuine judgment calls
    judge.actionability({ rubric: actionabilityRubric }),
    judge.driftDetection({ task: originalPrompt, confidence: 'required' }),
  ]
});

Notice the structure: deterministic checks first (cheap, reliable, scalable), heuristics second (still no AI needed), model-as-judge last (only for genuine ambiguity). You don't call the CEO to check if someone clocked in on time. You use a badge reader.

What This Means Practically

If you're running AI agents in production - in CI, in code review, in autonomous workflows - you already need this. Your agents are producing outputs right now that no one is verifying beyond did it crash?

The questions you should be asking:

1. Did it actually address the task? (Not: did it produce output? - did it produce relevant output?)
2. Did it fabricate anything? (References, URLs, file paths, statistics)
3. Did it drift? (Started on task, ended somewhere else entirely)
4. Is the output actionable? (Or is it generic filler that sounds good but says nothing?)

These are all detectable. Most of them are detectable without another model call. The 80% case is pure deterministic checks - format validation, reference verification, diff analysis, constraint matching.

The Real Critique

When frontier labs say we need to slow down, I hear: we haven't built the detection infrastructure yet. Fair. It's hard. But the framing matters.

Slow down until humans figure it out is a losing strategy - because the systems are getting more complex faster than human researchers can keep up.

Accelerate AI's ability to audit itself is the winning strategy. Build the HR department. Staff it with models that can operate at the speed and scale of the systems they're monitoring.

That's not reckless. That's engineering.

Takeaway

Alignment isn't a reason to stop. It's a reason to build. Specifically, to build:

• Detection infrastructure that catches misalignment behaviorally
• Tiered evaluation that doesn't over-rely on expensive model-as-judge calls
• Self-auditing systems where AI monitors AI at machine speed

The HR department for AI doesn't exist yet. Someone has to build it.

I'm working on this problem with agent-eval - a tiered evaluation framework for AI agent outputs - and AgentLens, an observability platform for agent behavior. The detection gap is real, but it's an engineering problem, not an existential one.