Software specifications and their implementations tend to drift apart over time. A specification is written once; the implementation is built, maintained, and modified separately — and the two slowly diverge. This gap is a routine source of costly failures, compliance issues, and audit findings, not just a documentation nuisance.
TRIEL is an open specification language that treats specification-to-implementation translation as the point where correctness evidence should be generated — not recovered afterward through separate testing or review.
What it looks like
Here's the actual hello_triel.triel from the repository — not a simplified stand-in:
SPECIFICATION hello_triel VERSION 1.0.0
