Wordtune sends sentences through its rewriter and stamps the chosen variant back into a WordPress post. The vendor owns the model call. WordPress owns the artifact: a row in wp_posts with title, author and status plus a handful of wp_postmeta keys describing the rewrite mode, suggestion count and source post id.

The default Posts screen shows title, status, author and date, and leaves the rewrite metadata buried in postmeta. SleekView reads the same wp_posts rows and the same meta directly. Mode, suggestion count and source post become first-class columns next to title and status. Sort by suggestion count, filter to rewrites in casual mode, or pull every rewrite tied to a single source post.

Edits route through wp_update_post and update_post_meta, so post-save hooks still fire and the Wordtune integration's meta stays consistent on update.

Wordtune lives inside an editor's workflow, which means its writes pile up quietly inside wp_postmeta without ever changing how the Posts screen looks. The default admin keeps showing title, author, status and date while the rewrite mode and suggestion count that actually drive editorial decisions stay one click away. SleekView reads the same rows and the same meta and turns them into a sortable, filterable, inline-editable table.

Editorial leads stop opening each draft to check the mode. Brand teams catch casual-mode polish on copy that should stay formal. Governance audits AI-stamped rewrites without exporting raw SQL.

The integration's writes stay intact and the view layer simply makes the audit possible at the row level rather than the post level.