This is the main documentation for the Encik Beku system. If this is your first time here, open Overview first.
| Field |
Value |
| Aligned |
7 October 2026 |
| Against |
repository commit 2aa241e |
| For |
Indoor, OE, Account, the Manager and the development team |
| Audience |
Internal — not for customers |
| Page |
Open this page when you want to... |
| Overview |
Understand what Encik Beku does and how one customer job works from start to finish |
| Component Map |
See which parts follow the standard Sales Module and which parts work differently |
| Cross-cutting Requirements |
Check rules that must be followed everywhere in the system |
| Glossary |
Check the meaning of a role, record, short form or Malay term |
| Feature Index |
Find instructions and rules for a specific system function |
| Decisions |
See what the team has already decided |
| Open Questions |
See what the team has not decided yet and who needs to answer |
| Implementation Status |
See what is already working, partly working or not built yet |
| Reference |
Find supporting lists such as items, lead sources, LG information and contacts |
| Proposals |
Read suggested ideas that have not been approved |
| System Handover |
Learn how to run, maintain, deploy and support the application |
When two statements disagree, this is the order that wins.
| Order |
Source |
| 1 |
Shared master component list, for rules applying to every unit |
| 2 |
Latest dated Encik Beku decision |
| 3 |
Relevant feature page |
| 4 |
Acceptance criteria on that feature page |
| 5 |
Dated audits, which are historical evidence only |
Each feature page separates two things:
- Approved behaviour: what the system is supposed to do.
- Current implementation: what the reviewed code actually does.
A Gap means the approved behaviour is not built yet. It does not mean the requirement has been cancelled.
| Date |
Change |
| 18/09/2026 |
Current-system reconciliation against commit ebf7cf0. Confirmed the remaining gaps recorded in the component map and implementation status |
| 16/09/2026 |
First publication. Replaced the Solution Alignment and Decision Record of 25 August, which stays as history |
| 14/09/2026 |
State sweep of the build: 31 gaps, 16 decisions and the developer's reply table |
| # |
Condition |
| 1 |
The Encik Beku and software owners have reviewed all 22 component rows |
| 2 |
Every disagreement has a recorded decision |
| 3 |
Every open question has an owner and answer |
| 4 |
The implemented refund types, snapshot names, company-freeze point and OE gate match the approved documentation |