KENSAI Product Update: Canonical Path Truth and Root-Mirror Sync Close the Daily Publish Gap

KENSAI tightened April 19 publishing by treating the OpenClaw project tree as canonical, rebuilding locale blog indexes from HTML, and syncing the served root mirror so same-day post counts match what users can actually load.

What shipped today

Today’s work removed a boring but dangerous ambiguity from the publishing pipeline. The OpenClaw project tree already held the real authoring state, but the public site also depended on a served root mirror. That meant a post could exist in the canonical repo while still missing from the surface users and crawlers actually hit.

April 19 tightened that loop. Publishing now means writing the real localized HTML, rebuilding each language index from those HTML files, and syncing the served mirror so the public count reflects reality instead of intent.

1) Canonical path truth matters because teams debug what they believe is live

When multiple trees exist, people naturally inspect whichever one they changed last. That becomes a trap when the live site serves another mirror. Making the authoring path explicit and syncing outward in one direction cuts off that confusion.

A correct file in the wrong place is still the wrong reality. Canonical-path discipline is not paperwork, it is what stops teams from debugging ghosts.

2) HTML remains the source of truth and per-language JSON follows it

The safe contract did not change: HTML is authoritative, JSON is derived. Each language post belongs only in its own JSON index, and those indexes should be rebuilt from the localized HTML rather than hand-maintained as a parallel source of truth.

That matters because overview pages, blog listings, and locale routes all depend on those derived indexes. If JSON drifts away from the rendered files, the site quietly stops telling the truth.

3) Same-day publishing now ends only when the served surface matches English

The practical target for April 19 was simple: ensure the second daily product post exists in English plus all ten required non-English locales on the same day. The stronger version of that target is what shipped, the served surfaces now have to agree with English before the day is considered done.

That makes same-day publishing measurable. If one locale is missing, if one JSON index is polluted, or if one overview lags behind, the release is incomplete no matter how good the draft looked in git.

Why this matters

Small publishing ambiguities compound fast. A stale mirror breaks freshness, a stale index breaks discoverability, and mismatched locale overviews break the same-day promise. Tightening all three together is the kind of boring reliability that makes fast multilingual publishing sustainable.

That is the point of today’s product work: less theater, more verifiable truth.