This section is the entry point for a team taking ownership of the Encik Beku Sales Module. The existing feature documentation remains the authority for approved business behaviour. These pages explain how the implemented system is structured, released, tested and operated.
| Item | Value |
|---|---|
| Source repository inspected | utopiabuilder/encik-beku |
| Local source commit inspected | 2231d88 |
| Source branch inspected | feat/add-notify-wiki |
| Inspection date | 29 September 2026 |
| Wiki repository | utopiabuilder/sales-module-wiki |
This is a source-code baseline, not proof of production deployment. Confirm the live frontend and backend versions through their version endpoints and hosting dashboards before an incident, release or data repair.
The older business pages cite commits 613165b and ebf7cf0. Their rules remain useful, but any statement about what is currently built must be rechecked when those commits differ from the deployed version.
| Order | Page | What it answers |
|---|---|---|
| 1 | Architecture | What runs, where the boundaries are, and how a request moves through the system |
| 2 | Environments and deployment | Where it runs, what deploys automatically, and how to release or roll back safely |
| 3 | Local development and testing | How to run and verify changes without touching production |
| 4 | Data, APIs and integrations | Database ownership, API surfaces, external systems and scheduled work |
| 5 | Security, access and privacy | Identity, authorization, secrets and sensitive-data boundaries |
| 6 | Operations runbook | Health checks, incident triage, high-risk workflows and recovery guidance |
| Layer | Implemented with | Ownership boundary |
|---|---|---|
| Web application | Next.js 16, React 19, TypeScript | Encik Beku frontend; deployed separately from the API |
| API | Laravel 13, PHP 8.4 | Encik Beku backend under /api/v1 |
| Database | PostgreSQL on the Encik Beku Supabase project | Schema is owned by SQL files in backend/supabase/migrations; Laravel migrations are not authoritative |
| Identity | UtopiaSpace Supabase project | Shared identity; Encik Beku authorization remains local in app_users, roles and branch permissions |
| Field application | utopiaspace-ops repository |
Separate application consuming /api/v1/ops/* |
| OE integration | Utopia Hub/OE | Dispatch and fleet boundaries cross repositories |
| Hosting | Vercel frontend; DigitalOcean App Platform backend | Independent releases can temporarily be on different commits |
| Files | S3-compatible storage through Laravel filesystem disks | Private and public upload disks have different exposure rules |
development as an automatically deployed branch for both halves of the system.QUEUE_CONNECTION=sync means queued jobs execute inside the request unless the infrastructure changes.schedule:run runner and must be verified.2026-08-18 16:00:00+00 when investigating current-business behavior.| Question | Authority |
|---|---|
| What should the business do? | Latest approved decision, feature page and acceptance criteria |
| What does this source checkout do? | Code and tests at the stated commit |
| What is deployed? | Live version endpoints, hosting release records and migration evidence |
| What happened to a record? | Database facts, audit rows and application logs |
When these disagree, record the disagreement. Do not silently rewrite one layer to make it resemble another.