AI Content Integrity
Inspect writing signals, protect exact facts and retain evidence without turning patterns into proof of authorship.
AI content integrity · Browser tools and evidence
Inspect text, protect exact facts and understand method limits without treating a writing pattern as proof. Each route states what ran, what did not run and what the result can support.
AI collection
Start with the browser checker for a private text inspection, or open the parent product for the complete method map. Platform pages explain how the same bounded checks work in Astro, Chrome, a terminal or local service, and WordPress. The research lab and methodology record what public evidence can support and where an official verification route is still unavailable.
Inspect writing signals, protect exact facts and retain evidence without turning patterns into proof of authorship.
Run local exact-character, Unicode, writing-pattern and protected-content checks in the browser.
Review what public research can support while the official Anthropic verification route remains unavailable.
Inspect rendered pages through the Astro Dev Toolbar and create bounded, report-only build evidence.
Inspect deliberately selected or pasted text locally without host permissions, analytics or remote code.
Run model-free checks from a terminal or through an authenticated service bound to the local machine.
Inspect posts in WordPress and retain optional hash-only receipts under explicit administrator controls.
Read the evidence model, method states, limitations and privacy rules behind the suite.
Opace tools
These routes share named methods and receipt formats, but each page documents its own capture method, data handling, release evidence and installation limits. That distinction matters when browser text, build output, selected page copy and WordPress drafts pass through different software boundaries.