Operations leadership
Enterprise Operations Home
ERP master data
Customer Master
Customer identity, ledger, transaction, and risk readbacks from the existing trade-core customer 360 routes.
FRONTEND_APP_ONLY
/erp/master-data/customer-master
Active root: frontend/app. Forbidden root: frontend/src/app.
TRADE_CORE_READBACKS
0/4 safe responses
HTTP 403/401 is treated as protected readiness, not a broken page.
NO_BACKEND_ROUTE
codex502-master-data-governance-family-v1
No DB schema, helper export, auth, route, payout, or scheduler change.
Customer 360
Buyer/company profile evidence remains DB-backed through trade-core.
Ledger linked
Customer ledger and transaction readbacks stay under existing ERP routes.
Governed
Credit/risk visibility is read-only and admin protected where required.
Governed Commands
Governance Proof
| Guard | Evidence | State |
|---|---|---|
| Frontend route | frontend/app/erp/master-data/customer-master/page.tsx | ADDED |
| Backend owner | Existing /api/trade-core customer 360 routes | UNCHANGED |
| Trade chain | No listing/order/wallet/payout mutation | PRESERVED |
Smoke Contract
Page HTTP 200 or 307 is accepted. Page HTTP 500 is forbidden. API 403 remains a protected-ready readback state.