AIthor pushes the prompt to a model vendor and drops the response back into WordPress as a post or block. The model owns the conversation. WordPress owns the resulting artifact: a row in wp_posts with an author, a status, a modified date and the meta AIthor stamps on top to mark it as a generated piece.

That artifact is what an editorial team can actually triage, and what the default Posts screen turns into one more long list. SleekView reads the same wp_posts rows and the same postmeta directly. Title, author, status and date sit alongside model, prompt category and generation status as real columns. Sort by date, filter to drafts on a single model, or pull every generation tied to a specific prompt category, all without opening each post.

Edits run through standard WordPress CRUD, so post-save hooks still fire, taxonomy updates still propagate, and any AIthor-side meta the plugin reads on update stays consistent.

AIthor lowers the cost of producing a post so much that volume rises before any reporting is in place. The default Posts screen is poorly equipped to summarise that volume: model and prompt category are stored in postmeta, hidden behind a click. SleekView reads the same wp_posts rows and the same meta and turns them into columns a team can sort, filter and edit.

Editorial leads stop opening every draft to check the model. Governance stops guessing about disclosure coverage. Content ops stops scrolling for templates that nobody adopts.

Same posts, same meta, completely different conversation in the editorial meeting.