A direct case study for the playable build and QA hooks behind the Aimaxin portfolio.
This page packages the Arcane Harmonizer: Proving Grounds Idle build as recruiter-safe proof of product
work: a live browser game route, stable public URL, local save/export path, and source-visible hooks for
browser automation. It supports a product-building claim, not traffic, revenue, adoption, or client claims.
This is a stronger portfolio target than another abstract AI claim because a reviewer can open the game, inspect
visible state, and see how the build was shaped for repeatable browser checks.
01
Playable product
Arcane Harmonizer opens as a public HTML game
The live build renders the castle market, party table, command buttons, automap area, chronicle, and utility
controls without requiring an account, install, app wrapper, or private repository access.
Proof: live game routeSkill signal: JS + UI stateCheck: open and interact
The build exposes a text-state readback function, a time-advance helper, data-action buttons, data-utility
buttons, and stable DOM targets such as the party table, action list, map grid, and log lines.
Local save plus export/import makes update checks safer
The game uses browser local storage for autosave and includes export, import, reset, fullscreen, and help
utility controls so future build swaps can be tested without relying on a single fragile manual session.
Proof: local save pathSkill signal: release QACheck: export/import controls
For LinkedIn, this route is useful because it points at the build, explains the QA affordances, and keeps
the public claim to implementation, verification, and packaging around a shipped browser artifact.
Use: Featured or ProjectsSkill signal: product proofBoundary: no adoption claims
Direct proof page for a public HTML game build, stable play URL, browser QA hooks, local save/export path,
and conservative claim boundaries around Codex-assisted product work.
Project description
Browser-game product build with verification hooks
Packages Arcane Harmonizer: Proving Grounds Idle as a public work sample: playable route, source-visible
readback hooks, local persistence, export/import controls, and post-deploy verification.
Post angle to hold
From AI-assisted build to verifiable artifact
This can become a public LinkedIn post when the broader portfolio and discovery pages expose the new case on
plain canonical URLs. Until then, use the direct route as the safest proof link.
Claim Boundaries
What this case supports
Supports
Shipped browser artifact with QA affordances
This page supports claims about implementation, browser UI, state persistence, inspection hooks, stable live
routes, and release verification for a public Aimaxin game build.
Does not support
No audience, revenue, client, or hiring claims
This page does not claim user counts, traffic, revenue, engagement, clients, rankings, certifications,
employer approval, adoption, or hiring outcomes.
Live dependency
The build URL is the proof target
The case depends on the live game route opening cleanly. If the game is replaced later, this page should be
rechecked and updated with the new build state.
Next check
Re-test canonical discovery pages before posting
A broader public post should wait until plain portfolio, compact proof, all-content, RSS, and sitemap reads
expose this case without cache-busting.