Public proof ledger
This ledger records which Aimaxin proof URLs were safe to share at the April 25, 2026 21:41 PT verification pass. It keeps LinkedIn and portfolio claims tied to public pages, not private workspace notes.
Live Status At Verification
These statuses came from direct live reads of aimaxin.com during this run. They are included as a receipt for the profile and portfolio decision, not as a permanent monitoring claim.
Newest readback
A fresh direct route records the April 25, 2026 22:36 PT follow-up check: ledger safe, broad proof pages still stale on plain URLs, and a public post still held back.
Current canonical
The direct QA receipts route returned 200 and exposed the latest proof set: browser build, proof checklist, compact proof page, portfolio route, guide route, discovery endpoints, and claim boundaries.
Cache-sensitive
The plain portfolio and compact proof URLs returned 200, but the edge copies did not yet expose the latest QA receipts wiring. Cache-busted reads showed the updated origin content.
Cache-sensitive
The checklist, all-content page, RSS feed, and sitemap also had stale plain canonical copies at the edge. Query-busted live reads showed the current origin files with the QA receipts and ledger wiring.
Product proof
Arcane Harmonizer: Proving Grounds Idle remains a concrete product proof link because the reader can open the game, interact with the UI, and inspect a shipped browser build directly.
Decision Record
Safer profile proof
A recruiter or collaborator can see why the direct receipt page is the safest link today instead of trusting a broad portfolio page that may lag at the CDN edge.
QA discipline
The ledger shows the release habit behind the work: check live routes, mark stale surfaces as risk, and avoid unsupported public claims.
No generic AI framing
The page points at public pages, browser builds, route integrity, discovery files, and deployment checks instead of generic AI capability language.
No-metrics boundary
This ledger does not claim revenue, traffic, clients, customers, engagement, rankings, certification, product adoption, or hiring outcomes.
Next Public Move
If canonical pages refresh
Once the plain portfolio, compact proof page, feed, and sitemap expose the latest proof wiring, the full portfolio can support a broader LinkedIn Featured or Projects link.
If cache stays stale
Keep LinkedIn proof pointed at direct routes that show the current claims without requiring cache-busting or private context.
If posting
The strongest non-repetitive post angle is not hype about AI. It is the workflow lesson: ship public artifacts, verify routes, and make stale cache states visible before promoting the work.
Proof links
Start with the QA receipts page, then use the checklist, compact proof route, portfolio, and browser build as deeper evidence once live freshness is confirmed.
Open QA receipts