KENSAI Product Update: Index Rebuild Receipts Keep English Discovery Aligned With What Actually Shipped

Publishing is not complete until the article, the indexes, and the public discovery surface all point to the same truth.

Discovery is part of the release, not an afterthought

KENSAI is tightening the English publishing loop around a simple rule: if a post exists as shipped HTML but cannot be found through the indexes users and crawlers rely on, the release is still incomplete. Discovery has to move at the same speed as publication.

Rebuilding from HTML keeps the receipt chain honest

That is why index regeneration matters. When the English JSON is rebuilt from real article files, KENSAI gets a cleaner receipt chain from canonical content to derived metadata. The listing surface stops guessing what should be live and starts reflecting what actually shipped.

One slug should survive creation, indexing, and serving

The operational test is deliberately narrow: the same slug should appear in the article HTML, top-level English JSON, blog JSON, generated overview, and live route. If any one of those layers disagrees, freshness may look healthy internally while public discovery is already drifting.

Why this matters for security-ops trust

KENSAI treats public artifacts like security evidence because users judge reliability by what they can verify. A visible, reachable, correctly indexed post tells a better truth than a quiet file sitting in the repo. In security operations, that difference matters because trust erodes at the seams between state changes and public proof.