| Group | Main records |
|---|---|
| Access | app_users, roles, permission modules, branch access/overrides, work-list members, API tokens |
| Customer | Customers, addresses and identity documents |
| Commercial | Quotations/lines, Orders/lines, commercial offers, combo components, discounts and relationships |
| Fulfilment | Trips, Trip items, proofs, vehicles and driver details |
| Money | Payments/documents, recurring cycles/payments, refunds/documents, adjustments, collections and defaults |
| Inventory | Items, stock units, locations, movements, transfers, repairs and warehouse checks |
| Procurement | Suppliers, purchase orders/lines, goods receipts/lines/serials and adjustments |
| After-sales | Service requests/actions, warranties and sleep tests |
| Integration | Notifications, deliveries, outbox, legacy import/mirror/projection state, mappings and issues |
All application APIs use /api/v1.
| Surface | Authentication | Purpose |
|---|---|---|
/auth/* |
Public entry plus JWT-protected identity actions | Google login, callback, session adoption, refresh, logout and current user |
| Portal resource routes | Hub JWT/session + PBAC | Staff CRUD, queues and state transitions |
/oe/* |
Scoped API token or authorised session | Dispatch board, assignment, provision and machine-facing roster operations |
/ops/* |
Hub JWT through OE | Driver and warehouse work owned by the signed-in person |
/health |
Public | Liveness only; do not treat it as dependency readiness |
Major portal route groups include users/roles, branches/lookups, customers, catalogue, quotations, Orders, Trips, payments, recurring payments, refunds, collections, itemisation, inventory, procurement, warranties, sleep tests and service requests.
| Record | Owning service |
|---|---|
| Order | OrderService |
| Trip | TripService |
| Payment | PaymentService |
| Recurring money | RecurringPaymentService and schedule hooks |
| Refund | RefundService |
| Itemize/Order Line | ItemizeService |
| Inventory movement | InventoryService |
| Procurement | ProcurementService |
| Warehouse checking | WarehouseCheckingService |
Do not reproduce these transitions in a controller, frontend component, SQL patch or external client.
The shared Hub owns authentication, profile identity, policy decisions and the fleet source. Ibnu Sina stores a thin local identity mirror for joins and list display. Detailed HR/person data should be resolved from the Hub on demand rather than duplicated.
ibnu-sina.BU_IB_BASE_URL, BU_IB_TOKEN and OE_BU_IBNU_SINA_UNIT_ID.X-OE-BU: ibnu-sina.EXPO_PUBLIC_ENABLED_BUS in the Ops build.Legacy integration uses mirror tables, ingestion runs, state, projection queues, identity mappings and issue records. Out-of-order safeguards prevent an old source event overwriting newer operational work. Operators should use the legacy health endpoint and issue tables instead of manually replaying arbitrary SQL.
The schema carries item/account/supplier mappings and the application exposes posting transitions. Current payment, recurring-payment and item-line exports are explicitly marked as stubs: they mint deterministic references and enqueue outbox events but do not prove an AutoCount document exists.
Any real writer must provide:
PayEx exists as a payment method in managed lookup data. A complete payment-gateway initiation, callback, signature validation and settlement-reconciliation contract was not found in the reviewed repository. Do not describe the payment-method option as a live gateway without production evidence.
Private evidence includes Trip proofs, payment slips and identity documents. Public storage is suitable only for approved catalogue/brand images. Persist storage object paths and generate signed URLs on read; never persist an expiring URL as the document identity.