Any meta key Aiomatic actually writes to wp_postmeta. Common ones are _aiomatic_source_url, _openai_model, _aiomatic_run_id and a prompt-category key, but the agent UI scans the installation and lists the meta keys present so you pick from a real list rather than guessing names.

No. SleekView never calls a model vendor. It reads what Aiomatic has already written to your WordPress database. If a generation never reached WP, it cannot appear in the table, which is the honest behaviour rather than a fabricated row.

Yes. Select rows, pick a new status and SleekView writes the changes through wp_update_post, so post-status hooks, taxonomy updates and any plugins listening on save still fire as expected.

Aiomatic can attach generated images to a post. SleekView shows them through the standard featured-image column when configured; the audit table is centred on the post artifact, so the image stays linked to its parent generation.

Yes. Aiomatic can be configured to write into any writeable post type, and SleekView mirrors that. Build separate tables for posts, products and case studies, or one combined table scoped by post type.

Yes. Each saved view captures column set, filters and sort order. Gate it by WordPress capability so editorial sees a draft-review table, governance sees a disclosure audit, and finance sees the model-mix slice.

Yes. Any filtered set exports as CSV with the same columns the view shows. Useful for briefing an external editor or for archiving a snapshot before a cleanup sprint.

No, it is an additional admin surface. Aiomatic's own screens stay where they are. SleekView gives editorial, ops and governance teams the row-level audit they actually need without disturbing the plugin's workflow.