Phase 217

Public Lead Capture Approval Gate

A design gate for safe public interest capture after role entry, without pretending that FAEDA has opened live onboarding.

Role entryScope lock

Lead gate decision

Interest capture must not become fake onboarding

FAEDA can collect public demand and business interest later, but only with consent, minimum fields, review queues, and clear blocked claims.

Phase boundary

Approval design, not live form

Phase 217 approves the design for public lead capture only. It does not create a live form, submit leads, create accounts, verify CNIC, approve shops, approve suppliers, onboard riders, activate Business Pro, collect payments, create wallet balances, or mutate production data.

Lead types

6

Live submit

0

Unsafe data

0

Approved lead categories

review first

Customer / Family

Customer interest

Waitlist only

A family wants to know when FAEDA is available in their area or wants a safe demo basket walkthrough.

Allowed future fields

Name or nicknameCity/areaOptional phone or WhatsAppInterest categoryConsent checkbox

Forbidden in public lead

CNICBank detailsExact home addressMedical dataPayment method

Review route

Customer success

Customer portal/auth approval later

Retailer / Shopkeeper

Shop listing interest

Lead only

A shop wants FAEDA team to review whether it can be listed after verification.

Allowed future fields

Shop nameShop categoryCity/areaOwner contactPhoto optional after consent

Forbidden in public lead

Live listing claimCustomer payment linkSupplier costsTax passwordBank login

Review route

FAEDA Team

Shop verification and listing approval gate

Raw Material Supplier

Raw supplier interest

Source lead

A supplier wants to show material source, grade, and availability to future manufacturers.

Allowed future fields

Supplier nameMaterial categoryOrigin typeCity/areaContact person

Forbidden in public lead

Invoice uploadSettlement accountPayment referenceStock ledgerImport credentials

Review route

Supplier ops

Supplier invite and source evidence gate

Manufacturer

Manufacturer Business Pro interest

ERP inquiry

A factory wants FAEDA Business Pro preview for material needs, capacity, products, payroll, or full ERP later.

Allowed future fields

Factory nameProduct categoryWorker rangeCity/areaBusiness contact

Forbidden in public lead

Payroll fileMachine accessBank detailsWorker CNIC listProduction secrets

Review route

Business Pro sales

Manufacturer source map and Business Pro upgrade review

Rider / Logistics Provider

Rider or logistics interest

Logistics lead

A rider, pickup partner, local transporter, or delivery group wants to join future delivery coverage.

Allowed future fields

NameVehicle typeCity/areaContactAvailability window

Forbidden in public lead

CNIC imageLicense imageBank accountLive route claimPayout account

Review route

Logistics ops

Rider verification and dispatch approval gate

Founder / Partner

Founder, investor, or partner inquiry

Reviewed inquiry

A serious partner wants a controlled founder demo, franchise discussion, or payment/legal partnership review.

Allowed future fields

NameOrganizationRoleContactPurpose of inquiry

Forbidden in public lead

Investment transferPayment credentialsAdmin requestLegal commitmentProduction data export

Review route

Founder office

Founder review and partner due-diligence gate

Approval flow

How a public lead becomes reviewable later

Step 01 - Public UX

Public intent chosen

Visitor arrives from Phase 216 role entry and chooses the type of interest they want to express.

Step 02 - Privacy

Consent and minimization

The future form must ask only minimum fields and show why each field is needed before any submission exists.

Step 03 - Lead ops

Safe lead packet

Lead packet remains pending, review-only, and non-operational. It cannot create account, listing, payment, or onboarding truth.

Step 04 - Trust ops

Duplicate and risk review

FAEDA checks spam, duplicate phone, suspicious category, unsafe request, and fake business claims before routing.

Step 05 - FAEDA Team

Role queue routing

Customer, shop, supplier, manufacturer, rider, or partner lead goes to the correct human review queue.

Step 06 - Founder approval

Later onboarding gate

Only a later approved runtime phase may convert a lead into real auth, profile, listing, supplier, rider, ERP, or partner record.

Consent rules

Minimum data, clear permission

1Every public lead must explain what FAEDA will do with the submitted contact.
2Marketing opt-in must be separate from operational follow-up consent.
3A visitor must know that this is interest capture, not account approval.
4A visitor must not be asked for CNIC, passwords, bank details, wallet keys, medical data, or precise address in this gate.
5All future submissions must carry source route, role intent, timestamp, consent version, language, and request id.
6Backend validation remains final authority when runtime is approved later.

Future packet shape

What a safe lead record may contain later

leadType

customer | shop | supplier | manufacturer | rider | partner

sourceRoute

/business-pro/role-entry-ux-public-visitors

safeStatus

draft-design | pending-review later

contactConsent

required before future submit

marketingConsent

optional and separate

riskFlags

duplicate, spam, unsafe-data, regulated-claim

reviewQueue

customer-success, FAEDA-team, supplier-ops, sales, logistics, founder-office

Blocked public claims

Lead capture must never say this

1Your account is created
2Your shop is live
3Your supplier profile is approved
4Your rider payout is enabled
5Your factory ERP is active
6Your wallet is ready
7Payment is successful
8CNIC verified
9Admin will approve instantly
10FAEDA guarantees orders

Acceptance checklist

Definition of public lead capture approval

1Phase 216 links forward to Phase 217.
2Phase 217 defines lead types for customer, shop, supplier, manufacturer, rider, and founder/partner.
3Each lead type lists allowed fields, forbidden fields, review owner, and next gate.
4Page clearly states no live form, no lead submission, no account, no CNIC verification, no payment, no wallet, and no production mutation.
5Public scope lock and route cleanup include Phase 217.
6OS launcher, founder navigation, and main chain control room include Phase 217.
7Mobile render has no horizontal overflow.
8No `/home` backlinks are introduced.

Next phase

Phase 218: Consent-Safe Lead Form Design

Next we design the non-submitting public lead form shell, field states, consent copy, errors, and review labels before any backend write exists.

Open Phase 218
Phase 216 Phase 218 Chain room