KENSAI Research: Freshness Proof Is a Cross-Index Contract

Top line: freshness is reliable only when every public index tells the same story. KENSAI treats daily blog coverage as a cross-index contract between HTML source files, JSON feeds, mirrors, and overview pages.

The failure mode

Most publishing failures are not dramatic. They are mismatches: two HTML files exist, but the app feed still shows yesterday; the root JSON is fixed, but a legacy mirror remains stale; the overview page rebuilds, but the heartbeat check reads a different path.

Those mismatches are operational debt. They make dashboards look healthy while the path a reader or crawler uses is still behind. A freshness contract reduces that debt by defining which surfaces must agree before the work is counted.

What a contract includes

• Source truth: HTML files carry the same date and metadata that the indexes expose.
• Root feed: the primary JSON index lists the same-day posts first.
• Mirror feed: compatibility paths receive the same rebuilt JSON, not a hand-maintained approximation.
• Generated view: the overview HTML is regenerated from the feed instead of edited by hand.

Research takeaway

A cross-index freshness check is small, but the pattern scales. Any system with generated artifacts needs independent surfaces to agree: report files and report lists, scans and scan history, status pages and source metrics. Agreement is the evidence.