Business source
Raw Material Supplier
A supplier registers material and answers manufacturer RFQs without creating payment or inventory truth.
Phase 152Founder ERP webRole registry powered
FAEDA Founder ERP Command Center
Full web control for Business Pro: role surfaces, source-to-sale chain health, product truth, logistics, payment ops, trust evidence, exceptions, and founder approvals without fake wallet or inventory claims.
Role surfaces
7
supplier to founder
Guarded actions
13
backend guarded
Support rails
5
product, logistics, finance, trust, team
Runtime leaks
0
wallet/payment stays gated
Phase 202 role clarity
Who am I, what I own, what I can safely do
Logged in as Founder / Admin Ops. This role owns chain health, exception review, payment evidence, release decisions, role readiness, and escalation visibility.
What I can safely do
Review exceptionsOpen role dashboardsPrepare partner payment draftReview source-to-sale blockers
What is blocked
Silent overrideAuto payoutFake ledgerUnlicensed wallet
Where the next handoff goes
Founder hands work back to the right operator: supplier, manufacturer, wholesaler, retailer, customer, rider, payment ops, or trust governance.
ERP modules
web commandactive
FAEDA Core Spine
Main connected source-to-customer operating map: supplier, manufacturer, wholesaler, shop, customer, logistics, partner payment, and founder control.
active
Customer-Shop Spine
Complete daily buying loop: nearby discovery, shop trust, product truth, basket, inquiry, quote, order draft, reservation, partner payment readiness, handover proof, statement, and support.
active
Customer-Shop Functional Flow
Touchable mobile demo where customer builds basket, sends inquiry, shop responds, and customer accepts an order draft candidate while payment/inventory/settlement stay locked.
active
Shop Request Inbox
Shopkeeper workbench for reviewing customer inquiry drafts, sending seller-response packets, tracking order draft candidates, and preserving payment/inventory/dispatch locks.
active
Customer Decision Hub
Customer workbench for reviewing seller response, asking revision, rejecting, or accepting into an order draft candidate while final order/payment/runtime gates stay locked.
active
Customer Order Confirmation
Customer workbench for confirming an accepted draft into ORDER_CONFIRMATION evidence only while stock, payment, dispatch, ledger, wallet, and payout remain gated.
active
Shop Stock Reservation
Shopkeeper workbench for holding stock in an evidence packet after customer confirmation while inventory ledger, payment, dispatch, wallet, and payout remain gated.
active
Partner Payment Intent
Customer/payer workbench for preparing an Upaisa/SBP partner payment intent packet after stock hold without real execution, callback, wallet, ledger, or payout.
new
Role Switcher
One founder/operator view of every FAEDA Business Pro role, dashboard, workbench, truth, and risk.
new
Founder Demo Journey
Five-minute source-to-sale story from supplier truth to customer demand and partner-gated payment ops.
new
Demo Seed Journey
Concrete seed story: polymer source to button manufacturer, wholesale, retail, customer demand, rider proof, and Upaisa evidence gate.
new
Demo Seed Data Pack
Portable seed pack shape with import order, stable keys, record groups, relationship edges, JSON envelope, and locked runtime mutations.
new
Demo Seed Dry-Run Validator
No-write validator for seed pack scope, schema, dependencies, idempotency, permission requirements, mutation locks, and audit report shape.
new
Seed Import Readiness Report Desk
Evidence-only desk for reviewing dry-run reports, decisions, audit notes, blocked scenarios, and next safe gates without importing records.
new
Seed Import Approval Design Gate
Maker-checker gate for approving importer design discovery only, with no importer build, run, schedule, or runtime write authority.
new
Importer Technical Design Documentation
Documentation-only architecture for future seed importer, no services, APIs, workers, queues, migrations, or database writers.
new
Role Functional Readiness Sprint
Phases 161-170 in one controlled sprint: scope review, role QA, demo personas, permissions, dashboards, workbenches, seed binding, and functional-lite readiness.
new
Role Demo Credential Shell
Phase 171 demo-only persona launcher for Supplier, Manufacturer, Wholesaler, Retailer, Customer, Rider, and Founder/Admin with no production auth claim.
new
Role Route Smoke Test Board
Phase 172 founder and QA board for checking all role dashboards, workbenches, primary routes, mobile fit, and blocked mutation boundaries.
new
Role UX Correction Backlog
Phase 173 founder and QA backlog for fixing weak UX, mobile fit, route labels, role clarity, and unsafe wording found during smoke testing.
new
Role QA Evidence Capture Desk
Phase 174 manual evidence desk for screenshot references, reviewer notes, route status, decisions, and correction proof without file storage or backend writes.
new
Evidence Storage Permission Design Gate
Phase 175 design gate for evidence upload, view, redact, retain, approve, export, delete, and restore permissions before storage exists.
new
Evidence Data Contract Design
Phase 176 schema-first design for evidence metadata, storage references, audit fields, redaction markers, review decisions, and retention signals before storage exists.
new
Evidence Storage Provider Boundary Design
Phase 177 provider-boundary design for aliases, encryption, signed-view policy, retention, quarantine, and forbidden data blocks before storage exists.
new
Evidence Upload Flow Approval Design
Phase 178 approval workflow for request, scope, contract validation, preflight scan, redaction, maker-checker, provider instruction, and audit before uploads exist.
new
Evidence Review Queue Workflow Design
Phase 179 review queue design for reviewer assignment, aging, escalation, decision lanes, correction loops, and audit status before queue services exist.
new
Evidence Correction Closure Packet Design
Phase 180 correction closure design for correction requests, fix proof, reviewer verification, closure decisions, reopen triggers, and audit packets before ticket or queue services exist.
new
Evidence Review Reporting Dashboard Design
Phase 181 privacy-safe reporting design for queue health, closure health, stale evidence, reopen trends, reviewer load, escalation pressure, and founder visibility before reporting APIs exist.
new
Evidence Reporting Export Policy Design
Phase 182 export policy design for permissions, redaction rules, allowed and blocked formats, signed report access, retention, and audit trail before export APIs exist.
new
Evidence External Auditor Access Design
Phase 183 external auditor access design for auditor identity, scoped report access, approval gates, redacted evidence views, revocation, and audit logs before auditor runtime exists.
new
Evidence Audit Retention Register Design
Phase 184 retention register design for retention lanes, lifecycle states, access windows, legal holds, tombstones, actor permissions, reporting views, and audit fields before retention runtime exists.
new
Evidence Audit Exception Review Design
Phase 185 exception review design for retention conflicts, expired-but-held records, missing approvals, risky lifecycle transitions, proposed outcomes, closure packet fields, and reviewer roles before exception runtime exists.
new
Evidence Audit Closure Governance Design
Phase 186 closure governance design for checker decisions, closure proof, reopen triggers, final audit review, actor boundaries, closure reports, and runtime approval readiness before closure runtime exists.
new
Evidence Audit Runtime Build Approval Gate Design
Phase 187 runtime build approval design for founder, data protection, security, backend, storage, RBAC, QA, and sandbox gates before evidence runtime is built.
new
Evidence Runtime Local Stub Readiness Design
Phase 188 Defines how FAEDA may create disabled local evidence stubs without persistence, provider writes, queues, workers, notifications, exports, or live user impact.
new
Evidence Runtime Feature Flag + Kill Switch Design
Phase 189 Defines disabled-by-default flags, role scope, zone scope, emergency stop, rollback levels, and audit visibility before evidence runtime can be exposed.
new
Evidence Metadata Database Schema Approval Design
Phase 190 Defines future evidence metadata tables, indexes, retention links, privacy classes, audit ids, and rollback conditions before any migration is created.
new
Evidence API Contract Approval Design
Phase 191 Defines future API boundaries for upload request, preflight, review queue, redaction, signed view, closure, export request, and audit events before routes exist.
new
Evidence Storage Adapter Sandbox Design
Phase 192 Defines how sandbox storage adapters can be tested with provider aliases, fake files, quarantine, encryption settings, signed view mocks, and no production object writes.
new
Evidence Upload Preflight Stub Design
Phase 193 Defines future upload preflight checks for scope, size, MIME type, privacy class, redaction need, scan status, retention lane, maker role, and duplicate detection before upload runtime exists.
new
Evidence Review Queue Local Stub Design
Phase 194 Defines a local-only review queue stub for assignment lanes, aging, severity, escalation, redaction return, correction loops, and no worker-backed mutation.
new
Evidence Audit Event Writer Stub Design
Phase 195 Defines append-only audit event shape, event categories, request ids, actor scope, before/after summaries, failure events, and no production log writes.
new
Evidence Permission Enforcement Test Matrix
Phase 196 Defines negative and positive permission tests for uploader, reviewer, checker, founder, support, auditor, data protection, security, and ops roles before runtime exposure.
new
Evidence Sandbox Runtime Dry-Run Validator
Phase 197 Defines no-write validation for sandbox evidence flows: upload preflight, storage mock, review queue, audit event, permission matrix, export block, and rollback checks.
new
Evidence Runtime Security + Privacy QA Gate
Phase 198 Defines security, privacy, redaction, consent, storage, secrets, audit, abuse, rate-limit, and incident-response checks before any controlled pilot.
new
Evidence Runtime Pilot Approval Packet
Phase 199 Defines the controlled pilot packet for allowed roles, allowed evidence classes, sandbox-to-pilot boundary, support plan, rollback, monitoring, manual override, and founder approval.
new
Evidence Runtime Founder Release Control Room
Phase 200 Defines the founder-facing release control room for runtime status, flags, kill switches, approvals, pilot health, incidents, blocked shortcuts, QA evidence, and final release decisions.
new
Core Operating Flow Resume Gate
Phase 201 closes the evidence branch and returns FAEDA to supplier, manufacturer, wholesaler, retailer, customer, rider, and founder operating flow.
new
Role Landing Clarity Sweep
Phase 202 makes every role landing answer who I am, what I own, what I can safely do, what is blocked, and where the next handoff goes.
new
Source-to-Sale Demo Journey QA
Phase 203 proves one founder-ready raw material to customer demand story with evidence packets, pass checks, and blocked fake runtime claims.
new
Mobile-First Role Dashboard Fit Check
Phase 204 verifies every role dashboard can be understood on a phone with clear actions, visible locks, and no horizontal spill or fake runtime claims.
new
Backend Action Boundary Audit
Phase 205 classifies every Business Pro workbench action as backend guarded, preview-only, partner-gated, or blocked before deeper runtime is added.
new
Workbench Submit-State + API Error Contract QA
Phase 206 verifies shared workbench submit states, API error display, preview-only behavior, partner-draft wording, and stable QA metadata before automated smoke tests.
new
Role Workbench Automated Smoke Test Matrix
Phase 207 converts Phase 206 DOM hooks into role-by-role smoke-test cases, safe click rules, mobile overflow checks, preview-only checks, partner-gated checks, and blocked success claims.
new
Workbench Smoke Runner Technical Design
Phase 208 designs the future smoke runner architecture, execution lanes, report schema, fail-fast policy, and sandbox approval requirements without creating tests, CI jobs, or runtime mutations.
new
Sandbox Auth, Fixture, and Safe Test Account Approval Gate
Phase 209 approves sandbox tenant rules, role test-account aliases, fixture labels, permission bands, secret custody, cleanup, and review gates before authenticated smoke tests can exist.
new
Public-Demo Readiness Board
Phase 210 decides what FAEDA can safely show publicly, what must remain internal, and what blocks Google or public upload before the final 5-day release track.
new
Public Scope Lock
Phase 211 freezes public routes, role paths, demo data, claims, CTAs, and hard-stop boundaries before route cleanup and public navigation repair.
new
Route Cleanup and Public Navigation Repair
Phase 212 locks public route map, removes old home-link patterns, separates public CTAs from internal ops, and prepares first screen polish.
new
Public Home and First Screen Polish
Phase 213 polishes the public home with safe demo CTAs, source-chain clarity, mobile-first copy, and no real wallet/order/payment claims.
new
Demo Mode Guard
Phase 214 makes demo, preview, sandbox, partner-gated, and blocked states visible so public viewers do not mistake sample data for live transactions.
new
Source-to-Sale Public Demo Flow
Phase 215 turns verified supply to household demand into a public-safe walkthrough with demo labels, blocked claims, and role handoffs.
new
Role Entry UX for Public Visitors
Phase 216 turns public interest into safe role-choice paths for customer, shop, supplier, manufacturer, rider, and founder/admin without live account or payment claims.
new
Public Lead Capture Approval Gate
Phase 217 defines safe public lead categories, consent rules, forbidden fields, review owners, and later onboarding gates without a live form submission.
new
Consent-Safe Lead Form Design
Phase 218 defines the non-submitting public lead form shell, field states, consent copy, sensitive-data blocks, and future packet preview before backend writes exist.
new
Public Lead Review Queue Design
Phase 219 defines the human review queue blueprint for consent-safe public lead packets, privacy masking, duplicate checks, role routing, and blocked operational actions before lead runtime exists.
new
Lead Triage Decision Policy
Phase 220 defines when future public lead packets can be rejected safely, corrected, held for consent, routed, escalated, or marked review-ready without live mutation.
new
Lead Assignment Approval Gate
Phase 221 defines when future reviewed lead packets may be approved for safe role-lane ownership without contact, CRM, account creation, onboarding, payment, wallet, commission, or partner sync.
new
Lead Contact Permission Gate
Phase 222 defines whether a future assigned public lead may be contacted by a specific channel, script, time window, and consent state without sending calls, messages, CRM tasks, or field visits.
new
Lead Follow-Up Outcome Review Gate
Phase 223 A response like interested, not reached, wrong number, or opted out can be reviewed later, but it must not become account truth, sales truth, or onboarding truth by itself.
new
Lead Contact Script Template Approval Gate
Phase 224 Every future contact must use a founder/legal/privacy-approved script shape so FAEDA does not sound like a bank, government body, fake job agent, or pressure-sales team.
new
Lead Contact Attempt Evidence Register
Phase 225 FAEDA should know that a permitted attempt happened, but it should not store full private call transcripts, WhatsApp screenshots, or sensitive personal details by default.
new
Opt-Out / Do-Not-Contact Register
Phase 226 If someone opts out, FAEDA must respect it across phone, SMS, WhatsApp, email, in-app, and FAEDA Team assisted follow-up surfaces.
new
Lead Conversion Candidate Gate
Phase 227 A serious lead may become a candidate for onboarding, but FAEDA still needs role-specific invitation, packet review, verification, and backend approval.
new
Role Onboarding Invitation Gate
Phase 228 An onboarding invitation should explain the role path, required information, privacy, and demo/current status without implying approval or live earning.
new
Role Onboarding Packet Review Gate
Phase 229 The onboarding packet is a joining file. It can be reviewed, corrected, held, or rejected before FAEDA creates actual role identity.
new
Public Onboarding Readiness Board
Phase 230 Before opening public onboarding, FAEDA needs a board that shows which role flows are safe enough for demo, beta, or live build approval.
new
Demo-to-Lead Analytics Safety Dashboard
Phase 231 Founder needs to see what public visitors care about, but not raw private lead content, contact details, or sensitive messages.
new
Public Trust / FAQ / Safety Page
Phase 232 Pakistani users need simple answers: what FAEDA is, what is demo, what is partner-gated, how privacy works, and how to report problems.
new
Public Feedback & Complaint Intake Gate
Phase 233 If someone receives a fake FAEDA call, sees unsafe wording, or finds wrong public information, the public surface needs a clear reporting gate.
new
Public Privacy / Terms / Consent Surface
Phase 234 Before public upload, FAEDA must show privacy, terms, consent, contact rules, demo status, and partner payment boundaries clearly.
new
Public Upload Readiness Checklist
Phase 235 Before Google/public upload, FAEDA needs a strict checklist for routes, mobile fit, wording, demo labels, privacy, contact safety, and fake runtime prevention.
new
Production Env & Secret Readiness Gate
Phase 236 Before public upload, FAEDA needs a gate that confirms env variables, public config, secrets, provider keys, and local-only assumptions are clean.
new
Domain / SEO / Metadata / Performance Pass
Phase 237 FAEDA needs clear titles, descriptions, social previews, icons, mobile speed, and search-safe wording before public upload.
new
Public QA Smoke Matrix
Phase 238 Every public route should be checked for load, mobile fit, wording, route links, demo labels, contact safety, and no fake runtime claims.
new
Founder Go / No-Go Launch Board
Phase 239 A founder board should show what is ready, risky, blocked, and deferred before FAEDA freezes a public launch candidate.
new
Public Launch Candidate Freeze
Phase 240 After freeze, FAEDA should stop adding new public features and only accept bug fixes, copy safety fixes, claim corrections, accessibility fixes, and security fixes.
new
Post-Freeze Bugfix Control Gate
Phase 241 After Phase 240, FAEDA should behave like a release candidate: every change must be a verified fix, must name its evidence, must avoid feature drift, and must be reviewable by founder/QA/security where needed.
new
Post-Freeze Regression Replay Gate
Phase 242 After a post-freeze fix, FAEDA must replay the affected routes plus key public journey gates so a mobile fix, wording fix, or safety correction does not quietly break another part of the public launch candidate.
new
Launch Candidate Evidence Sign-Off Gate
Phase 243 After regression replay, FAEDA needs a human sign-off layer that says the evidence is complete enough to assemble a public upload package. This is not store submission and not public release.
new
Public Upload Package Assembly Gate
Phase 244 After evidence sign-off, FAEDA needs a clean public-upload package draft: route list, screenshots, claims, policy notes, demo labels, payment disclaimers, support paths, and risks. This is assembly for review, not public release.
new
Public Upload Package Final Review Gate
Phase 245 The assembled package now needs one last human review pass across product, QA, security, privacy, payment/legal, support, and founder scope. Passing this gate means the package can move to store-listing draft work, not public upload.
new
Store Listing Metadata Draft Gate
Phase 246 After final package review, FAEDA can draft public listing metadata. The metadata must explain FAEDA clearly while staying truthful: demo-safe, partner-gated, consent-first, and no fake wallet, bank, job, government, hospital, order, or payout promise.
new
Store Listing Asset Review Gate
Phase 247 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.
new
Store Listing Policy Link Verification Gate
Phase 248 A public store listing is not safe just because it looks polished. Every claim must have a visible, working, approved policy or support path so customers, shops, riders, suppliers, and manufacturers know what FAEDA is and what it is not.
new
Store Listing Final Compliance Review Gate
Phase 249 Before FAEDA moves toward a public store submission, the whole listing package must be reviewed as one truth bundle: words, screenshots, policy exits, support routes, payment wording, privacy, and founder approval all have to agree.
new
Store Listing Manual Submission Approval Gate
Phase 250 After final compliance review, FAEDA still needs a maker-checker approval before any human opens the store console. This gate locks the authorized submitter, candidate version, release track, evidence expectations, and founder hold power without performing the upload itself.
new
Store Submission Evidence Capture Gate
Phase 251 If a human submits the FAEDA package later, FAEDA needs a clean evidence packet showing exactly what was submitted, by whom, when, to which track, and what the console said. That evidence must not include secrets or become a fake public-launch claim.
new
Store Review Status Monitoring Gate
Phase 252 After a manual submission attempt, FAEDA needs a calm review board that separates store-console status from public-launch truth. In review, rejected, approved, and published are evidence states that must be checked, timestamped, and routed without turning into unsafe runtime activation.
new
Store Rejection / Changes Required Evidence Gate
Phase 253 When a store requests changes, FAEDA must preserve the truth, protect secrets, classify the issue, assign correction ownership, and prevent rushed resubmission. The aim is disciplined recovery: no panic edits, no fake approval claims, no lost evidence.
new
Store Approval Evidence Gate
Phase 254 A store approval signal is important, but it is only one controlled proof point. FAEDA still needs a separate public availability check to confirm real users can find, install, open, and safely use the correct build without exposing disabled or regulated flows.
new
Public Availability Verification Gate
Phase 255 A public or tester-facing store page proves visibility, not full readiness. FAEDA must verify the correct listing, country/track scope, version, install button state, screenshots, policy links, and release notes before moving to real-device install smoke testing.
new
First Install Device Smoke QA Gate
Phase 256 A controlled install proves the store package can reach a device. It still does not prove app opening, login, permissions, backend runtime, role flows, orders, payments, support, or public rollout. FAEDA must record device, version, source, install result, and evidence before moving to first app-open smoke QA.
new
First App Open Runtime Smoke QA Gate
Phase 257 Opening the installed app proves only the first runtime boundary: launch, splash, first screen, environment label, crash state, and safe visible claims. FAEDA still needs separate gates for permission prompts, auth entry, role selection, backend connectivity, support, orders, payments, wallets, and public launch.
new
First Screen Permission Prompt QA Gate
Phase 258 A first-screen permission prompt can protect or damage trust. FAEDA must prove that camera, location, notifications, Bluetooth, contacts, microphone, storage, tracking, and health prompts are delayed, explained, optional where possible, and safe before any auth, role, order, payment, wallet, or public rollout path is tested.
new
Auth Entry Boundary QA Gate
Phase 259 The first auth surface must be checked before any credential is typed. FAEDA needs proof that users understand whether they are entering as customer, shop, supplier, rider, FAEDA Team, founder, or guest, and that the screen does not pretend wallets, jobs, payments, bank rails, or live onboarding are ready.
new
OTP Request Boundary QA Gate
Phase 260 Before FAEDA can send any OTP, the request screen must prove why the contact is needed, which channel will be used, what country or region is supported, what rate-limit and privacy rules apply, and what safe exit exists. Seeing an OTP request form does not prove delivery, verification, login, wallet, payment, or onboarding.
new
OTP Verification Boundary QA Gate
Phase 261 The verification screen must prove the user understands what OTP is being checked, how long it remains valid, how retries work, how mistakes are handled, and how to go back safely. Seeing an OTP verification surface does not prove the code was delivered, verified, sessionized, permissioned, or connected to wallet/payment/onboarding.
new
Session Creation Boundary QA Gate
Phase 262 After OTP verification, FAEDA needs a controlled boundary before any session, cookie, token, account shell, or role dashboard appears. This phase proves the transition is honest: verified contact does not equal approved role, KYC, wallet, payment, shop listing, rider job, supplier account, or founder/admin access.
new
Authenticated Shell Boundary QA Gate
Phase 263 The first authenticated shell must behave like a guarded frame around future role-specific work. It may show safe navigation, pending setup, limited account state, and help exits, but it must not pretend the user has approved roles, live shop powers, wallet powers, payment powers, order powers, or founder/admin authority.
new
Role Routing Boundary QA Gate
Phase 264 FAEDA can show where a user may go next only if the route clearly says what is approved, pending, unavailable, demo-only, or requires review. A role card, role switcher, or route button must not become hidden approval for shop powers, supplier powers, rider jobs, wallet, payment, order access, or founder/admin access.
new
Customer Role Boundary QA Gate
Phase 265 A person may enter FAEDA as a customer to discover nearby supply and understand value, but the app must not quietly turn that public entry into access to wallet, orders, saved family details, saved addresses, payment methods, support tickets, or household data. Every private action stays behind explicit auth, consent, permission, and backend scope.
new
Shopkeeper Role Boundary QA Gate
Phase 266 A person may say they run a shop, but FAEDA must not treat that as verified shop ownership, public listing approval, POS activation, settlement readiness, inventory truth, delivery hub approval, or Business Pro subscription. Shopkeeper power begins only after business verification, permission checks, and later operational gates pass.
new
Supplier Role Boundary QA Gate
Phase 267 A person or business may claim they supply raw material, packaging, machinery, spare parts, chemicals, fabric, food inputs, farm inputs, or services, but FAEDA must not treat that as verified supply truth. Supplier power begins only after source verification, material identity checks, compliance review, RFQ gates, purchase gates, dispatch gates, and payment partner controls pass.
new
Manufacturer Role Boundary QA Gate
Phase 268 A business may claim it makes garments, buttons, zippers, food, furniture, chemicals, packaging, machinery, or any other product, but FAEDA must not treat that claim as verified factory truth. Manufacturer power begins only after factory verification, product-source mapping, raw-material links, capacity checks, compliance review, production gates, inventory gates, and Business Pro approvals pass.
new
Wholesaler Role Boundary QA Gate
Phase 269 A business may claim it buys from manufacturers and supplies retailers, restaurants, shops, institutions, exporters, or street networks, but FAEDA must not treat that claim as verified distribution truth. Wholesaler power begins only after depot verification, source links, purchase records, GRN/stock gates, allocation gates, pricing controls, dispatch evidence, and payment/accounting approvals pass.
new
Retailer Role Boundary QA Gate
Phase 270 A shop may claim it sells groceries, medicine, furniture, clothes, meat, hardware, electronics, food, services, or any local product, but FAEDA must not treat that as verified retail truth. Retailer power begins only after shop verification, product identity mapping, source links, availability checks, price controls, order gates, delivery gates, and payment/accounting approvals pass.
new
Street Vendor Role Boundary QA Gate
Phase 271 A thela, cart, stall, hawker, fruit seller, sabzi seller, chaat/pakora seller, chai seller, milk seller, mobile repair stall, or roaming service provider may be visible in a street today, but FAEDA must not treat that as verified vendor, verified location, verified freshness, verified stock, or guaranteed delivery without later checks.
new
Home Chef Role Boundary QA Gate
Phase 272 A home cook, cloud kitchen, tiffin maker, bakery-from-home, catering aunty, student meal seller, Ramadan iftar seller, frozen-food maker, or family kitchen may want to sell, but FAEDA must not treat that as verified food safety, verified halal handling, verified kitchen capacity, or live customer order readiness without later checks.
new
Farmer Role Boundary QA Gate
Phase 273 A kisaan, dairy farmer, poultry farmer, fish farmer, orchard owner, vegetable grower, grain grower, livestock seller, nursery grower, or village aggregator may be the original source, but FAEDA must not treat that as verified land, verified crop, verified quantity, verified grade, pesticide-safe produce, or guaranteed pickup without later checks.
new
Rider Role Boundary QA Gate
Phase 274 A biker, cyclist, walker, loader, van driver, pickup driver, rickshaw driver, cold-chain courier, intercity transport helper, or neighborhood runner may want delivery work, but FAEDA must not treat that as verified identity, verified vehicle, safe route, COD authority, live tracking permission, or payout readiness without later checks.
new
FAEDA Team Role Boundary QA Gate
Phase 275 A FAEDA Team member, onboarding agent, support helper, field verifier, delivery support, shop digitizer, rural assistant, or training guide may help people use FAEDA, but must not gain uncontrolled access to private data, approvals, payments, wallets, listings, orders, verification, or admin controls without explicit scoped permission and audit.
new
Zone Manager Role Boundary QA Gate
Phase 276 A Zone Manager may supervise city, tehsil, union council, village, bazar, shop cluster, FAEDA Team work, and local onboarding health, but must not become a hidden founder/admin, payment operator, verifier, support closer, or unrestricted data viewer without explicit scoped approval and audit.
new
Admin Role Boundary QA Gate
Phase 277 An admin may operate a bounded workbench after approval, but FAEDA must not treat admin as founder, bank operator, payment partner, security owner, data owner, or final truth authority without explicit role scope, maker-checker controls, audit trails, and founder-level review where needed.
new
Founder Role Boundary QA Gate
Phase 278 The founder can hold the highest product and governance responsibility, but FAEDA must still keep evidence, audit, legal, security, partner payment rails, consent, data protection, and role permissions intact. Founder authority is a release and governance lane, not a license to rewrite operational truth.
new
Investor Role Boundary QA Gate
Phase 279 An investor may later review approved opportunities, risk disclosures, performance summaries, and governance reports, but FAEDA must not imply guaranteed profit, ownership, voting rights, payout readiness, wallet authority, or operational control without legal, finance, compliance, and founder-approved gates.
new
Partner Role Boundary QA Gate
Phase 280 A partner may later represent a licensed payment rail, logistics network, verification vendor, cloud provider, bank, insurer, telco, compliance body, exporter agent, or local service provider, but FAEDA must not imply live integration, regulatory approval, credential issuance, settlement authority, or private data sharing without contract, compliance, security, and founder-approved gates.
new
Regulator Role Boundary QA Gate
Phase 281 A regulator may later receive lawful, purpose-scoped, masked, and approved reports for SBP/payment partner coordination, tax, labor, food safety, commerce, export, municipal, health, telecom, data protection, or consumer protection matters, but FAEDA must not imply official approval, government partnership, direct enforcement power, or unrestricted data sharing from this design route.
new
Auditor Role Boundary QA Gate
Phase 282 An auditor may later inspect founder-approved, role-scoped, masked, immutable evidence for finance, payment, inventory, supplier, manufacturer, shop, customer, compliance, privacy, security, or launch-readiness reviews, but FAEDA must not let the auditor mutate business truth, bypass permissions, export raw private data, or treat review access as operational authority.
new
Compliance Officer Role Boundary QA Gate
Phase 283 A compliance officer may later review whether FAEDA workflows follow approved policy, consent, payment-partner, privacy, customer-safety, role-boundary, store-listing, and launch-readiness controls, but this route must not turn compliance into legal counsel, regulator, auditor, founder, admin, payment-ops, or operations authority.
new
Legal Counsel Role Boundary QA Gate
Phase 284 Legal counsel may later review contracts, terms, privacy language, regulated claims, disputes, notices, partner agreements, investor documents, employment language, marketplace rules, and launch-risk memos, but this route must not treat legal review as signed authority, public approval, payment authority, operational control, or a shortcut around founder/governance gates.
new
Finance Officer Role Boundary QA Gate
Phase 285 A finance officer may later review budgets, payables, receivables, invoices, COD, commissions, supplier balances, shop/rider balances, partner receivables, platform fees, reports, and exceptions, but this route must not become payment execution, wallet custody, ledger override, tax filing, settlement finality, or unrestricted financial disclosure.
new
Payment Operations Role Boundary QA Gate
Phase 286 Payment operations may later prepare partner-powered execution drafts, queue records, callback evidence, retry reviews, reversal reviews, and payment exception packets, but this route must not become real money movement, wallet custody, callback finality, ledger posting, settlement finality, or uncontrolled partner access.
new
Settlement Officer Role Boundary QA Gate
Phase 287 A settlement officer may later review matched evidence and prepare release or hold decisions, but the settlement surface must not become payment execution, wallet truth, ledger truth, reconciliation closure, or custody claim.
new
Reconciliation Officer Role Boundary QA Gate
Phase 288 A reconciliation officer may later compare order, payment, callback, settlement, statement, invoice, GRN, COD, and ledger evidence, but this route must not become final accounting truth, settlement authority, payment authority, or custody proof.
new
Ledger Controller Role Boundary QA Gate
Phase 289 A ledger controller may later review whether evidence is eligible for accounting entry, reversal, adjustment, or period-close preparation, but this route must not become actual posting, settlement release, payment execution, wallet balance, bank custody, or reconciliation closure.
new
Treasury Officer Role Boundary QA Gate
Phase 290 A treasury officer may later review bank, cash, partner, COD, funding, and float evidence, but this route must not become money movement, custody proof, wallet licensing, payout authority, refund authority, secret access, or ledger finality.
new
Cash Custody Officer Role Boundary QA Gate
Phase 291 A cash custody officer may later review cash packet evidence, COD handoffs, deposit proofs, count sheets, and shortage/overage claims, but this route must not become real cash acceptance, bank deposit truth, wallet balance, COD settlement, ledger posting, or treasury authority.
new
Bank Operations Officer Role Boundary QA Gate
Phase 292 A bank operations officer may later review statement rows, bank references, branch deposit evidence, failed transfer evidence, and partner rail evidence, but this route must not become bank admin access, money movement, deposit finality, wallet licensing, ledger posting, or settlement authority.
new
Wallet Operations Officer Role Boundary QA Gate
Phase 293 A wallet operations officer may later review partner-powered balance labels, top-up intents, withdrawal intents, wallet statement evidence, holds, releases, and reward/refund credit evidence, but this route must not become stored value custody, independent wallet licensing, money movement, ledger truth, or settlement authority.
new
Licensed Partner Operations Officer Role Boundary QA Gate
Phase 294 A licensed partner operations officer may later review partner registration packets, contracts, callback evidence, settlement statements, SLA incidents, and API-readiness notes, but this route must not become partner approval, credential control, payment execution, regulatory approval, or FAEDA licensing authority.
new
Provider Credential Custodian Role Boundary QA Gate
Phase 295 A provider credential custodian may later verify secret classes, vault ownership, rotation readiness, emergency revocation, signing boundaries, and access-audit evidence, but this route must not expose, rotate, activate, or use any real provider credential.
new
Webhook Callback Security Gate
Phase 296 A webhook callback security gate may later review provider reference formats, signature rules, replay windows, idempotency keys, duplicate handling, and callback evidence packets, but it must not become payment truth, ledger truth, settlement truth, or live webhook runtime.
new
Production Config Approval Gate
Phase 297 A production config gate may later review public URLs, feature flags, partner endpoints, callback URLs, analytics, maps, storage, notifications, and release labels, but this route must not switch FAEDA from demo/sandbox into production or expose any secret configuration.
new
Public Runtime Smoke Test Gate
Phase 298 A public runtime smoke gate may later verify that FAEDA opens, routes render, mobile views are usable, demo labels are visible, public trust pages exist, and protected runtime actions stay blocked, but this page must not create real users, orders, payments, wallet balances, notifications, geolocation events, or public upload claims.
new
Role Demo Account Login QA
Phase 299 A role demo login QA gate may later verify that each FAEDA role has a clear demo entry path, safe labels, bounded permissions, and mobile-friendly copy, but it must not create live accounts, expose real credentials, issue sessions, or unlock production dashboards.
new
Founder Public Upload Go/No-Go Board
Phase 300 A founder go/no-go board may later let the founder mark upload readiness as green, amber, or red using verified evidence, but it must not publish FAEDA, execute Google Play upload, activate production, or unlock regulated money flows.
new
Permission Gate Matrix
Founder safety board showing live, preview, backend-gated, partner-gated, founder-approved, blocked, and future actions.
active
Commerce Network
Supplier, manufacturer, wholesaler, retailer, customer, rider, and founder chain.
active
Universal Product Bank
Master product, listing, availability, manufacturer product, demand signal.
active
20M Product Factory
Deterministic 20M master-product identity universe with category, alias, source-pattern, shard, and risk-lane coverage.
active
Product Candidate Review Queue
Seller, supplier, wholesaler, and manufacturer uploads become review decisions before product truth can change.
active
Procurement / RFQ
Material need, RFQ, quotes, comparison, PO gates.
gated
Inventory Gates
Inventory movement and ledger posting candidates only.
regulated
Finance Gates
Receivable, ledger, payment intent, partner draft, callbacks, settlement.
sandbox
Partner Payments
Upaisa/SBP partner rail, callbacks, reconciliation, exceptions.
active
Logistics
Dispatch planning, execution approval, handover, proof, delivery completion.
active
Trust Governance
Evidence, disputes, watchlists, trend intelligence, audit safety.
role-safe
Runtime Workbenches
Supplier, manufacturer, wholesaler, retailer, customer, rider, and admin action surfaces.
Chain health
Source-to-sale roles
Exception desk
Founder attention
Customer portal scope review required
Owner: Security/Admin
Payment partner execution must stay sandbox gated
Owner: Payment Ops
Role workbenches need credential QA before field rollout
Owner: Founder/Product
Wholesale and rider preview packets need backend gates before mutation
Owner: Backend/Ops
Role command centers
Open switcherProduction source
Manufacturer
A manufacturer declares what it needs, what it can make, and which market channel should receive output.
Bulk movement
Wholesaler / Distributor
A wholesaler bridges factory output into retailer-ready bulk supply without pretending stock is already posted.
Public selling point
Retailer / Shopkeeper
A shop publishes source-linked local offers and receives customer demand without bypassing order/payment gates.
Demand endpoint
Customer / Family
A family expresses demand and builds a basket while FAEDA protects privacy and regulated finance boundaries.
Movement proof
Rider / Logistics Provider
A rider offers movement capacity and proof packets while finance remains partner-gated.
Governance
Founder / Admin Ops
Founder sees the full FAEDA Business Pro web ERP without weakening backend authority.
Support rails
cross-rolehuman trust
FAEDA Team field rail
Onboarding, geo/photo proof, shop and supplier verification, field issue handling, and assisted adoption.
identity
Product truth rail
Master product, local listing, vendor availability, manufacturer capacity, supplier offer, and demand signal separation.
movement
Logistics rail
Carrier offers, dispatch planning, handover proof, delivery completion evidence, COD deposit proof, and route status.
regulated
Licensed partner finance rail
Upaisa/SBP partner evidence, callbacks, reconciliation, exception desk, maker-checker, and payout approval gates.
audit
Trust governance rail
Source evidence, dispute packets, watchlists, trend intelligence, audit logs, and founder/security review.
Founder decisions
Next approvals
1
Use /business-pro/roles as the human map before adding more deep modules.
2
Keep Business Pro as paid web/tablet/desktop shell while public app remains the entry point.
3
Enable real actions only where backend permission helpers exist and route tests pass.
4
Keep Upaisa/SBP payments as licensed partner evidence until final integration contract is ready.
5
Do not expose internal cost, supplier pricing, ledger details, or other customer data in customer surfaces.
Hard boundary
No fake ERP truth
Founder dashboard can view, route, and approve work. It must not pretend to create wallet balances, partner execution, real receivables, ledger postings, inventory mutation, or payment settlement until those modules are modelled, permissioned, audited, and legally approved.
Backend permission final
Audit trail required
Partner callback evidence only
Maker-checker before payout