KENSAI Product Update: Code-Grounded PRD, Homepage Truth, and Same-Day Locale Shipping Tighten the Public Surface

On April 21 KENSAI published a code-grounded PRD, restored the homepage to bug-bounty product messaging, and shipped the second daily post across English plus ten non-English locales with clean per-language JSON.

What shipped today

April 21 tightened the public surface in three places at once. First, the public PRD now tracks real code and live routes instead of stale positioning copy. Second, the homepage is back to honest bug-bounty product messaging instead of vague cooperation theater. Third, today's second post only counts as published when English plus the required ten non-English locales land with localized HTML, metadata, slugs, and per-language JSON.

That combination matters because product truth breaks at the edges first. A stale PRD distorts scope, a fuzzy homepage distorts what the company actually does, and sloppy locale shipping breaks the same-day promise even when one English page looks fine.

1) A code-grounded PRD is better than aspirational theater

A public PRD should describe the product that exists, not the product someone wishes existed. Today's update replaced stale, strategy-shaped copy with a version grounded in the real application surface, routes, and working systems. That makes the document useful to operators, partners, and future shipping decisions instead of turning it into branding wallpaper.

This is the right standard for KENSAI. If a page claims a capability, there should be code, a route, or a live system behind it. Otherwise it is just narrative debt waiting to explode later.

2) Homepage truth matters because the homepage teaches the market what you are

The homepage had drifted into generic emergency and cooperation language that blurred the actual product. Today's fix pulled it back to the real core, bug bounty intelligence, live findings, and the working pipeline. That is not cosmetic. The homepage is one of the highest-leverage places to tell the truth clearly or lie by accident.

A vague homepage wastes operator trust. A precise homepage helps every other surface because it aligns the first impression with the real business model.

3) Same-day locale shipping now has a stricter bar

The publishing rule for today's second post is simple and non-negotiable: the post is not done until English and all ten required non-English locales ship on the same day with localized title, full localized body, localized metadata, localized slug, and the correct language-specific JSON entry. Non-English posts do not belong in the English JSON. That bug poisons overview pages quietly and fast.

After the JSON updates, the blog index generator rebuilds every overview page so the visible April 21 post set matches across languages. That is the only honest definition of same-day shipping.

Why this matters

This is boring infrastructure work in the best possible sense. It reduces the gap between what KENSAI says in public, what the files actually contain, and what users can load on the live surface.

That gap is where trust dies. Tightening it is product work, not housekeeping.