This section explains how the Ibnu Sina Sales Module is structured, configured, deployed, secured, tested and supported. It contains operational reference material only; it does not include an acceptance or handover checklist.
Read it together with the business workflows and implementation status. A technically successful change can still corrupt money or stock when it ignores the business state machines.
| Page | What it answers |
|---|---|
| Architecture | What runs where and how the portal, API, database, OE and Ops fit together |
| Data, APIs and Integrations | Main records, route groups, state ownership and external contracts |
| Environments and Deployment | Local services, configuration boundaries and release mechanics |
| Security and Access | Authentication, permissions, branches, work lists, tokens and sensitive data |
| Testing and Operations | Verification, monitoring, triage, recovery and recurring maintenance |
The reviewed portal/backend source is utopiabuilder/ibnu-sina commit 67c2c3a on development, reviewed 30 September 2026. The independent Utopiaspace Ops repository was reviewed for the Ibnu Sina slice and integration contract. Production environment values, external credentials and the exact deployed backend commit remain environment-owned facts.
Preserve the existing system boundaries:
When an external integration is unavailable, retain the committed local transaction and make the delivery/reconciliation state observable. Do not pretend an outbox row is external acceptance.