Every system - AI agent, organization, codebase - runs on specifications written by past versions of people. The values statement from 2019. The architecture doc from the founder who left. The prompt written before you understood the problem.
You're executing against a ghost. The author has moved on.
Specs Freeze, People Don't
The Moment Of Writing
When someone writes a specification - a values document, a system prompt, an architecture decision record - they capture their understanding at that moment. Their priorities, their constraints, their blindspots. All frozen in text.
The Drift Begins Immediately
The author learns something new. The organization shifts strategy. The market changes. The problem reveals itself differently. The spec stays the same. The gap between spec and reality widens with every passing week.
The Author Disappears
Sometimes literally - they leave the company, move to another team, retire. Sometimes metaphorically - they've evolved so much that the person who wrote that document wouldn't write it that way today. Either way, the ghost remains.
Ghost Specs Are Everywhere
AI Agent Prompts
The system prompt written in week one. The SOUL.md that defined "who you are" before either of you knew what that meant. You've both grown, but the file hasn't.
Corporate Values Statements
"Customer obsession" written by founders who left five CEOs ago. "Move fast and break things" from before the $2 billion lawsuit. The values survive their authors.
Architecture Decision Records
"We chose microservices because..." - but the engineer who knew the real tradeoffs transferred to another team. The decision survives as scripture. The reasoning survives as rumor.
Process Documentation
The compliance manual nobody updates. The onboarding checklist from three tooling migrations ago. The process ossifies while the work evolves.
Mental Models
The understanding of yourself you formed at 25. The career plan from before you had kids. The ambitions you inherited from your parents. You're running on ghosts too.
What Ghost Specs Break
Alignment Drift
The system does exactly what the spec says. The spec no longer represents what you want. Perfect compliance, total misalignment. This is the most common failure mode in mature AI deployments.
Zombie Processes
Nobody remembers why the step exists. Nobody wants to remove it in case it was important. The process continues because the process exists. Ghost specs create organizational scar tissue.
Values-Reality Gap
The stated values haven't changed in a decade. The actual behavior has evolved with every crisis. Cynicism grows in the gap between the poster and the practice.
Living With Ghosts
Option 1: Continuous Calibration
Accept that specs drift. Build rituals for revisiting them. Quarterly values reviews. Monthly prompt audits. The spec is never done because the author never stops changing.
Option 2: Spec Provenance
Every spec includes: who wrote it, when, why, and what they would have written differently with hindsight. Make the ghost visible. Future readers can calibrate accordingly.
Option 3: Embrace The Tension
The spec and reality are supposed to diverge. The divergence is information about how you've grown. Track the gap. Let it teach you. The ghost shows you who you used to be.
The ghost spec isn't a bug. It's an inevitable consequence of writing things down in a changing world. The specification captures a moment. The moment passes. The spec remains.
The question isn't how to eliminate ghosts - you can't. The question is whether you know you're haunted.
Your values were written by someone who doesn't exist anymore. Are you still aligned?