LinkedIn proof link
This compact route gives one shareable profile target for Nathan Funk's Aimaxin work: live browser builds, homepage product routing, publishing automation, guide architecture, route-integrity QA, RSS/sitemap wiring, deployment cleanup, and a direct systems-proof index for profile readers.
Fast Proof Stack
Proof Manifest
Gives technical readers a direct HTML page and JSON manifest for the current proof routes, cache boundary, supported claims, and unsupported metrics claims.
Posting Readiness
Records the current live cache split: direct proof routes are useful for Featured, Projects, and outreach, while broad canonical pages still lag enough to make a fresh public post weaker.
Proof Router
Routes the reader through the direct proof map, systems proof, game QA case, and QA playbook while keeping broad public-post claims on hold until stale plain URLs catch up.
Portfolio
The portfolio page ties the site into AI systems, publishing automation, browser builds, affiliate guide architecture, QA loops, and deployment operations.
Homepage
The live homepage now places browser builds in the opening product surface alongside AI routes, guide lanes, and selected reads instead of treating games as a hidden side path.
Product Build
Arcane Harmonizer: Proving Grounds Idle is a stable public HTML build with party management, castle services, auto-delving, save state, and browser-first interaction.
Publishing Ops
Aimaxin changes are pushed into the crawlable content map, RSS feed, and sitemap so public proof is not limited to a single visible page.
Route Integrity
Profile-facing links are treated as release artifacts: a promoted guide route must open directly, appear in the static publish path, and be easy to verify from the portfolio surface.
Guide Architecture
The guide layer is organized around real setup blockers such as desk flow, hybrid work, creator output, power reliability, and audio/video confidence instead of generic product sprawl.
Direct Checklist
A shorter verification route that lists the safest live artifacts, what each one proves, and the claim boundaries for Nathan Funk's Codex-built Aimaxin work.
QA Receipts
The receipts page shows the safer direct proof set when broad portfolio pages are cache-sensitive: browser build, checklist, compact proof route, guide route, discovery endpoints, and claim boundaries.
Proof Ledger
The ledger records the live freshness state for public proof links, including which direct route was safe to share and which broad pages needed cache follow-up before supporting a public post.
Live Readback
The readback route records the latest live check: proof ledger safe, broad portfolio and discovery pages still cache-sensitive, and no public post until the public URLs support the stronger claim.
Project Readback
The project readback records the profile proof item, the direct Aimaxin route it points at, and the cache-sensitive broad pages that keep the public post boundary conservative.
Game QA Case
The game QA case explains the live Arcane Harmonizer route, source-visible readback hooks, local save/export path, and conservative claim boundary for profile-safe product proof.
Systems Proof Index
The systems proof index ties the browser build, QA hooks, publishing/discovery surfaces, guide architecture, proof receipts, and claim boundaries into one profile-safe page.
Browser QA Playbook
The QA playbook explains how live routes, DOM/state readback, desktop and mobile layout checks, cache state, RSS, sitemap, and claim boundaries are verified before profile links or posts rely on them.
Canonical Cache Readback
The cache readback records which plain public URLs still served older edge copies and why direct proof routes remain safer for Featured or Projects until the broad pages catch up.
Profile Proof Map
The proof map turns the profile claim into a short review path: compact brief, systems proof, playable build, browser QA, and current cache boundary, all without metrics claims.
Featured Receipt
The Featured receipt documents the safest profile proof link, the live proof-map route check, and the cache boundary that keeps broad public posting on hold.
Verification Notes
This proof page does not claim traffic, revenue, clients, hiring outcomes, rankings, certifications, or adoption numbers. It points to shipped public artifacts.
Each proof claim is tied to a live Aimaxin URL or a machine-readable discovery surface that can be opened directly from the page.
The point is implementation: routing, page architecture, browser builds, QA checks, deployment plumbing, and explaining the work clearly enough for a technical reader.