Tlloancy Source Stamp

Tlloancy Source Stamp listens to the official WordPress AI Client (wp_ai_client_prompt() / wp_ai_client_after_generate_result). When a generation finishes through that API, the plugin writes a row in a table on your database. When the post is saved, it is stamped (origin, model, time) from the generation that was made for it.

The journal stores metadata only: caller plugin, model, provider, context, token counts when available, and the user account that triggered the generation. Prompt and completion text are never stored.

An optional visitor-facing note can appear on posts the plugin stamped as generated or assisted. Unstamped posts stay silent.

What it does

• Listens to wp_ai_client_after_generate_result (WordPress 7.0+)
• Writes a self-hosted journal (Tools → Source Stamp), filterable and paginated
• Never stores prompt or completion text
• Stamps a post from the generation made for that post (editor, REST route or post_id parameter), or from the only generation waiting for you (15 minutes)
• Block editor sidebar panel and classic editor box to set or correct the origin by hand
• Optional visitor-facing note only on stamped posts, also in feeds
• CSV export of the whole journal
• Personal data export and erasure for the journal, and suggested privacy policy text
• Daily prune of rows older than 365 days (filter tllss_retention_days)

What it does not do

• Site-wide chatbot banners or AI-tool scanners
• Image IPTC / C2PA embedding
• Compliance scores, Article 4 checklists, or legal templates
• RAG, budget caps, or model routing

Honesty about the law

Installing this plugin does not make a site compliant with Regulation (EU) 2024/1689. Whether Article 50 applies to a given page is a legal assessment for the site operator. This is a technical record of AI Client use.

Requirements

Automatic stamps need WordPress 7.0 (or later) so wp_ai_client_prompt() exists. On older versions the journal stays empty; you can still set origin by hand in the editor. The block editor panel is shown for post types that support custom fields and the REST API; other types keep the classic box.

Privacy

The journal links each generation to the WordPress user who triggered it. It stays in your database, is deleted after the retention period, can be exported and erased with the WordPress privacy tools (erasing detaches the account and keeps the technical row), and is detached automatically when a user is deleted. Suggested policy text is added to the Privacy Policy guide.