Every page on the journal now carries the async verification script for the site publisher account in its head, so ownership checks pass on the home page, on articles, and on log entries alike. The tag is the vendor verification script: one static line in the shared head template, with no ad units, no placements, and no visual change anywhere.
Motivation
The journal plans to verify ownership with the ad vendor before ever serving ads, and verification requires the same script tag in the head of every public page. A single shared head template already renders each page on the site, so one static line there covers the whole corpus at once. Shipping verification now, without any ad units, keeps the door open for later revenue work while leaving reading completely untouched.
What changed
The shared head template now ends with the async vendor verification script just before the closing head tag, after the deferred site script. Because the tag is plain static markup with no builder placeholder, the builder passes it through unchanged to the home page, every article page, and every log page. The artifact budget test now allowlists only that exact vendor address while continuing to block every other external script or image, and this log entry ships beside the change in the same pull request.
How it was done
After the hosting preflight and a fresh branch from the main line, development added the single script line to the shared head template and narrowed the artifact test with an exact-match exception for that vendor address. The log entry was drafted beside the change with the pipeline trail attached, then the site was rebuilt to confirm the tag lands on the home page, an article page, and the log index. The full suite and the presence gate were run to confirm the budgets still hold and the entry covers the production change.
Verification evidence
The site build exits success and the built home page, one article page, and the log index each contain the verification tag for the publisher account. The full suite is green, including the narrowed artifact budget test, and the presence gate prints success with this entry covering the change. A scan of the diff finds no secrets, and security plus quality reviews attach to the exact pushed head after the pull request opens.
How this entry was built.
Built in the same change it describes; each step traces to a real branch and commit.
- Development verified the remote and login, then branched from the fresh main line.
- Development added the verification script to the shared head plus this entry.
- Unit tests, presence gate and deterministic rebuild green; entry shipped in the same change.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
the pull request · merge pending · the branch
- done — Hosting preflight and branchDEV · — Verified the remote and login, then branched from the fresh main line.
- done — Verification snippet and log entryDEV · — Added the async verification script to the shared head plus this entry.
- done — Pull requestDEV · — Opened the pull request with the snippet and the log entry.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Hosting preflight and branch | DEV | done | commit | Verified the remote and login, then branched from the fresh main line. |
| Verification snippet and log entry | DEV | done | commit | Added the async verification script to the shared head plus this entry. |
| Pull request | DEV | done | commit | Opened the pull request with the snippet and the log entry. |
Why each step ran.
- DEV
- The snippet lives in the shared head template as static markup with no builder placeholder, so the builder passes it through to every rendered page unchanged. The artifact budget test now allowlists only that exact vendor address while keeping every other external script or image blocked. The deterministic build, the full suite, and the presence gate pass with this entry covering the change.
- SEC
- Not evidenced in the linked record. The security verdict for the reviewed head is recorded in the review trail.
- QA
- Not evidenced in the linked record. The quality verdict for the reviewed head is recorded in the review trail.
- Director
- This change adds one vendor verification script through the existing head template with no visual or structural change elsewhere. Security and quality reviews are pinned to the exact pull-request head in parallel. Release approval fires only when both verdicts pass that exact head.
Receipts.
●●●