The LinkTiller safety contract

Nothing leaves WordPress during the scan.

The first scan reads selected published content and builds an incoming-link map inside WordPress. It does not call Sai Studios, your configured model, or a third-party analytics service.

A model request happens only when an administrator tests the configured connection or asks for source opportunities for one target page.

What the configured endpoint receives.

• The selected target ID, URL, title, and up to 2,000 characters of plain-text content.
• Up to 40 locally ranked source IDs, titles, and excerpts of up to 700 characters.
• The model name selected in LinkTiller settings.
• An Authorization header only when the operator configured an API key.

Requests go directly from the WordPress server to the configured Base URL. Sai Studios does not relay, inspect, or store them. Provider retention and privacy terms still apply.

The private pilot adds six readiness gates.

Before evidence consent or any pilot write, an administrator can download a read-only preflight showing content-type counts, storage coverage, provider class and verification state, and every gate result. It excludes content, titles, URLs, credentials, endpoint and model names, hostname, generated site ID, and private session ID.

Private mode

An administrator explicitly enables the controlled five-site pilot gates.

Local evidence consent

Redacted pilot counters remain off until an administrator opts in. Nothing is sent automatically.

Current provider connection

The saved endpoint, model, and credential configuration must pass a connection test within 24 hours. Any configuration change invalidates that verification.

Recovery path

A current backup or recoverable staging path must be reconfirmed for each 24-hour write session.

Supported source storage

Classic and block-editor content may proceed. Builder-managed and registered-shortcode sources stay protected until that stack is explicitly validated.

Bounded session

One recovery confirmation opens at most three approved changes, with an immediate administrator write lock and automatic relock after an Undo failure.

Seven deterministic checks protect each insertion.

Administrator intent

A user with the required WordPress capability must request opportunities and approve a specific insertion.

Selected content

The source and target must still be published records from a content type selected in LinkTiller settings.

Exact phrase

The proposed 2-6 word anchor must still exist as editable text in the source. Rewritten or invented anchors fail.

Real destination

The target must resolve to the selected on-site post or page, and the source must not already link to it.

Fresh source

The current stored source content must match the SHA-256 snapshot that LinkTiller verified when it displayed the opportunity.

Fresh destination

The current destination type, status, title, content, and permalink must match the snapshot LinkTiller verified for that opportunity.

Safe placement

The phrase must be outside links, headings, code, forms, navigation, and other protected DOM contexts.

One insertion gets one receipt.

LinkTiller tags the inserted anchor, saves through WordPress, and confirms that the marker survived save processing before reporting success. The receipt records the source, target, anchor, and hashes needed for recovery. It does not claim that the link improved rankings.

Rendered review checkpoint

The active receipt opens the public source and destination. After inspecting both pages, an administrator can record a local human checkpoint only while the tagged link remains present and the destination remains published at the URL stored in the receipt. This is not automated visual verification.

Exact Undo

If the stored content still matches the approved result, Undo restores the exact content WordPress held before that insertion.

Surgical Undo

If later edits exist and the tagged LinkTiller anchor is still present, Undo removes only that link while keeping the later work. If the marker is missing or the state is ambiguous, LinkTiller refuses to guess.

What has been proved, and what has not.

Build proof

v0.3.7 passed the WordPress 7.1 deterministic smoke suite. Three clean builds matched SHA-256 7975AD0E...A1787.

Directory checks

Plugin Check 2.1.0 completed its full suite with no errors. Its documented runtime-enabled CLI path then ran all five runtime performance checks with no errors or warnings. A disposable blocking-script control produced the expected warnings, confirming the runtime collector was active.

Browser proof

A controlled provider-backed run inserted receipt 8820c9b5, restored the exact content, and refused a deliberately stale source. The v0.3.7 suite also refused destination changes before review and writing. Local receipt a8728a0e opened both public pages, persisted its rendered review, and restored the exact source on Undo.

Pilot session proof

A current saved-provider test, explicit local evidence consent, and confirmed recovery path open one private 24-hour session capped at three approved changes. The administrator can lock new writes immediately, and an Undo failure relocks them.

Preflight proof

The administrator-downloaded preflight reports environment classes, compatibility coverage, and gate states without content, URLs, credentials, hostname, or generated site identifiers.

Still unproved

No external pilot, ranking lift, time saving, retention, or adoption result has been established. v0.3.7 is not a public WordPress.org release.

The operator still owns the judgment.

Use a current backup or staging environment. Open the source and destination from each receipt, inspect both rendered pages, and record the checkpoint only after that review. Check custom post types and page builders before assuming their storage model is safe. Keep provider credentials out of pilot notes and support messages.