Direct proof checklist
This page is built for fast profile review. It points to live artifacts, explains what each route proves, and keeps the claims limited to shipped pages, browser builds, QA loops, and publishing infrastructure.
Verification Stack
Product Build
Arcane Harmonizer: Proving Grounds Idle is a public HTML build with party flow, castle services, auto-delving, local save state, and repeatable browser interaction.
Route QA
Public proof links are checked as routes, not assumed from local files. The hybrid-work guide is a direct example of a promoted route that now resolves as a public page.
Portfolio Packaging
The portfolio page groups the work into AI systems, browser builds, guide architecture, publishing ops, route-integrity QA, and recruiter-safe proof framing.
Publishing Ops
Public changes are wired into the content map, RSS, and sitemap so the site has a crawlable trail beyond the visible navigation layer.
QA Receipts
The receipts route keeps the verification story explicit: which public URLs carry the proof, how broad discovery surfaces are handled, and which metric claims are intentionally out of scope.
Cache Ledger
The proof ledger records which profile-safe routes were current at the live readback pass and which broader pages still needed cache follow-up before they could support a public post.
Live Readback
The readback receipt records the current live check in one fresh route, making the safe profile link explicit while the broad portfolio and discovery pages remain cache-sensitive.
QA Loop
Before promoting a link
A profile-facing artifact should open as a live route before it becomes a Featured, Projects, or post link. The point is to avoid asking a reader to trust a private build or a missing page.
After changing the site
Proof pages are checked at wide and narrow widths so the portfolio framing does not break for the actual person clicking through from LinkedIn.
After publishing
Changes are connected to navigation, content-map entries, feeds, sitemap records, and deploy lists when those surfaces are relevant to the proof claim.
Claim Boundaries
This page does not claim traffic, revenue, engagement, rankings, client outcomes, hiring outcomes, or product adoption. It only links to public artifacts and the systems work behind them.
The proof links are designed to work without asking a reviewer to inspect a private repository, account, analytics dashboard, or unpublished local file.
The signal here is implementation: routes, pages, browser builds, publishing workflows, QA checks, deploy coverage, and clear framing for technical readers.