This page compares the documented Scaffolding workflow with repository commit c0bce14, reviewed on 29 September 2026.
Status meanings:
The Scaffolding documentation was reconstructed mainly from repository evidence. Aligned means aligned with this documented repository baseline; it does not prove that the same version is deployed in production.
| Count | What |
|---|---|
| 5 | Aligned — supported by the reviewed code and tests |
| 6 | Partial — implemented, but a control or operating detail remains |
| 1 | Gap — required process not established in the repository |
| 3 | Unverified — requires production or business-owner evidence |
| 5 | Critical — affects access, money, stock, integration recovery or system recovery |
| Area | Expected behaviour | Position at c0bce14 |
Status |
|---|---|---|---|
| Authentication | A Core identity with sales.scaffolding.view can enter the product and receive a local user record |
Login, callback, session refresh/logout, Core policy check and local provisioning exist | Aligned |
| Permissions and branch scope | Backend permissions and allowed branches control every sensitive action and record | Local roles, permissions and branch APIs exist; complaint routes do not show a dedicated complaint permission gate | Partial |
| Branch configuration | Use stable branch codes while showing friendly labels | Shah Alam (ShahAlam) and Johor are seeded; shared label helpers exist |
Aligned |
| Customers and quotations | Maintain customers and addresses; quote Rent, Buy, Service and transport charges; convert an accepted quote | Customer, quotation, terms, company, send/accept/reject/duplicate/convert routes and services exist | Aligned |
| Orders | One Order can mix Rent, Buy and Service lines and support lock, finalise, dispatch, revert and audit | Order APIs and service flows exist for these actions | Aligned |
| Trips and fulfilment | Plan and complete delivery, pickup/return and lorry-crane work with traceable dates and assignments | Trip models, APIs, calendar/filter logic and tests exist; confirm the timestamp that proves actual completion | Partial |
| Inventory | Reserve, issue, keep on rent, return and reconcile physical stock; support registration, checking and transfers | Item, variant, movement, check, discrepancy, transfer, receipt and approval flows exist with tests | Aligned |
| Payments | Record a customer payment and let an authorised Finance user verify it separately | Payment records and verification routes exist; the live reconciliation and accounting ownership are not documented | Partial |
| Refunds and deductions | Sale requests, Manager approves, Account verifies; deposit refunds require completed pickup; deductions create a separate invoice | Approval queues, pickup checks, deductions and deduction-invoice code/migrations exist; production rollout is not proven | Unverified |
| Monthly rental billing | Produce the correct recurring rental charge according to the approved billing schedule | No repository scheduler or confirmed operating procedure establishes how monthly billing runs | Gap |
| Accounting posting | Send approved invoice/payment information to one clearly owned accounting process without duplicate numbering | Invoice records exist, but the live accounting system, posting contract and number ownership are not established | Unverified |
| AppSheet / sheet sync | Queue and retry supported entity changes and reconcile them by stable IDs | Sync tables, outbox, scripts and retry paths exist; authoritative-system and conflict rules need confirmation | Partial |
| OE integration | Authenticated draft/commit operations with technicians, vehicles and recoverable job logs | Machine-authenticated OE endpoints and job-log resources exist; live environment, credentials and recovery ownership are unknown | Partial |
| Complaints | Only authorised staff can view and manage complaints within the intended scope | Complaint pages and authenticated routes exist; dedicated permission enforcement needs review | Partial |
| Deployment, backup and recovery | Repeatable backend/frontend release, rollback, backup and tested restore | Frontend deployment evidence and backend container exist; backend release process, backup ownership and restore evidence are unavailable | Unverified |
These items affect access, money, stock, integration recovery or recovery of the whole system.
| Priority | Work required |
|---|---|
P0 |
Confirm and test the complete monthly rental billing process |
P0 |
Confirm refund/deduction rollout and test Sale → Manager → Account with a completed pickup |
P0 |
Establish one accounting-posting and invoice-number ownership contract |
P0 |
Review complaint permissions and enforce the approved backend capability |
P0 |
Document and test backend deployment, rollback, database backup and restore |
P0 |
Define AppSheet/OE authority, retry, duplicate prevention and reconciliation rules |
| P1 | Add the missing backend and frontend environment-variable templates without secret values |
| P1 | Remove or clearly mark inherited Encik Beku, mock-data and Spring Boot notes |
| P1 | Confirm the exact Trip completion timestamp used by refund and operational checks |
| P1 | Decide whether Follow-up, Intercompany, Subcontract Split and tool-check workflows are in scope |
These require evidence from the running environment and responsible owners. They should not be guessed from source code.