Live proof readback

A dated receipt for profile-safe Aimaxin proof links.

This page records the April 25, 2026 22:36 PT live readback pass for Nathan Funk's Codex-built Aimaxin proof surface. It exists because the broad portfolio and discovery URLs still served older Cloudflare HIT copies, while direct receipt routes remained the safer profile proof.

Route Status

What opened cleanly, and what did not prove the newest wiring

These are live URL readbacks from aimaxin.com during this run. They are a release receipt, not a promise that cache state will remain unchanged.

01

Fresh direct receipt

Codex live proof readback

This route was created as a new public proof artifact so a profile reader can open the current readback without depending on an older cached portfolio page.

Status: new direct route Use: Featured or Projects support Signal: release readback
02

Profile follow-up

LinkedIn project proof readback

A follow-up receipt records how the LinkedIn Projects item points at this live Aimaxin readback route while preserving the same no-metrics and cache-aware promotion boundary.

Status: direct proof route Use: Projects context Signal: profile proof packaging
03

Current safe proof

Codex public proof ledger

The ledger returned 200 and exposed the proof-ledger, QA-receipts, proof-checklist, and compact LinkedIn proof markers. It remains the safest preexisting direct proof link from this pass.

Status: safe direct link Use: profile proof Signal: cache-aware QA
04

Partially stale direct routes

Older proof pages still opened, but did not show the newest link set

The compact LinkedIn proof page, proof checklist, and QA receipts returned 200, but their plain cached copies did not all expose the newest ledger and readback wiring. They remain useful as older proof, not as the latest proof surface.

Status: verify before promoting Use: supporting evidence Signal: CDN cache readback
05

Do not post from broad pages yet

Portfolio, content map, RSS, and sitemap were still stale on plain URLs

The broad proof and discovery URLs returned 200 but did not expose the newest proof-ledger or QA-receipt markers on plain canonical reads. That makes a fresh public LinkedIn post too easy to overstate until the edge cache catches up or is purged.

Status: broad cache blocker Use: recheck before posting Signal: conservative claims

LinkedIn Use

Profile-safe copy for this proof link

Featured title

Aimaxin Codex Live Proof Readback

A dated live readback for Codex-built Aimaxin proof links: what opens now, what remains cache-sensitive, and where the public work can be verified.

Projects description

Route QA and proof packaging

Documents a Codex-assisted portfolio QA pass across public proof URLs, discovery files, and no-metrics claim boundaries before promoting the work on LinkedIn.

Post boundary

Skip the broad post until broad URLs catch up

The readback supports a profile proof link today. It does not support broad claims about traffic, adoption, customers, clients, ranking, revenue, or engagement.

Strongest next angle

Ship, verify, then promote

The clean public lesson is the workflow: make proof links public, check the live routes, and hold back promotional copy when the readback does not support it.

Claim Boundaries

What this page proves, and what it does not claim

Proves

Public artifacts and route QA

This readback points to public Aimaxin pages, a live browser build, proof receipts, discovery files, and a conservative decision not to post when broad URLs are stale.

Does not claim

No traffic, client, or revenue proof

This page does not claim customer usage, traffic, revenue, engagement, clients, rankings, certifications, employer approval, or hiring outcomes.

Best use

Recruiter or collaborator skim

Use this page when the reader needs one current receipt before deciding whether to inspect the broader portfolio, the proof ledger, or the playable build.

Next check

Re-test canonical pages first

Before the next LinkedIn post, recheck the plain portfolio, compact proof page, content map, RSS, and sitemap. If they still serve old copies, keep using direct proof routes.