Most DevOps conversations focus on one question:
Should CI and CD be separated?
That matters—but I think it misses the deeper issue.
Modern pipelines are good at answering:
- Can this code build?
- Do the tests pass?
- Can it be deployed?
But they rarely answer a more important question:
Should this system state exist at all?
This is where many pipelines fail quietly.
A deployment can be technically successful while still introducing:
- semantic inconsistencies
- invalid state transitions
- ambiguous rollback paths
In other words:
«Passing tests does not guarantee system truth.»
So I’ve been exploring a different architecture:
CI → Semantic Validation → CD
Where:
- CI handles build and test
- Semantic Validation enforces meaning and state integrity
- SKOS for controlled semantics
- RDF for graph projection
- SPARQL for rule enforcement
- CD promotes only validated system states
This changes deployment from:
shipping code → promoting validated reality
Benefits:
- Clear state traceability
- Deterministic rollback
- Stronger governance over production changes
Rollback becomes simple:
Replay a known validated state.
Not rebuild-and-hope.
I believe the next evolution of DevOps is not just faster pipelines.
It’s pipelines that can formally answer:
What is allowed to exist in production?
Curious how others think about this.
Do your current pipelines validate only code, or system meaning too?
