LinkedIn posting readiness

Profile proof is ready. Broad public posting is still on hold.

Checked April 26, 2026 at 11:35 PT: Aimaxin's direct Codex proof routes are live and useful for LinkedIn Featured, Projects, and outreach. Plain broad pages still serve older Cloudflare HIT copies, so a public LinkedIn post should not lean on those broad URLs yet.

Open proof manifest Open proof map Proof router Systems proof QA playbook

Live Readback

What changed in the posting decision

The proof stack is strong enough for profile surfaces, but not broad enough for a clean public post until the plain canonical pages show the same proof markers that the direct routes and query-busted pages already show.

Ready for profile proof

Direct proof routes return current markers

The direct proof manifest, proof router, proof map, and systems proof routes return live 200 responses. These routes support profile claims about shipped public pages, route QA, browser-game proof, and deployment verification.

Use: Featured Use: Projects Use: outreach

Open manifest

Not ready for broad post

Plain broad URLs still lag at the edge

Plain portfolio, compact LinkedIn proof, all-content, RSS, sitemap, homepage, resources, and contact routes still returned older HIT copies without the newest proof-manifest markers during the live check.

Risk: stale unfurl Risk: stale discovery Decision: no broad post

Open cache readback

Origin is current

Query-busted pages expose the fresh proof stack

Query-busted portfolio, compact proof, all-content, RSS, and sitemap URLs exposed the manifest, router, proof-map, and systems-proof markers. That confirms the origin update exists; the remaining issue is the cached broad path.

Proof: origin freshness Skill: cache-aware QA Next: cache catch-up

Open QA playbook

Claim boundary

The proof stays inside shipped-work claims

This supports claims about Codex-assisted public routes, proof packaging, browser QA, publishing discovery, RSS/sitemap updates, and deploy checks. It does not claim traffic, revenue, clients, rankings, certifications, adoption, or hiring outcomes.

Supported: shipped systems Unsupported: metrics Framing: proof first

Open proof map

LinkedIn Use

What this page is for

Featured

Back the existing proof card

Use the direct proof manifest or profile proof map behind Featured. This page explains why those direct routes are safer than broad pages while cache state is mixed.

Featured receipt

Projects

Support the route-QA project item

Use this readback as a dated appendix for the Projects item about live route QA, proof readback, deploy verification, and cache-debug decisions.

Project readback

Public post

Wait for plain canonical freshness

A post can be stronger once the plain portfolio, LinkedIn proof, all-content, feed, sitemap, and homepage surfaces expose the current proof stack without query strings.

Portfolio