Business Pro Phase 247

Store Listing Asset Review Gate

Store listing visuals must look strong but stay honest. Every screenshot, icon, banner, and preview image must avoid private data, fake live payment claims, government/bank implication, and unapproved runtime promises.

Assets

review

Upload

Private data

blocked

Phase rule

Pretty assets still need proof

Phase 247 designs the store listing asset review gate only. It reviews icons, screenshots, feature graphics, preview images, captions, and visual disclaimers for a future store/public listing, without uploading assets, submitting to Google, creating a release build, publishing public pages, enabling accounts, activating payments, or claiming live runtime. No real contact, CRM task, account creation, onboarding approval, listing activation, order, payment, wallet, commission, ledger, export, or partner sync is created in this phase.

Review outcome

Approve visual asset set

Allow reviewed assets to move toward policy-link verification.

No store upload.

Review outcome

Request asset correction

Send weak or unsafe image/caption back for replacement.

No asset approval.

Review outcome

Quarantine risky asset

Hold screenshots or graphics that expose private, regulated, or misleading content.

No public use.

Review outcome

Reject asset set

Block the listing asset packet until visual truth and policy safety are fixed.

No next gate movement.

Asset types

What must be reviewed

App icon

Brand-safe icon that does not imply bank, government, hospital, police, or official state authority.

Phone screenshots

Mobile screens showing public demo, role entry, source-to-sale story, and safety labels without private data.

Feature graphic

Public banner that explains FAEDA simply without overclaiming wallet, job, payout, approval, or medical authority.

Captions

Short captions that describe visible features only and avoid promises not backed by approved package evidence.

Demo labels

Visual labels that clearly mark demo, preview, sandbox, Business Pro gated, partner-gated, and blocked states.

Support visuals

Screens or graphics showing help, complaint, consent, opt-out, and public safety paths.

Founder/admin visuals

Founder ERP screenshots must be public-safe, masked, and not expose internal/admin-only data.

Localized variants

Urdu or regional-language variants must match approved meaning and not soften safety disclaimers.

Visual safety checklist

Every asset must pass these checks

1No CNIC, phone number, address, OTP, bank detail, payment proof, medical content, child data, or exact private identity is visible.

2No screenshot shows real orders, real payouts, real wallet balance, real partner callback, real approval, or real verification unless the backend/runtime is approved later.

3No visual implies FAEDA is a bank, government body, hospital authority, guaranteed-income app, or licensed payment provider.

4Every payment, wallet, payout, credit, and settlement visual must show partner-gated or preview language where relevant.

5Screenshots must fit public mobile expectations and not hide critical demo/preview labels through cropping.

6Assets must be clear enough for Pakistani families, shopkeepers, suppliers, riders, and manufacturers to understand quickly.

7Founder/admin screenshots must be masked, synthetic, and explicitly demo-safe.

8Rejected assets must remain visible in the review record as rejected, not deleted silently.

Asset decision matrix

Visual state to next movement

All assets reviewed and safe

Move to Phase 248 policy-link verification

No upload yet

Screenshot exposes private data

Quarantine asset

No public use

Graphic overclaims wallet or payout

Return to metadata/copy correction

No asset approval

Admin visual leaks internal data

Mask or replace asset

No founder screenshot approval

Caption contradicts approved metadata

Return to Phase 246 metadata draft

No asset pass

Demo labels hidden by crop

Replace or recrop asset

No next movement

Localized asset changes meaning

Escalate language review

No listing asset approval

Asset packet

Future asset review fields

assetReviewIdmetadataDraftIdpackageIdcandidateVersionassetTypeassetNamesourceRoutecaptionlanguageprivateDataScanclaimSafetyStatemaskingStatedemoLabelStatedecisionreviewedByreviewedAt

Blocked automation

What this phase must not create

1Auto upload assets to Google

2Auto generate final app-store screenshots

3Auto approve icons, screenshots, banners, or captions

4Auto include screenshots with private data

5Auto crop away demo, preview, sandbox, or partner-gated labels

6Auto imply FAEDA is a bank, government body, hospital authority, job approval system, or licensed wallet

7Auto publish visual assets without policy-link verification

8Auto enable accounts, onboarding, orders, payments, wallets, payouts, or partner callbacks

Acceptance

Done means wired and safe

1Phase 246 links forward to Phase 247.

2Phase 247 defines store listing asset review gate without runtime mutation.

3Phase 247 is wired into OS launcher, founder navigation, public scope lock, route cleanup, and main chain control room.

4Mobile render has no horizontal overflow.

5No /home backlinks are introduced.

6Runtime contact, account, onboarding, listing, order, payment, wallet, commission, export, and partner sync stay blocked.

Back to Phase 246 Main chain room Open Phase 248