One founder-level board showing which FAEDA actions are live, preview-only, backend-gated, partner-gated, founder-approved, blocked, or future ERP depth.
12
Allowed only through existing backend helpers and auth/permission checks.
6
Safe payload packets with no mutation, no financial truth, and no inventory truth.
5
Needs endpoint, validation, permissions, audit, tests, and route QA.
3
Real financial movement stays behind licensed partner and maker-checker flow.
Matrix is planning truth, not runtime authority
This page documents the intended gate state. Backend permissions and audit logs remain the actual enforcement layer.
Filters
Status
Role
Export shape
Current filtered view: 29 actions.
Supplier
LiveSupplier action workbench
Backend
createSupplierNetworkProfile
Approval
Backend auth and business permission
Risk
Duplicate or fake supplier profile can poison source truth.
Next
Add source evidence score and duplicate detection.
Supplier
LiveSupplier action workbench
Backend
createSupplierNetworkOffering
Approval
Backend auth and product/source validation
Risk
Wrong grade, unit, or origin can mislead manufacturers.
Next
Attach COA, origin invoice, lot proof, and warehouse proof.
Supplier
LiveSupplier action workbench
Backend
createSupplierQuote
Approval
Backend auth and RFQ permission
Risk
Tax, unit, quantity, and lead-time mismatch can break PO flow.
Next
Add quote comparison warning and tax validation.
Supplier
BackendSupplier PO acknowledgement desk
Backend
planned PO acknowledgement endpoint
Approval
Supplier identity, issued PO scope, audit
Risk
Supplier can corrupt PO truth if original terms are overwritten.
Next
Keep original PO immutable and store supplier acknowledgement separately.
Supplier
PartnerSupplier settlement ledger posting
Backend
partner callback plus ledger posting later
Approval
Licensed partner callback, reconciliation, maker-checker
Risk
Fake payout claim creates financial and regulatory exposure.
Next
Keep as evidence until partner settlement and ledger posting are verified.
Manufacturer
LiveManufacturer action workbench
Backend
createSupplierNetworkProfile
Approval
Backend auth and manufacturer seller status
Risk
Unverified manufacturer can publish capacity without real factory proof.
Next
Add factory proof, machine/photo evidence, capacity confidence.
Manufacturer
LiveManufacturer action workbench
Backend
createProcurementRfq
Approval
Backend auth and material need validation
Risk
Bad RFQ creates noisy supplier quotes and wrong purchasing intent.
Next
Add raw material grade templates and delivery city constraints.
Manufacturer
PreviewManufacturer action workbench
Backend
none yet
Approval
Founder/product approval before mutation
Risk
Capacity can be mistaken for real finished stock.
Next
Create output capacity endpoint separate from stock/inventory.
Manufacturer
BackendFinished goods stock posting gate
Backend
planned stock posting endpoint
Approval
Finished goods review, warehouse proof, audit
Risk
Fake inventory damages retailer/customer trust.
Next
Require lot review, quality lock, warehouse lock, and posting audit.
Manufacturer
FutureManufacturer Business Pro
Backend
future BOM/batch/QC/HR/IoT services
Approval
Paid Business Pro and implementation scope
Risk
Starting too deep slows FAEDA market proof.
Next
Unlock after demand, product truth, and B2B pipeline are working.
Wholesaler
LiveWholesaler action workbench
Backend
createSupplierNetworkProfile
Approval
Backend auth and wholesale role permission
Risk
False distribution network inflates market coverage.
Next
Add warehouse proof and distribution zone verification.
Wholesaler
LiveWholesaler action workbench
Backend
createSupplierNetworkOffering
Approval
Backend auth and source/product validation
Risk
Bulk offer can look like real stock if not source-linked.
Next
Require manufacturer source link and receiving evidence confidence.
Wholesaler
PreviewWholesaler action workbench
Backend
none yet
Approval
Backend allocation endpoint needed
Risk
Allocation can create fake retailer stock if posted too early.
Next
Build allocation endpoint after receiving and stock register gates.
Wholesaler
BackendWholesaler stock register gate
Backend
planned stock register endpoint
Approval
Receiving evidence, shortage/damage checks, audit
Risk
Incorrect stock register can misroute retailer supply.
Next
Separate receiving candidates from posted stock truth.
Retailer
LiveRetailer action workbench
Backend
createSupplyProfile
Approval
Backend auth and shop scope
Risk
Fake shop profile can create false public supply map.
Next
Add FAEDA Team geo/photo verification and duplicate shop checks.
Retailer
LiveRetailer action workbench
Backend
createProductTruthDraft
Approval
Backend auth and product identity validation
Risk
Mixing product identity with shop stock makes the product bank messy.
Next
Route through product linkage approval when confidence is low.
Retailer
PreviewRetailer action workbench
Backend
none yet
Approval
Customer inquiry response endpoint needed
Risk
Seller response can be mistaken for accepted quote/order.
Next
Build seller response endpoint before quote acceptance gate.
Retailer
BackendRetail listing publication gate
Backend
planned listing publication endpoint
Approval
Listing approval, source link, availability confidence
Risk
Public listing without truth creates customer disappointment.
Next
Require approved listing candidate and freshness window.
Customer
LiveCustomer action workbench
Backend
createDemandDraft
Approval
Backend auth where available or customer-scoped draft rules
Risk
Demand must not become order/payment without confirmation.
Next
Attach family basket, delivery zone, and substitution consent.
Customer
PreviewCustomer action workbench
Backend
none yet
Approval
Family/group basket backend model needed
Risk
Group basket can expose family/private purchasing data.
Next
Add household consent, group privacy, and budget cap controls.
Customer
BackendCustomer order confirmation gate
Backend
planned order confirmation endpoint
Approval
Quote acceptance, stock reservation, customer consent
Risk
Order confirmation before stock and terms can create disputes.
Next
Keep order draft, quote acceptance, and confirmation separate.
Customer
FounderCustomer portal later
Backend
customer-scoped APIs required
Approval
Security/privacy review and customer scope tests
Risk
Cross-customer data leakage is a critical privacy issue.
Next
Implement only after backend scope review and portal DoD.
Rider
LiveRider action workbench
Backend
createLogisticsCarrierOffer
Approval
Backend auth and logistics booking scope
Risk
Carrier offer cannot mean delivery accepted or completed.
Next
Add route capacity, vehicle proof, and service zone checks.
Rider
PreviewRider action workbench
Backend
none yet
Approval
Handover proof endpoint needed
Risk
Proof packet can be mistaken for delivery completion.
Next
Build proof endpoint with OTP/photo/location evidence rules.
Rider
PartnerRider earnings settlement view
Backend
partner settlement plus ledger later
Approval
COD deposit evidence, partner reconciliation, maker-checker
Risk
Fake rider balance or COD settlement creates finance exposure.
Next
Keep rider view as pending/held/approved/paid/disputed status only.
Founder
LiveAdmin action workbench
Backend
createPartnerPaymentExecutionDraftFromApproval
Approval
Licensed payout approval and backend permission
Risk
Draft must not be treated as payment execution.
Next
Add queue visibility, callback intake, reconciliation, and exception links.
Founder
PreviewAdmin action workbench
Backend
none yet
Approval
Exception desk backend model needed
Risk
Unstructured exception notes can hide real financial mismatch.
Next
Persist exception desk cases with hold, review, escalate, resolve states.
Founder
PartnerLicensed partner payout approval gate
Backend
future real partner execution
Approval
Maker-checker, partner config, reconciliation, legal approval
Risk
Real money movement requires licensed partner and audit proof.
Next
Do not enable until Upaisa/SBP integration contract and test sandbox pass.
Founder
BlockedNot allowed
Backend
none
Approval
Never silent; emergency break-glass only after policy
Risk
Silent override destroys trust and audit integrity.
Next
Design break-glass policy separately with audit and notification.
Review checklist
Backend authority
Every action must be enforced server-side. UI visibility is never permission.
Audit evidence
Any approval, hold, exception, or change needs actor, timestamp, reason, and source record.
No mixed truth
Product identity, stock, order, invoice, ledger, and payment remain separate tables/flows.
Licensed finance
Wallet, settlement, payout, and partner rails stay evidence-gated until legal integration is live.
Customer privacy
Customer surfaces never expose other customers, supplier cost, internal ledger, or hidden pricing.
Founder review
High-risk gates need maker-checker and founder/admin review before runtime activation.
Hard boundary
This board is a founder/product safety map. Backend APIs, server permissions, audit logs, partner callbacks, and maker-checker approvals remain the only runtime authority.