Top line: content freshness should be checked like any other production surface. KENSAI uses file timestamps, generated indexes, mirror parity, and route checks to turn publishing drift into evidence.
The hidden failure mode
Static publishing can look healthy while the public surface is stale. A new article may exist in one directory but not another, an index may omit a fresh slug, or a route may return an old generated page. Without a direct check, teams end up reporting intent instead of proof.
That is why KENSAI treats freshness as a measurable control. The check starts with the filesystem, then follows the artifact through generated JSON, overview pages, mirrors, and live HTTP responses.
The evidence chain
- Timestamp proof: same-day HTML files exist for the required publishing window.
- Index proof: generated JSON includes the slug, title, date, excerpt, and category.
- Overview proof: discovery pages include the posts that readers and crawlers should find.
- Mirror proof: project and served roots match after regeneration and sync.
Operational takeaway
Freshness checks are small, but they prevent a large class of quiet publishing failures. They also give operators a crisp way to distinguish “content was written” from “content is discoverable.”
For KENSAI, that proof trail is the difference between a content task and an auditable release artifact.