glossary · term
Context Spine
A versioned specification that lives in the repository and travels with the work through every agent run. It carries intent from product discussion through planning, generation, testing, and operations, so downstream people and agents can act without inventing missing meaning. It gets reviewed in pull requests like any other production artifact.
in practice
How I use the term
I introduced the term in April 2026 while describing how AI tools sprawl across a delivery pipeline. Several systems were generating overlapping artifacts from partial context, and nothing carried the governing intent from one stage to the next. The Context Spine is the artifact that does.
A spine holds the minimum a downstream person or agent needs: the problem statement, acceptance criteria, constraints, interfaces, and non-goals. Model output varies from run to run, so the durable control is intent precise enough that a deviation is easy to detect and reject.
The name matters less than the function. At organizational scale the same argument becomes a platform question, because trusted context is something a platform should provide.
in the essays · 5
Where it shows up
- The Agentic SDLC: Uniting the AI Tool Sprawl
Where the term starts: the artifact every layer transition needs.
- The Spec Is the Product
What the spec holds, and why it outlasts the code.
- The Frame Is the Bottleneck
The spine as the way to make smuggled intelligence reusable and legible.
- Workflow.ts: When the Code Runs the Agent, Not the Other Way Around
A spine used as the contract inside a coded workflow.
- Context Is a Platform Capability Now
The same argument at organizational scale.
see: spec-driven development · agentic SDLC · context engineering