Store Onboarding

Purpose

Guide an eligible creator through the discovered store-application surface while distinguishing sampled operation from untested review branches.

Eligible Users and Roles

Authenticated creator applicants. Administrator review is Blocked without the port-3007 fixture.

Prerequisites

Use a synthetic creator account and synthetic documents only in an isolated local fixture. Do not upload real identity or bank evidence.

How to Open This Feature

Open the creator/store-registration entry available from the authenticated V6 workspace.

Step-by-Step Instructions

Step 1: Start or Resume the Application

Confirm whether the synthetic account has no application or an existing editable application.

Step 2: Enter Synthetic Information

Complete only fields whose current UI/server rules are visible. Do not infer legal or approval requirements.

Step 3: Save or Submit Once

Use a single bounded action and wait for the authoritative result before retrying.

Step 4: Verify the Saved State

Reload the application and confirm the server state. Admin approval/rejection/resubmission branches were not completed in this audit.

Verified mapping coverage preserves the canonical saved public description instead of dropping it during adaptation. This does not expand public eligibility: existing approval/publication rules remain authoritative.

Possible States

Draft or Editable

Source and sampled creator operation indicate an editable onboarding path.

Submitted or Under Review

Discovered in the application model; full browser state capture is Not Tested.

Approved, Rejected, Changes Requested, or Suspended

These branches must be verified with the isolated admin fixture before documentation claims exact behavior.

Sensitive Identity Unavailable

Server mutations must fail closed when protected historical identity material cannot be safely read; no real identity data was used.

Input Rules and Limits

Use current server constraints. Exact upload size/type, field-length, duplicate-submission, and Unicode matrices are Not Tested here.

Common Problems and Recovery

• On ambiguous submit, reload the authoritative application before retrying.
• Preserve draft work during session or network recovery where supported.
• Contact an authorized operator for review-state discrepancies; do not attempt privileged APIs.

Important Warnings

Identity, payout, and registration evidence is sensitive. Never capture it unredacted. Do not invent review states or approval rules.

What Happens Next

An approved creator may access the enabled workspace/product functions. Exact timing and notification behavior remain subject to verified business rules.