Proof of work
This page turns Aimaxin into a clearer portfolio surface: not just a content site, but a running record of Codex-assisted product work, site architecture, automation, deployment, and live browser experiences.
Portfolio Lanes
AI Systems
Aimaxin is organized around routes, blockers, guide lanes, selective reads, and proof surfaces instead of a flat pile of pages. The system keeps navigation, content, and monetization paths connected.
Open routing layerBrowser Builds
Arcane Harmonizer and Spaghetti Clicker are standalone browser builds with stable URLs, local saves, and automation-friendly inspection hooks for repeated browser checks.
Open games hub Open game QA casePublishing Ops
Site changes are built as durable HTML surfaces, wired into shared discovery, and published with SFTP, WordPress sync, RSS, sitemap, and live route verification.
Open content mapMonetization
Buying pages are grouped by actual setup blockers: desk flow, creator output, comfort, reliability, and travel workflows, with disclosure and decision paths visible before product links.
Browse guide lanesCase Studies
These are the fastest public routes to verify the work: live product builds, homepage product positioning, a JSON-backed proof manifest, a dated posting-readiness readback, machine-readable shipping surfaces, route-integrity QA, blocker-led guide architecture, direct proof checklists, recruiter-safe proof packaging, a public cache-status ledger, a dated live-readback receipt, a canonical cache readback, a LinkedIn Projects readback route, a direct browser-game QA case, a consolidated AI systems proof index, a browser QA playbook, a profile proof map, a LinkedIn Featured receipt, and a direct proof router for profile readers. The newest direct routes keep the QA claim verifiable even when older broad pages are cache-sensitive.
Proof Manifest
Adds a direct manifest that lists the current proof routes, their supported claims, the cache readback boundary, and the unsupported metrics claims in both readable page form and structured JSON.
Posting Readiness
Records the April 26, 2026 11:35 PT live check: direct proof routes are safe for Featured, Projects, and outreach, while broad canonical pages are still stale enough to keep a public post on hold.
LinkedIn Proof Router
Gives recruiters and technical peers a direct first-click path while broad canonical pages are still cache-sensitive: proof map first, systems proof second, then browser-game QA and QA playbook details.
Product Build
Rebuilt a browser game into a Wizardry-style idle crawler with castle services, party management, spell circles, trap chests, auto-delving, save state, and browser automation hooks.
Product Surface
Promoted browser builds into the homepage highlight band so Arcane Harmonizer and Spaghetti Clicker read as public products, with direct routes into stable game URLs and the games hub.
Automation
Built and maintained a shipping loop where workers update site surfaces, verify live routes, and leave a machine-readable trail through the content map, RSS feed, and sitemap after each public-facing change.
Content System
Expanded the guide layer into blocker-led lanes for desk flow, hybrid work, creator kits, audio, power, camera workflows, and reliability, with disclosure and decision paths visible before product links.
Deployment QA
Treats portfolio CTAs as release-critical routes: guide links are checked after deploy, added to the static publish list when needed, and verified as live URLs before they become proof targets.
Proof Packaging
Packaged the work into a single live surface that explains what shipped, what each route proves, and where to click next without forcing a recruiter to decode the whole site first.
Direct Verification
Gives recruiters and collaborators one short route that lists the safest live artifacts, explains what each route proves, and keeps the claims bounded to shipped pages, browser builds, QA, and publishing ops.
QA Receipts
Adds one direct receipts route for the public URLs behind the profile proof: live browser build, checklist, compact proof page, portfolio route, guide route, discovery endpoints, and explicit cache-risk framing.
Public Proof Ledger
Records the live verification state for proof URLs so a profile reader can see which public route was safest to share and which broad pages still needed cache follow-up.
Live Readback
Captures the current live URL state in one fresh direct route: which proof link was safest, which broad pages were still cache-sensitive, and why no broad LinkedIn post should overstate the proof yet.
LinkedIn Projects
Records the Projects proof surface after it was updated to point at the live readback URL, with the same no-metrics boundaries and cache-aware promotion decision kept visible.
Browser QA Case
Packages Arcane Harmonizer as a public work sample with a live play route, source-visible state readback hooks, local save/export controls, and claim boundaries suitable for LinkedIn Featured or Projects.
Systems Proof Index
Consolidates the strongest public proof into a single profile-safe page: live browser build, game QA hooks, publishing/discovery plumbing, guide architecture, proof receipts, and no-metrics boundaries.
Browser QA Playbook
Documents the verification loop behind the portfolio proof: live URL readback, DOM/state hooks, desktop and mobile checks, discovery-file wiring, cache-aware promotion decisions, and no-metrics claim boundaries.
Canonical Cache Readback
Records the April 26, 2026 canonical readback showing portfolio, compact proof, all-content, games, RSS, and sitemap URLs still serving stale edge copies while direct proof routes remain safer profile targets.
Profile Proof Map
Gives profile readers a short verification sequence: proof brief first, systems proof second, playable product and QA case next, then deploy/cache readback with explicit no-metrics boundaries.
LinkedIn Featured
Records the safest current profile proof path: keep the Featured card pointed at the direct profile proof map while broad portfolio and discovery pages remain cache-sensitive on plain public reads.
Fast Verification
Build Proof
The flagship browser build lives on a fixed URL, keeps local save state, and can be opened as a public work sample rather than a private repo artifact.
Systems Proof
The commercial layer is not a list of random products. It is grouped by workflow blockers, with disclosure, internal links, and narrower routes once the problem is known.
Ops Proof
New work is not only visible on the page layer. It is pushed into the content map, RSS feed, and sitemap so publishing changes become crawlable and easier to verify after release.
Route QA
Portfolio CTAs are checked as public URLs, not assumed from local files, so a profile-facing proof link does not depend on an unpublished static route.
Profile Copy
Headline Angle
Aimaxin is public proof that the work is not just prompting. It is planning, implementation, QA, routing, deployment, and making each shipped asset easier to explain.
Featured Angle
Link this page as a Featured item when the goal is to show systems work quickly: games, guide lanes, publishing automation, and verification all in one shareable surface.
Featured / Projects Link
Point profile cards at the shorter proof route when the reader needs the fastest scan: profile copy, portfolio link, live build, guide catalog, RSS, sitemap, and explicit no-metrics framing.
Open LinkedIn proofProof Map Link
Use the profile proof map when the reader needs a direct path from profile copy to proof brief, systems proof, live browser build, QA playbook, and current cache boundary.
Open proof mapFeatured Receipt
Use this when the Featured card itself needs context: direct proof-map target, live route readback, cache boundary, and no-metrics guardrails.
Open Featured receiptFast Review Link
Use the checklist when the reader should see the build route, route QA, publishing discovery surfaces, and no-metrics claim boundary before deciding which deeper page to open.
Open proof checklistQA Receipts Link
Use the receipts page when the point is route integrity: what was checked, which live URLs carry the proof, and which claims are intentionally not being made.
Open QA receiptsLive Readback Link
Use the readback route when a reviewer needs the newest live URL status before trusting a broader portfolio or discovery-page claim.
Open live readbackProjects Link
Use the project readback when the profile proof item itself needs context: what it points at, what it proves, and where the promotional boundary stops.
Open project readbackProduct Proof Link
Use the game QA case when the profile needs a concrete product artifact: live play route, state hooks, persistence controls, and browser verification framing.
Open game QA caseSystems Proof Link
Use the AI systems proof index when the reader needs one direct page that ties product build, QA hooks, publishing ops, guide architecture, and claim boundaries together.
Open systems proofQA Playbook Link
Use the browser QA playbook when the reader should see how routes, state hooks, mobile checks, cache state, RSS, and sitemap entries are verified before public promotion.
Open QA playbookPost Angle
Strong posts should point to one real change, explain the workflow behind it, and connect that work to AI systems, automation, product building, or publishing infrastructure.