LinkedIn proof router

Open this first when a profile reader needs the current Aimaxin proof path.

This route exists because the strongest proof should not depend on stale broad cache layers. It points a recruiter, collaborator, or technical peer to the live direct routes that currently support Nathan Funk's Codex-built AI systems, browser-game QA, publishing automation, guide architecture, and deployment claims.

Open proof manifest Posting readiness Start with proof map Open systems proof Featured receipt Game QA case QA playbook Portfolio

Reader Path

Which proof link to use for each question

The router keeps the profile path short: one direct start page, then deeper evidence only when the reader wants systems detail, product proof, QA method, or cache-status context.

Technical appendix

What route inventory backs the profile proof?

Open the proof manifest when the reader wants the human-readable route inventory, the structured JSON manifest, live-readback status, and supported versus unsupported claim boundaries.

Best target: technical review Proof: HTML + JSON manifest Use: route inventory

Open manifest JSON

Fast profile review

What should I open first?

Open the profile proof map. It gives the shortest click order from LinkedIn wording to proof brief, systems index, playable browser build, QA playbook, and claim boundaries.

Best target: Featured or Projects Proof: direct public URL Use: recruiter scan

Open proof map

Technical review

What shipped beyond profile copy?

Open the AI systems proof index. It connects browser-game product work, QA hooks, publishing and discovery plumbing, affiliate guide architecture, deployment checks, and no-metrics limits.

Shows: systems architecture Proof: shipped pages Use: technical peer review

Open systems proof

Product proof

Where is the live build?

Open the browser-game QA case, then the Arcane Harmonizer play route. The case documents live interaction, source-visible test hooks, local save/export behavior, and stable URL framing.

Shows: playable product Proof: browser route Use: product signal

Open game QA case Open live build

QA method

How is the work verified?

Open the browser QA playbook and cache readback. Together they show the route, DOM/state, responsive, feed, sitemap, and cache checks behind profile-safe proof decisions.

Shows: verification loop Proof: route checks Use: QA discipline

Open QA playbook Open cache readback

Claim Boundary

What this supports and what it does not claim

Supported

Codex-assisted site architecture, public HTML routes, browser-game builds, QA hooks, discovery wiring, RSS/sitemap updates, SFTP deployment checks, and cache-aware public proof decisions.

Not claimed

This page does not claim traffic, revenue, clients, hiring outcomes, ranking, certifications, production adoption by another company, or private employer work.

Current post decision

Because broad plain proof pages are still stale on public readback, this route supports profile proof and Featured/Projects context better than a new broad public LinkedIn post.