QA receipts
This page keeps one public receipt trail for profile-facing Aimaxin proof: live route checks, responsive verification targets, deployment discovery surfaces, and the claim boundaries around Nathan Funk's Codex-assisted systems work.
Verified Route Set
These links are useful for LinkedIn Featured, Projects, or recruiter review because each one is a public artifact rather than a private workspace claim.
Product Build
Arcane Harmonizer: Proving Grounds Idle is the fastest product proof: a public HTML build with party flow, castle services, auto-delving, local save state, and browser-first interaction.
Direct Verification
The checklist page packages the safest live artifacts into one scan-friendly route and makes the no-metrics boundary visible before the reader clicks deeper.
Route Integrity
The hybrid-work guide is a route-integrity receipt: a page that was promoted as proof only after the static deploy path included it and the direct public URL returned successfully.
Profile Surface
The compact proof page is built for profile cards: it explains the work in AI systems, browser builds, guide architecture, route QA, RSS/sitemap wiring, and deployment cleanup.
Portfolio Surface
The full portfolio groups Aimaxin into AI systems, browser builds, publishing ops, affiliate guide architecture, route-integrity QA, and proof packaging.
Discovery Trail
Broad discovery surfaces are kept in the deploy set so proof pages have more than one route into them. If an edge cache lags, the direct proof URL remains the safest link to share first.
Cache Ledger
The ledger records which proof URLs were current at publish-time verification and which broad pages were still cache-sensitive, so profile claims stay tied to safe public links.
Live Readback
The readback page captures the newest live status after this proof pass, including the safe direct route, the stale broad pages, and the reason a broader LinkedIn post was skipped.
Receipt Logic
Route check
A profile-facing link should return a usable public page, not just exist as a local file or a planned route in the workspace.
Layout check
Proof pages need to work at recruiter-click widths, so the receipt route is designed around the same responsive portfolio card system as the existing proof surfaces.
Deploy check
The file is included in the static deploy manifest and mirrored into RSS, sitemap, and site discovery data when those public surfaces are relevant to the claim.
Cache check
When older portfolio pages lag at the CDN edge, this direct route keeps the public proof claim narrow: the linked artifacts are the receipt, not an unsupported broad claim.
Claim Boundaries
Proves
The receipts show that Aimaxin has public pages, browser builds, guide routes, proof pages, and discovery surfaces that can be opened and inspected.
Proves
The work is framed around route integrity, responsive review, deploy coverage, discovery wiring, and explicit boundaries for public profile claims.
Does not prove
This page does not claim revenue, traffic, customers, clients, engagement, search rank, hiring outcomes, certifications, or product adoption.
Use on LinkedIn
Point readers here when the strongest signal is disciplined shipping: build, route, verify, publish, and state the limits of what the public artifact proves.
Open checklist