Blocked
API
api/v1 : 4000
http://127.0.0.1:4000/api/v1
Customer-shop runtime activation
Move from demo flow to real evidence, one gate at a time.
This page checks the API, database, migration table, and sandbox evidence desk before customer-to-shop records are trusted as persisted runtime evidence.
Checking
Checking FAEDA runtime readiness.
Last checked: Not checked by API
Blocked
Database
Not connected
API_NOT_REACHED_FROM_WEB_PREVIEW
Blocked
Sandbox table
Migration needed
RUNTIME_READINESS_ENDPOINT_UNAVAILABLE
Needs seed / action
Records
0
Run the functional flow after API and DB are live.
Truth boundary
This gate activates evidence only.
Even when every readiness card turns green, customer charging, wallet movement, stock ledger mutation, provider execution, and payout stay behind later approval gates.
readiness Onlyno Customer Chargeno Wallet Movementno Inventory Mutationno Automatic Payoutno Provider Credential Exposure
Activation order
Do these in this order.
The order prevents a fake-success UI where the web page looks live but records are not persisted.
Step 1
BlockedStart PostgreSQL runtime
DevOps / founder technical desk
docker compose up -d postgresStep 2
BlockedApply Prisma migrations
Backend operator
npm run db:migrateStep 3
Needs seed / actionSeed sandbox QA accounts
QA operator
npm run db:seedStep 4
BlockedStart FAEDA API on port 4000
Backend operator
npm run start:dev -w apps/apiStep 5
BlockedRun customer-shop functional flow
Product QA
Open /business-pro/customer-shop-functional-flowStep 6
Needs seed / actionReview persisted sandbox evidence
Ops / audit
Open /business-pro/customer-shop-sandbox-recordsQA account policy
Use seeded accounts only inside sandbox QA.
Admin, customer, and shopkeeper fixtures belong to the seed script and internal testing. This screen intentionally does not expose raw passwords or provider credentials.
Next connected screens