AI systems proof index
This index packages the strongest public proof into a single profile-safe URL: a playable browser build, source-visible QA hooks, publishing and deployment plumbing, guide architecture, cache-aware verification, and explicit boundaries around what is not being claimed.
Proof Lanes
Each lane points at a public Aimaxin artifact or discovery surface a technical reader can open. The goal is proof of implementation and process, not vague AI positioning.
Product build
Arcane Harmonizer: Proving Grounds Idle is a public HTML build with party management, castle services, auto-delving, local persistence, export/import controls, fullscreen support, and a fixed route.
Browser QA
The game case records source-visible hooks such as text-state readback, time advancement, data-action controls, data-utility controls, local storage persistence, and stable DOM targets. The QA playbook explains how those checks fit into route, mobile, cache, RSS, and sitemap verification.
Publishing ops
Aimaxin changes are wired into the content map, shared discovery data, RSS, sitemap, and static deploy lists so proof pages are not isolated one-offs after they ship.
Guide architecture
The guide layer is structured around problems such as hybrid work, desk flow, creator capture, audio, power reliability, and camera support, with disclosure and internal paths visible before product links.
Profile packaging
The compact proof route, project readback, and proof ledger explain what to link from Featured or Projects, which routes are safest, and why broad public posts should wait when canonical pages are stale.
Verification discipline
The proof ledger and live readback routes record when direct pages are fresh and when broad pages are Cloudflare-stale, keeping LinkedIn copy tied to what a reader can verify today.
LinkedIn Use
Featured title
Direct proof index for Codex-built Aimaxin work: browser-game product build, QA hooks, publishing and deployment plumbing, guide architecture, and conservative claim boundaries.
Project description
Packages live Aimaxin artifacts into one verification route for product building, automation-aware browser QA, RSS/sitemap discovery, route integrity, and profile-safe proof packaging.
Post boundary
This route supports a Featured or Projects link now. A broader public post should wait until the plain portfolio, compact proof, all-content, RSS, and sitemap URLs expose the newest wiring without cache-busting.
Claim Boundaries
Supports
This page supports claims about shipped browser artifacts, automation-aware QA hooks, live route checks, discovery-file wiring, guide architecture, and clearer public proof packaging.
Does not support
This page does not claim customers, usage, traffic, revenue, engagement, clients, rankings, certifications, employer approval, product adoption, or hiring outcomes.
Safest use
Use this direct route when a reader needs the shortest path from profile claim to public artifacts without relying on a broad page that may still be serving an older cached copy.
Next check
Before publishing a public LinkedIn post, recheck the plain portfolio, compact proof page, content map, games hub, RSS, and sitemap for the new proof-index link.