Lesson 05

Publish the proof, then test every perspective.

Use Aikarai Studio to freeze a truthful snapshot, process the package, publish a lane, and verify the public and claimant journeys.

Suggested time: 45–60 minutes
You will finish with: A public Build whose claims, package, lane, and Launch match what you actually tested.

Test before publication

Use a clean checkout and fresh browser state before describing the Build.

Builder: create, edit, reset, keyboard, mobile, and failure states.
Recipient: follow the README from a freshly extracted archive.
Visitor: understand function, maturity, requirements, source status, limitations, and offer without private context.

Publish through the real gates

Create the Build and version in Studio, attach processed media if used, upload the source ZIP, and wait for package state READY before publishing a FREE Copy.

Aikarai scans and processes uploaded source; it does not execute seller code.
Use truthful builder identity and measured build time.
Publish a Launch story that describes observed work, not invented traction.

Test after publication

Repeat the public flow against the exact published snapshot.

Anonymous visitor: Learn → Free Shelf → Build with no account/session side effects.
New account: verification email appears through the configured mail provider.
Claimer: FREE order creates the entitlement and Library access; no money moves.
Builder: Service request or Takeover entry appears only when that real lane is published and eligible.

Copy-ready starter prompt

Replace the bracketed details, give it to your coding agent, and keep the verification steps intact.

Prepare this project for a truthful Aikarai publication. Do not deploy externally.

Before publication, run the full builder, fresh-recipient, anonymous-visitor, and claimant journeys. Record desktop/390px/320px behavior, keyboard access, console errors, external requests, tests, build, secret scan, archive contents, and measured active build time.

Then provide the exact Studio field values, disclosures, limitations, package metadata, FREE Copy terms, and Launch story supported by that evidence. After publication, rerun Learn → Free Shelf → Build → claim → entitlement/Library and any real Service or Takeover path. Clearly separate verified results from anything not tested.

Learn pages are public and anonymous. They do not create an account, a session, analytics, or marketplace activity.