//07 Tokenization · Series: The Token Economy
The prompt is the product
Treating the system prompt as a first-class artifact, versioned, tested, and owned by the team that ships it.
A small reframe
For most teams shipping agentic features, the model is a commodity. The prompt is not. The prompt encodes the product decision.
Treat it like code
- Version it. A
system.mdin the repo beats a Notion doc that nobody finds. - Test it. Snapshot the outputs you care about and diff them on every change.
- Review it. Prompt changes deserve the same scrutiny as schema migrations.
The team boundary problem
When the prompt is owned by “whoever wrote it last,” quality regresses every release. Pick an owner the same way you’d pick an owner for the auth layer.
“We don’t ship the model. We ship the prompt around the model.”
What this looks like in practice
A small prompts/ directory, a CI step that runs eval cases, and a weekly review of the worst 20 outputs. That’s it. Most of the work is showing up to look at what your system actually said.