Two layers, and they do not overlap. The shared design holds the rules every unit inherits. Each business unit records only its own workflow, differences, decisions and open questions. A unit's pages never replace the shared design — they say where that unit departs from it.
| Page | What it covers |
|---|---|
| What is Sales Module | The 22 components and the rules every unit inherits |
| All Business Units | Every unit documented here, and the state of each |
| Technical Updates | What changed in the code, per business unit — written by the update workflow |
Every documented unit carries the same three groups, in the same order. Learn them once and you know where to look in any unit.
| Group | Pages |
|---|---|
| Foundation | Overview Component Map Cross-cutting Requirements Glossary |
| Workflows | Feature Index Proposals Reference |
| Governance | Decisions Open Questions Implementation Status |
| Technical handover | System Handover |
| Group | Pages |
|---|---|
| Foundation | Overview Business Overview Component Map Cross-cutting Requirements Glossary |
| Workflows | End-to-End Workflows Feature Guide |
| Governance | Implementation Status |
| Technical handover | System Handover |
| Group | Pages |
|---|---|
| Foundation | Start Here Overview Component Map Cross-cutting Requirements Glossary |
| Workflows | End-to-End Workflows Feature Guide |
| Governance | Implementation Status |
| Technical handover | System Handover |
Ibnu Sina is documented as an independent Sales Module; OE and Utopiaspace Ops appear only as integrations.
| Order | Source |
|---|---|
| 1 | The shared master component list |
| 2 | The latest business-unit decision |
| 3 | The feature page |
| 4 | Its acceptance criteria |
Dated audits are historical evidence, not current truth.
Future units appear alongside Encik Beku, each with its own sections and vocabulary. Read a unit's glossary before reusing its pages — itemize, snapshot, item and job mean specific things in Encik Beku and different things elsewhere.