Codex proof manifest

A direct manifest for the Aimaxin proof stack.

This page gives profile readers and technical peers one fresh route that describes the proof links, the JSON manifest, the current cache boundary, and the claims Nathan Funk can make about Codex-built Aimaxin work without leaning on traffic, revenue, client, or adoption metrics.

Open JSON manifest Posting readiness Open proof router Proof map Systems proof QA playbook

Manifest Contract

What this route records

The manifest turns the proof stack into an inspectable contract: what exists, what each route supports, what was checked live, and what should not be claimed from the public artifact.

Machine-readable artifact

JSON route for proof readback

The JSON file lists the proof router, proof map, systems proof, QA playbook, game QA case, live build, and cache readback routes in a structured format a technical reviewer can inspect quickly.

URL: /codex-proof-manifest.json Proof: structured route list Use: technical appendix

Open JSON manifest

Posting-readiness receipt

Dated post-or-hold decision for LinkedIn

The readiness page records the current live split: direct proof routes are strong enough for profile surfaces, while stale broad pages make a fresh public LinkedIn post a weaker move.

URL: /codex-linkedin-posting-readiness-20260426.html Proof: cache-aware decision Use: profile-safe planning

Open readiness

Public route stack

Short path from profile claim to evidence

The manifest keeps the strongest proof order explicit: proof router, profile proof map, systems proof, browser QA playbook, browser-game QA case, and the playable Arcane Harmonizer route.

Proof: direct public URLs Skill signal: IA, QA, deployment Use: recruiter scan

Open proof router

Cache boundary

Broad pages are not the public-post anchor yet

The live check still showed plain portfolio, LinkedIn proof, all-content, RSS, and sitemap URLs serving older HIT copies. Query-busted origin URLs were fresh, but broad LinkedIn posting stays on hold.

Proof: live readback 10:35 PT Decision: direct routes first Risk: edge cache lag

Open cache readback

Claim boundary

What this supports and what it does not

This supports claims about Codex-assisted public routes, browser builds, QA hooks, discovery wiring, RSS/sitemap work, and deployment checks. It does not support traffic, revenue, ranking, client, certification, or external adoption claims.

Supported: shipped site systems Unsupported: metrics claims Use: profile-safe framing

Open proof map

LinkedIn Use

Where this belongs

Featured

Technical appendix for the proof card

Use the manifest behind the Featured proof-map link when the reader wants a compact route inventory and claim boundary instead of another narrative case page.

Featured receipt

Projects

Structured proof for shipped Aimaxin systems

Use the manifest as a supporting Projects link for AI systems, browser-game builds, publishing automation, QA, deployment, and public proof routing.

Systems proof

Public post

Hold broad posting until cache catches up

The direct manifest is strong profile proof, but the broader portfolio and discovery URLs should be fresh without query strings before using them as the anchor for a new public LinkedIn post.

Proof router