From content planning to verified publishing

KernelWake is SlateMoth’s second commercial product, being developed for brand content teams, creators and MCNs working across domestic and international channels. The aim is to connect a content brief, authorized media, platform-specific versions, review and publishing evidence in one workflow.

The work starts with content the team owns or is authorized to use. A useful result must fit the intended audience and destination, preserve the brand’s requirements and leave the team able to understand what happened.

The planned workflow brings together briefs, captions, media preparation and optional image or video generation. People review the content, destination accounts, timing and spending before an approved publishing action proceeds. Changes should return the affected work for review.

The local workbench currently supports campaign drafts, per-platform captions, version-bound content review and content-plan exports. That content review is not authorization to publish, and the exported plans are not executable publishing jobs.

The initial targets are Xiaohongshu, Douyin, Kuaishou, Bilibili, WeChat Channels, Instagram, TikTok and Facebook. These are integration targets, not a list of connected services. All eight still require platform integration and the relevant account authorization.

Availability will depend on each platform, account, region and permitted action. A missing connection must be visible to the team; it cannot be replaced with a simulated success message.

A submitted upload, a post awaiting moderation and a publicly available post are different outcomes. The intended workflow keeps evidence for the actual state. When evidence is unavailable, the result remains unconfirmed.

A timeout should trigger investigation, not blind reposting. KernelWake’s engineering foundation tests approval changes, duplicate dispatch prevention and recovery from uncertain results. Local test demonstrations do not prove live platform support.

The product direction separates workflow charges from image and video API usage, with explicit currency amounts instead of points. Estimates and spending limits belong before generation; recorded usage belongs in the explanation of the final cost. Public prices and payment services have not been launched.

RouterShift focuses on model access. KernelWake focuses on enterprise media work. They retain separate accounts, permissions and billing. RouterShift generation calls, real publishing connectors and production services are still being integrated into KernelWake.

This website introduces the product direction and the current development boundary. It does not announce general availability, universal platform access or production publishing results. Confirmed availability will be described on KernelWake’s own website.