# Sintesis Korpus Dokumen CRM — Estimates, Leads, Activity History, Pivot Enterprise, Approval & SOD

## 1. Judul dan Subjudul

**Judul:** Sintesis Korpus Dokumen CRM — Estimates, Leads, Activity History, Pivot Enterprise, Approval & SOD.

**Subjudul:** Satu referensi utuh atas 31 dokumen sumber yang memuat spesifikasi final Estimate Activity History (full snapshot), blueprint Estimates Pivot Enterprise & KPI, tata kelola proyek (RACI/sprint/weekly/UAT), fitur Leads beserta timeline-nya, prosedur Approval & Segregation of Duties, serta alur integrasi CRM → Subsidiary → Holding.

**Cakupan:** 31 file markdown sumber. **Tanggal snapshot data:** 2026-04-18. **Status dokumen:** sintesis terkompilasi (versi mutakhir ditandai per topik).

---

## 2. Ringkasan Eksekutif

Dokumen ini adalah sintesis dari **31 file markdown sumber** yang mencakup portofolio CRM modul **Estimates (Penawaran)**, **Leads**, **Activity History**, **Pivot & KPI Enterprise**, **Governance/RACI/UAT**, serta **alur integrasi CRM → Subsidiary → Holding**. Seluruh materi dikoleksi dari basis kode CodeIgniter (RISE CRM), basis data MariaDB, dokumen spesifikasi, HOA, dan dokumen laporan pivot.

### 2.1 Peta singkat isi korpus

| Kelompok | Jumlah File | Fokus |
|---|---|---|
| Estimate Activity History (spec, hardening, PII, skala, task) | 5 | Spesifikasi final full-snapshot, PII masking, index/scale, rencana eksekusi |
| Estimates Pivot & KPI Enterprise | 5 | Blueprint pivot role-based, endpoint P1/P2, UAT KPI, kontrak KPI |
| Project Governance (RACI, sprint, weekly, evidence, mapping) | 5 | RACI final PIC, sprint plan, weekly checklist, UAT evidence, UAT mapping |
| Leads & Timeline | 2 | Prioritas data lead, adopsi estimate, timeline HOLD |
| Analisis & Laporan 2 Minggu / Direksi | 4 | Analisis v14, nama konsumen, laporan snapshot, ringkas direksi |
| Integrasi & Flowchart | 2 | Master map teknis CRM→Sub→Holding, UAT multi-kondisi |
| Approval & SOD | 1 | Prosedur approval & segregasi of duties |
| SQL Manual / Retensi / Rencana / Konteks | 5 | Panduan eksekusi SQL, retensi Step3, rencana penyelesaian, konteks fitur, pivot plan |

### 2.2 Temuan eksekutif utama

1. **Activity History Estimate memakai pendekatan *full snapshot per event*** (append-only) dengan hash SHA-256. Konsep ini menjadi fondasi audit trail modul Estimate.
2. **Ada koreksi versi penting**: daftar `NEW/QUALIFIED/NEGOTIATION/...` adalah flow **Lead**, sedangkan activity code untuk **Estimate** mengikuti status dokumen `DRAFT/SENT/ACCEPTED/DECLINED`.
3. **Pivot Enterprise dibangun tanpa menambah tabel baru** — dimulai dengan reuse data existing lewat 7 endpoint data terstruktur (summary, owner, channel, client, lead, aging, exception). P1 dan P2 core sudah selesai di kode (per 2026-04-19); UAT + reconciliation masih tertunda.
4. **Baseline portofolio all-time**: 36 estimate, nilai Rp 8,05 miliar, accepted rate 92,86%, tapi backlog draft 22 dokumen dengan 21 di antaranya aging ≥7 hari. Lead incomplete 18, ready SO hanya 1.
5. **Risiko terbesar**: Rp 4,71 miliar nilai estimate 6 bulan terakhir berada pada `owner kosong` (akuntabilitas follow-up).
6. **Alur integrasi** CRM→Subsidiary→Holding memiliki 4 *fault point* yang sudah teridentifikasi (F1–F4).
7. **Approval SO** sedang dirombak: muncul status baru `siap_diorder` yang memisahkan pengajuan (sales) dari otorisasi (atasan), enacting prinsip SOD *four-eyes*.
8. **RACI final** sudah dikunci dengan 8 peran (EXE/BO/PO/TL/BI/QA/SO/DEV) dan matriks eskalasi ber-SLA.

---

## 3. Peta Modul & Objek CRM (tabel)

| Objek / Modul | Tabel / Sumber Data | Controller / Service Utama | Endpoint Kunci | PIC / Prioritas |
|---|---|---|---|---|
| **Estimate (dokumen)** | `rise_estimates`, `rise_estimate_items`, `rise_clients`, `rise_users`, `rise_taxes` | `app/Controllers/Estimates.php` | `estimates/list_data`, `estimates/save`, `estimates/update_estimate_status/{id}/{status}` | Sales / Sales Ops |
| **Estimate Activity Master** | `rise_estimate_activity_master` (seed 4 kode: DRAFT/SENT/ACCEPTED/DECLINED) | — (referensi tabel) | — | TL / DEV |
| **Estimate Activity History** | `rise_estimate_activity_history` (append-only) | `EstimateActivityHistoryService` | `estimates/activity_timeline/{id}`, `activity_snapshot/{id}/{ver}`, `activity_compare/{id}/{from}/{to}` | DEV / Codex |
| **Estimate Activity State** | `rise_estimate_activity_state` | — | — | DEV |
| **Pivot / KPI Estimate** | turunan `rise_estimates` | `Estimates.php`, `Reports.php` | `estimates/kpi_core_data`, `pivot_owner_month_status_data`, `pivot_summary_data`, `pivot_owner_performance_data`, `pivot_channel_performance_data`, `pivot_client_data`, `pivot_lead_data`, `pivot_aging_data`, `pivot_exception_data` | PO / BI / DEV |
| **Prioritas Lead (Data)** | `rise_estimates` join client | `Estimates.php` | `estimates/prioritas_data_summary_data`, `estimates/prioritas_data_list_data` | Sales Ops (SO) |
| **Lead** | `leads`, `lead_shared` state | `app/Controllers/Leads.php` | `Leads/update_share()`, `save_as_client()`, `delete_file`, `save_profile_image` | Sales / BO |
| **Lead Activity Timeline** | gabungan event lead+estimate | `LeadActivityTimelineService.php` (HOLD) | panel `/leads/view/{id}` | DEV (status: belum selesai) |
| **Akses / Security** | `roles.permissions` | `Security_Controller.php` | helper `validate_estimate_access()`, `can_access_this_estimate()` | TL / QA |
| **Sales Order & Bridge** | `order_bridge_items` (CRM), `rise_order_bridge_items` | `Estimates::_writeOrders()`, `save_order()` | `authorize_order($id)` (baru) | Supervisor / Atasan |
| **Webhook Integrasi** | — | `WebhookService`, `Webhook.php` | `sendOrderSubsidiary()`, `sendOrderDirectHolding()`, `/eusvc/webhook/receive_order` | DEV |
| **Personnel Activity Pivot (BI)** | `transaksi.counters_intext`, `dim_person`, `trx_activity_raw` | `Activity_model.php`, `LaporanApi.php` (CodeIgniter 3) | `LaporanApi/activity_pivot`, `run_etl` | BI |
| **Sub-Modul Biaya (terkait)** | `transaksi` master | `coTransaksiUi.php` | — | Ops |

---

## 4. Estimate: Activity History (Full Snapshot) — Spec Final

### 4.1 Dokumen Kanonik & Koreksi Versi

Dokumen kanonik: `ESTIMATE_ACTIVITY_HISTORY_FINAL_SPEC.md` (Last update 2026-04-16). Pendekatan yang disepakati adalah **full snapshot per event** — baik saat ganti status aktivitas maupun saat edit data.

**Koreksi penting (2026-04-16)** yang harus menjadi rujukan utama:
> Untuk modul **Estimate**, activity code mengikuti **status dokumen estimate**, yaitu `DRAFT`, `SENT`, `ACCEPTED`, `DECLINED`. Daftar `NEW/QUALIFIED/NEGOTIATION/...` adalah flow **Lead**, bukan flow Estimate.

Konsekuensi koreksi ini:
- Tabel `rise_estimate_activity_master` di-seed **4 kode aktif**, bukan 9 (lihat §3.4).
- Jika pernah menjalankan flow lama (`NEW/WON/LOST`), wajib jalankan `SQL_ESTIMATE_ACTIVITY_ALIGN_TO_DOC_STATUS.sql` untuk normalisasi.

**Tujuan bisnis (5):** jejak perubahan estimate dari awal s.d. final; hitung revisi per aktivitas; audit trail lengkap (siapa/kapan/apa); UX timeline di panel detail; integritas data via append-only + hash.

### 4.2 Asumsi Teknis

1. DB aktif: `MySQLi` (MariaDB), prefix tabel aplikasi `rise_`.
2. Tabel inti existing tetap dipakai: `rise_estimates`, `rise_estimate_items`, `rise_clients`, `rise_users`, `rise_taxes`.
3. Histori bersifat **additive** (menambah tabel), bukan mengganti mekanisme existing.

### 4.3 Data Model & DDL (tabel inti)

#### 4.3.1 Tabel History Event + Full Snapshot — `rise_estimate_activity_history`

Kolom kunci dan constraint:
- `id` BIGINT UNSIGNED AI (PK)
- `estimate_id` INT UNSIGNED (FK → `rise_estimates.id`)
- `event_type` ENUM(`STATUS_CHANGE`,`EDIT`,`SYSTEM_SYNC`)
- `activity_code` VARCHAR(30)
- `cycle_no`, `activity_entry_no`, `revision_no`, `version_no` (penomoran)
- `estimate_doc_status` VARCHAR(30)
- `change_note` TEXT
- `snapshot_hash` CHAR(64) (wajib = SHA-256 canonical JSON)
- `snapshot_json` LONGTEXT (wajib, append-only)
- `changed_by` INT UNSIGNED (FK → `rise_users.id`)
- `changed_at` DATETIME, `ip_address` VARCHAR(45), `user_agent` VARCHAR(255)

Index & unique:
- UNIQUE `uq_estimate_version (estimate_id, version_no)`
- `idx_estimate_snapshot_hash (estimate_id, snapshot_hash)`
- `idx_estimate_changed_at (estimate_id, changed_at)`
- `idx_estimate_activity (estimate_id, activity_code, changed_at)`
- `idx_event_type_changed_at (event_type, changed_at)`
- Engine InnoDB, charset utf8.

Catatan kompatibilitas MariaDB: gunakan `LONGTEXT` untuk `snapshot_json`; validasi JSON di layer aplikasi (`json_encode/json_decode`); `snapshot_hash` wajib dari SHA-256 canonical; tabel **append-only**.

#### 4.3.2 Tabel State Cepat — `rise_estimate_activity_state`

- PK `estimate_id`; kolom `current_activity_code`, `current_cycle_no`, `current_activity_entry_no`, `current_revision_no`, `last_version_no`, `last_changed_by`, `last_changed_at`.
- FK ke `rise_estimates(id)` dan `rise_users(id)`.
- Index `idx_state_activity (current_activity_code, last_changed_at)`.

Tujuan: query list/tabel cukup baca 1 baris per estimate; timeline detail tetap baca dari tabel history.

#### 4.3.3 Tabel Master Aktivitas — `rise_estimate_activity_master`

Kolom: `code` (PK), `name`, `sort_order`, `is_terminal`, `is_active`, `created_at`, `updated_at`. Engine InnoDB charset utf8. Seed aktif (versi final Estimate): `DRAFT`, `SENT`, `ACCEPTED`, `DECLINED`.

### 4.4 Struktur Snapshot JSON (Wajib Lengkap)

Setiap event menyimpan full snapshot dengan blok minimum:

```json
{
  "estimate": { "id", "estimate_number", "status", "estimate_date", "valid_until",
                "client_id", "owner_id", "source_id", "domain_id", "top_id", "meta_data" },
  "client":    { "name", "address", "phone" },
  "items":     [ { "item_id", "title", "sku", "part_no", "qty", "price",
                   "disc_percent", "disc_amount", "net_price", "line_total" } ],
  "totals":    { "subtotal", "tax_basis", "tax_total", "grand_total", "currency" },
  "tax_rules": { "tax_id", "tax_rate", "tax_name", "tax2_id", "tax2_rate", "tax_basis_mode" },
  "attachments": [],
  "audit":     { "captured_at", "captured_by" }
}
```

**Catatan mutakhir (dari PII Policy):** contoh di atas adalah bentuk *pre-mask*. Data sensitif dimask sebelum disimpan; setiap snapshot menyertakan metadata privasi `_privacy.mode`, `_privacy.masked_fields`, `_privacy.policy_version`.

### 4.5 Flow Implementasi & Penomoran

**Trigger wajib simpan snapshot:** (1) create estimate; (2) edit header; (3) tambah/edit/hapus item; (4) update status dokumen; (5) ganti aktivitas proses.

**Urutan proses save event (13 langkah):** mulai DB transaction → lock state `FOR UPDATE` → baca state terakhir → deteksi perubahan material → skip bila no-op → tentukan `event_type` → hitung penomoran → bangun snapshot → hitung SHA-256 → simpan history → update state → simpan perubahan `rise_estimates` dalam transaksi sama → commit (rollback bila gagal).

**Aturan penomoran:**
- `version_no` naik +1 setiap event valid.
- `revision_no`: reset ke 1 saat `STATUS_CHANGE`; naik +1 saat `EDIT` di aktivitas sama.
- `activity_entry_no`: naik +1 bila kembali ke aktivitas yang pernah dilewati di cycle yang sama.
- `cycle_no`: naik +1 saat `RENEWAL` memulai siklus baru.

### 4.6 Rule Validasi Final

**Rule umum:** semua event wajib `snapshot_json`; `estimate_id` valid; `activity_code` ada di master; `changed_by` user aktif; `version_no` unik per estimate; `snapshot_hash` cocok.

**Rule aktivitas (berlaku pada flow 9-kode):** `NO_RESPONSE`/`LOST`/`WON` wajib `change_note`; `WON` hanya bila status doc minimal `accepted`; `RENEWAL` hanya setelah status terminal.

**Transisi aktivitas yang diizinkan (9-kode / flow Lead):**
- `NEW → QUALIFIED|NO_RESPONSE|LOST`
- `QUALIFIED → NEGOTIATION|FOLLOWUP_1|NO_RESPONSE|LOST`
- `NEGOTIATION → FOLLOWUP_1|FOLLOWUP_2|WON|LOST|NO_RESPONSE`
- `FOLLOWUP_1 → FOLLOWUP_2|NEGOTIATION|WON|LOST|NO_RESPONSE`
- `FOLLOWUP_2 → NEGOTIATION|WON|LOST|NO_RESPONSE`
- `NO_RESPONSE → FOLLOWUP_1|LOST`
- `WON → RENEWAL`; `LOST → RENEWAL` (opsional)

**Akses snapshot:** full snapshot hanya untuk role `admin`, `supervisor`, `owner estimate`. User lain hanya melihat ringkasan timeline. Permission gate memakai key role **`can_view_estimate_activity_snapshot`** (gate `_current_user_can_view_estimate_activity_snapshot()`).

### 4.7 UX Timeline (Wireframe)

Lokasi: halaman detail estimate `/estimates/view/{id}`, panel kanan. Baris timeline memuat: tanggal/jam, activity code, `Rev`, `Ver`, nama user, ikon tipe event. Default 20 event terbaru dengan `Load more`. Tombol `Lihat` (drawer snapshot) dan `Banding` (compare versi + diff highlighter). Filter: Semua / Status / Edit / Aktivitas.

### 4.8 PII Policy (Phase 3)

- **Mode proteksi:** `mask` (deterministik). Dilakukan di service **sebelum** `to_canonical_json()` dan sebelum hash SHA-256 dihitung. Masking deterministik menjaga kestabilan no-op detection.
- **28 kunci PII yang dimask:** `phone`, `mobile`, `mobile_phone`, `cellphone`, `wa`, `whatsapp`, `email`, `contact_email`, `address`, `alamat`, `pic_phone`, `pic_email`, `npwp`, `no_npwp`, `nik`, `ktp`, `no_ktp`, `identity_no`, `identity_number`, `rekening`, `account_number`, `account_no`, `bank_account`, `iban`, `swift`, `routing_number`, `akun_1`, `akun_2`.
- **Aturan masking:** email — local-part dimask, domain dipertahankan (`janson@example.com` → `ja****@example.com`); identitas/telepon/rekening — digit disamarkan kecuali 4 digit akhir; alamat — prefix pendek dipertahankan; nilai non-scalar → `[MASKED]`.
- **Metadata privasi:** `_privacy.mode`, `_privacy.masked_fields`, `_privacy.policy_version`.
- **Belum selesai:** kebijakan retensi/arsip; kontrol akses granular pembacaan snapshot detail.

### 4.9 Strategi Skalabilitas & Retensi

- Retensi aktif: snapshot penuh minimal **24 bulan** di tabel utama; data >24 bulan dipindah ke `rise_estimate_activity_history_archive`.
- **Growth threshold (trigger tindakan):** tabel > **2 juta rows**, atau ukuran > **5 GB**, atau query timeline **p95 > 2 detik**.
- **Archive strategy (rolling):** hot data 24 bulan; warm/archive dipindah bertahap per batch **5.000–20.000 rows**; verifikasi hash sebelum & sesudah pemindahan; archive table read-only.
- **Partition guidance:** hanya jika volume > **10 juta rows** dan growth bulanan stabil; wajib uji detail karena ada unique key `(estimate_id, version_no)`; lakukan di window maintenance + backup penuh.
- **Index strategy (Step 4):**
  1. `idx_estimate_cycle_activity_entry (estimate_id, cycle_no, activity_code, activity_entry_no)`
  2. `idx_estimate_event_version (estimate_id, event_type, version_no)`
  3. `idx_estimate_activity_version (estimate_id, activity_code, version_no)`
  4. `idx_changed_by_changed_at (changed_by, changed_at)` (audit/reporting)
- **Monitoring routine:** harian (volume rows/hari, event mix); mingguan (top estimate history terbanyak, hash mismatch sample); bulanan (ukuran tabel data/index MB, tren 30 hari).
- Skrip: `SQL_ESTIMATE_ACTIVITY_HISTORY_PERFORMANCE_STEP4.sql`, `..._MONITORING_STEP4.sql`, `..._RETENTION_STEP3.sql`.

### 4.10 Panduan Eksekusi Manual SQL

File SQL yang dipakai (prefix `rise_`):
1. `SQL_ESTIMATE_ACTIVITY_HISTORY_MANUAL_EXEC.sql` (DDL + seed)
2. `SQL_ESTIMATE_ACTIVITY_HISTORY_ROLLBACK.sql` (opsional)
3. `SQL_ESTIMATE_ACTIVITY_HISTORY_VERIFY.sql` (semua baris harus `PASS`)
4. `SQL_ESTIMATE_ACTIVITY_ALIGN_TO_DOC_STATUS.sql` (jika pernah pakai flow lama)
5. `SQL_ESTIMATE_ACTIVITY_HISTORY_IMMUTABILITY.sql` (blok update/delete via trigger)
6. `SQL_ESTIMATE_ACTIVITY_HISTORY_MONITORING_STEP4.sql`
7. `SQL_ESTIMATE_ACTIVITY_HISTORY_PERFORMANCE_STEP4.sql`
8. `SQL_ESTIMATE_ACTIVITY_HISTORY_RETENTION_STEP3.sql`

**Retensi Step3 (idempoten, tanpa purge):** menyalin data lama (default > **730 hari**) ke tabel arsip. Output dicek: `candidate_rows`, `archived_rows_last_run`, `archive_rows_older_than_threshold`, `purge_candidate_rows` (hanya estimasi, bukan delete). Karena ada trigger immutability, script **tidak** purge; bila ingin purge: maintenance window → backup → drop trigger sementara → purge batch terkontrol → aktifkan kembali trigger. Rekomendasi: arsip **1x/bulan**, simpan bukti audit, cek `information_schema.TABLES`.

### 4.11 Hardening Enterprise — Status per Fase (per 2026-04-16)

| Fase | Target | Cakupan | Status |
|---|---|---|---|
| 0 Baseline & Safety | 0,5 hari | Freeze fitur, backup 3 tabel, catat baseline metric (save latency, error rate, volume/hari) | Tidak selesai |
| 1 Immutability & Atomicity | 1–2 hari | Insert-only, hash wajib, validasi hash saat baca, 1 transaksi atomik, logging error terstruktur | **Selesai** |
| 2 Concurrency & Version Safety | 1–2 hari | `version_no` paralel, retry/lock, cegah over-logging no-op, observability konflik | **Selesai** |
| 3 Security & Compliance | 2–3 hari | Definisi PII, masking, retensi/arsip, kontrol akses role | PII+masking **selesai**; retensi & role access **in progress** |
| 4 Performance & Scale | 1–2 hari | Optimasi index, strategi growth, monitoring (write latency, hash mismatch, version conflict) | **Selesai** (index + monitoring SQL dieksekusi) |
| 5 UX & I18N Cleanup | 1 hari | Hilang hardcoded text, diff konteks bisnis, responsivitas timeline | Tidak selesai |
| 6 UAT & Rollout | 1–2 hari | UAT backend, UAT UX timeline, pilot, rollout bertahap, hypercare 3–7 hari | Tidak selesai |

**Bukti eksekusi Fase 1–4 (2026-04-16, PIC Codex/Team):**
- SQL trigger immutability dieksekusi di server → update/delete history diblok di level DB.
- Monitoring SQL pack: **8 query sukses, 0 error/warning**; integrity duplicate version **0 row**.
- Performance SQL: **19 query sukses, 0 error/warning**, index optimization applied; verifikasi index mengembalikan **10 baris**.
- Role permission `can_view_estimate_activity_snapshot` ditambahkan (controller + role form + language key) — **menunggu deploy + UAT role matrix**.
- SQL retention & archive pack disiapkan — **menunggu eksekusi di server**.

Risk register: race condition save paralel; pertumbuhan tabel history cepat; eksposur data sensitif; hardcoded label i18n. Approval checkpoint (approval teknis, compliance/security, rollout production) masih kosong.

### 4.12 Checklist Implementasi Task-Level (2 Sprint)

Checklist harian (pakai `[x]`, isi PIC/tanggal/bukti; jangan lanjut sebelum prasyarat). Sprint 1 = Fondasi (minggu 1–2): A) Finalisasi aturan & scope (A1 freeze activity code Estimate ke `DRAFT,SENT,ACCEPTED,DECLINED`; A2 rule transisi + sinkronisasi `activity_code ↔ estimate.status`; A3 role akses snapshot); B) Database & integritas (B1–B7: migration 3 tabel, seed master, index/unique, DB privilege append-only, script rollback); C) Service logging inti (C1–C7: canonical JSON, SHA-256, atomic transaction, `FOR UPDATE` lock, versioning 4 angka, no-op detection, validasi transisi); D) API dasar timeline (D1 list paged, D2 detail snapshot, D3 compare).

Sprint 2 = UX, Hardening, UAT, Go-Live (minggu 3–4): E) Timeline UI (E1–E6); F) Security & performance hardening (F1 role, F2 hash read, F3 uji 5.000 history <2s, F4 concurrency 2 user, F5 retensi 24 bulan + archive table); G) Backfill & data operasional (G1 script `SYSTEM_SYNC` untuk existing, G2 staging, G3 production off-peak); H) UAT & sign-off (H1 F-01..F-21, H2 N-01..N-08, H3 checklist UX, H4 fix & re-test, H5 sign-off bisnis/QA/teknis); I) Go-live & hypercare (I1 deploy, I2 monitoring 48 jam, I3 tutup hypercare + laporan).

**DoD:** semua event menghasilkan snapshot valid; hash terisi & tervalidasi; append-only di API & DB; timeline stabil di data besar; rule validasi sesuai; UAT ≥95%; tidak ada regresi alur estimate.

---

## 5. Estimates Pivot Enterprise & KPI

### 5.1 Prinsip & Endpoint

Tujuan blueprint: menutup gap laporan pivot agar setara enterprise **tanpa menambah tabel baru**, dengan memaksimalkan data yang sudah ada, menjaga kompatibilitas dengan `/estimates/pivot_report`.

Prinsip desain: satu sumber data inti (base dataset) dipakai ulang untuk banyak pivot; semua pivot konsisten terhadap filter global; KPI punya rumus baku; pisahkan konsumsi eksekutif vs operasional.

**Endpoint page:** `GET /estimates/pivot_report`.

**Endpoint data terstruktur (P1 + P2, aktif):**
- `estimates/pivot_summary_data`
- `estimates/pivot_owner_performance_data`
- `estimates/pivot_channel_performance_data`
- `estimates/pivot_client_data`
- `estimates/pivot_lead_data`
- `estimates/pivot_aging_data`
- `estimates/pivot_exception_data`

**Filter global wajib:** `owner_id`, `role_profile`, `status`, `time_frame`, `date_from`, `date_to`, `date_basis`, `source_id`, `sub_source_id`, `entity_type`. Preset time frame: `This week`, `This month`, `This quarter`, `YTD`, `Rolling 30D`, `Rolling 90D`; date basis: `estimate_date` / `created_at` / `accepted_at`.

### 5.2 Rumus KPI Baku (KPI Contract)

| KPI | Rumus |
|---|---|
| `Estimate count` | jumlah dokumen estimate |
| `Estimate value` | SUM nilai estimate |
| `Accepted` / `Declined` | count status accepted / declined |
| `Accepted rate (%)` | `Accepted / (Accepted + Declined) * 100` (denominator 0 → `0.00%`) |
| `Lead count` / `Client count` | jumlah estimate terkait lead / client |
| `Item lines` / `Item qty` | total baris item / SUM qty item |
| `Avg deal size` | `Estimate value / Estimate count` |

**KPI Contract (enterprise):** setiap KPI punya `kpi_id`, `business_definition`, `sql_formula_reference`, `grain`, `allowed_dimensions`, `filter_behavior`, `null_zero_rule`, `inclusion_exclusion_rule`, `data_owner`, `approval_signoff` (Direksi, Sales Ops, Finance). Standarisasi definisi `accepted_rate` sudah didokumentasikan.

### 5.3 Struktur Tab per Role

- **Tab A — Executive Summary (Direksi):** KPI cards (total estimate/value, accepted rate, accepted/declined, avg deal size); Pivot `Month x Status`; `Channel x Status`; Top 10 Owner by value; Top 10 Client by value.
- **Tab B — Sales Manager:** KPI cards + tren mingguan; `Owner x Week x Status`; `Owner x Channel`; `Owner x Lead/Client`; Aging bucket (`0-3`,`4-7`,`8-14`,`>14` hari).
- **Tab C — Sales Ops:** `Source x Sub source x Status`; `Client x Status`; `Lead x Status`; exception list (draft tua, nilai nol, item qty ekstrem).
- **Tab D — Detail Explorer (opsional):** tabel detail export Excel dengan filter global sama, untuk audit angka pivot.

### 5.4 Mapping Kebutuhan vs Gap

- **Sudah ada:** `Month x Status`; `Owner x Week x Status`; KPI dasar accepted/declined/value/count.
- **Belum lengkap (target):** laporan per user dengan ranking + kontribusi; tujuan submit/channel (source-sub source); konsumen (client-centric); lead-centric; time frame preset konsisten; custom range + date basis selector.

**Prioritas implementasi (tanpa ubah skema DB):**
- **P1:** filter global lengkap; tab role profile otomatis dari role user (override untuk admin); laporan per user + channel.
- **P2:** laporan client + lead; aging & exception table.
- **P3:** executive summary polish + optimasi performa query.

### 5.5 Implementasi Teknis P1 (Checklist File-by-File)

**A. `app/Controllers/Estimates.php`:**
- [x] Parser filter global single function, contoh `buildPivotFilterInput()`.
- [x] Resolver timeframe + custom range; resolver `date_basis`; role profile auto resolver dari session/user role.
- [ ] Access scope check sebelum query (row-level policy).
- [x] Endpoint: `pivot_summary_data()`, `pivot_owner_performance_data()`, `pivot_channel_performance_data()`.
- [x] Standarkan payload response JSON (`success`, `filters_applied`, `captured_at`, `rows`, `totals`).
- [x] Validasi tanggal invalid; [ ] range terlalu besar (belum); [x] enum tidak dikenal.

**B. `app/Controllers/Reports.php`:** daftar route/menu report eksekutif atau redirect ke `/estimates/pivot_report`; selaraskan permission check.

**C. View pivot (kandidat `app/Views/estimates/index.php`):** [x] filter global lengkap (time frame, custom date range, date basis, source/sub source, entity type); [x] role profile default auto readonly non-admin; [x] wiring AJAX ke 3 endpoint P1; [x] tampilkan `captured_at`; [ ] warning filter invalid/no data.

**D. Language files:** [x] tambah key label filter/KPI baru di `app/Language/english/custom_lang.php` & `app/Language/Indonesian/custom_lang.php` agar konsisten `app_lang`.

**Query mapping matrix (P1):**
- Owner performance: group by `owner`,`status`,bucket waktu (`week`/`month`); metrics: count, value, accepted, declined, accepted_rate, lead_count, client_count.
- Channel performance: group by `source`,`sub_source`,`status`; metrics: count, value, accepted_rate, avg_deal_size.
- Summary: grand aggregate + optional trend by month.

### 5.6 Governance & NFR (Enterprise)

- **Data Governance:** satu semantic definition layer; data dictionary wajib; lineage tabel sumber → KPI; reconciliation rule (kartu KPI = agregasi tabel detail untuk filter sama).
- **Security & Access Control:** row-level security per role + struktur atasan-bawahan; scope Direksi=all, Sales Manager=timnya, Sales Ops=operasi sesuai domain; audit trail untuk akses laporan, export, perubahan definisi KPI.
- **NFR:** data freshness SLA near real-time ≤15 menit atau batch harian; response p95 ≤3 detik (filter umum), p99 ≤8 detik (rentang besar); concurrency ≥50 user tanpa degradasi kritis.
- **Performa:** pre-aggregation dimensi berat; cache terkontrol per kombinasi filter; index pada date basis, owner, status, source/sub source, lead/client flag; materialized summary layer bertahap.
- **QA otomatis:** unit test rumus KPI inti; integration test endpoint pivot; reconciliation test (pivot vs SQL baseline); regression test; UAT evidence template berisi screenshot + filter + hasil numerik.
- **Monitoring/Alerting/Runbook:** monitor error rate, latency p95/p99, freshness; alert refresh gagal, latency melewati threshold, mismatch rekonsiliasi; runbook incident (diagnosa, fallback, eskalasi PIC).
- **Compliance/Privacy/Retention:** masking PII per role; kebijakan retensi resmi; kontrol export (siapa boleh, watermark, log export).
- **Change Management:** version KPI format `KPI_VERSION`; setiap perubahan rumus wajib change note + impact analysis + backtest + approval lintas fungsi + rollback plan.
- **Operating Model (RACI min):** Product owner laporan = Sales Ops Head; data owner = tim data/BI; technical owner = engineering owner Estimates; validator bisnis = Sales Manager + Finance; approver final = Direksi.

### 5.7 Progress Snapshot Blueprint (Update 2026-04-19)

**Sudah selesai (implementasi kode):**
- P1 core: filter global konsisten; endpoint aktif summary/owner/channel; UI pivot memanggil endpoint via AJAX.
- P2 core: endpoint client/lead/aging/exception aktif; UI tabel tambahan aktif (Client performance, Lead performance, Aging bucket, Exception list).
- I18n: label pivot baru dipindah ke `app_lang` (EN/ID).
- Bugfix terakhir: filter `All time` tidak lagi mewarisi `date_from/date_to/month` dari state sebelumnya.

**Belum selesai (sesi lanjutan):**
- UAT komprehensif per role (Direksi, Sales Manager, Sales Ops).
- SQL baseline reconciliation untuk semua blok P1+P2.
- Hardening validasi input (`time_frame=custom` harus valid range; guardrail rentang tanggal terlalu panjang).
- Hardening security (audit log akses/report/export; verifikasi row-level policy lintas role).
- P3: optimasi performa query (indexing/caching/pre-aggregation); final executive polish.

**Next action:** (1) UAT + reconciliation numerik per blok; (2) tutup gap validasi input + guardrail rentang tanggal; (3) lanjut P3.

### 5.8 Plans & NFR Target Summary

- **Data freshness:** near real-time ≤15 menit atau batch harian (pilih & tetapkan).
- **Response time:** p95 ≤3s, p99 ≤8s.
- **Concurrency:** minimal 50 user.
- **Re-export:** Excel/Print parity dengan UI (UAT-NF-02).
- **Role profile:** otomatis dari role; admin boleh override; non-admin tidak bisa override di luar haknya.

---

## 6. Project Governance: RACI, Sprint Plan, Weekly Checklist, UAT Evidence

### 6.1 RACI Final (EST-RACI-ENT-FINAL, Effective 2026-04-17)

Dokumen kanonik: `ESTIMATES_ENTERPRISE_RACI_MATRIX.md`. Alias: `ESTIMATES_ENTERPRISE_RACI_FINAL_PIC.md` (semua perubahan wajib di dokumen kanonik).

**PIC Final (role-based, 8 peran):**

| Kode | Fungsi / PIC Jabatan Final |
|---|---|
| EXE | Executive Sponsor — Director of Sales and Marketing |
| BO | Business Owner — Head of Sales |
| PO | Product Owner — Product Owner CRM |
| TL | Technical Owner — Tech Lead CRM |
| BI | Data Governance Owner — BI and Data Analytics Lead |
| QA | Quality Owner — QA Lead CRM |
| SO | Operational Owner — Sales Operations Lead |
| DEV | Delivery Owner — Backend and Frontend Lead |

Legend: R=Responsible, A=Accountable, C=Consulted, I=Informed.

**Matriks Governance & KPI:** Menetapkan KPI resmi (EXE A; BO/PO/BI R); definisi Accepted Rate/Aging (BO A; PO/BI R); pivot per role (EXE A; BO/PO R); SLA dashboard (EXE A; BO/PO R); toleransi rekonsiliasi (EXE A; PO/BI R).

**Matriks Build & Integration:** mapping endpoint/query→KPI (PO A; BI/DEV R); query/report backend (TL A; DEV R); UI pivot & filter (PO A; DEV R); role access control (TL A; DEV R); export parity (TL A; DEV R).

**Matriks UAT & Go-Live:** menyiapkan skenario & evidence (QA A; SO/DEV R); UAT KPI & pivot by role (QA A; BO/SO R); rekonsiliasi UI vs DB (BI A; SO R); security & scope validation (QA A; SO/DEV R); defect triage P0/P1 (PO A; TL/BI/DEV R); Go/No-Go (EXE A; BO/PO R).

**Escalation Matrix:**

| Trigger | Severity | Owner Eskalasi | SLA |
|---|---|---|---|
| KPI total mismatch > tolerance | P0 | PO + BI + TL | ≤4 jam |
| Role access leakage | P0 | TL + QA | ≤4 jam |
| Dashboard unusable (blocking) | P1 | TL + DEV | ≤8 jam |
| UAT blocker lintas tim | P1 | PO | ≤1 hari kerja |
| KPI definition conflict | P1 | EXE + BO + PO | ≤2 hari kerja |

Approval Board (EXE, BO, PO, TL, BI, QA, SO) — belum diisi.

### 6.2 Sprint Plan (Estimates Enterprise)

| Sprint | Durasi | Fokus | Exit Criteria |
|---|---|---|---|
| Sprint 0 — Foundation | 1 minggu | KPI dictionary, blueprint pivot, endpoint-query mapping, AC UAT | KPI tidak ambigu; owner setuju blueprint |
| Sprint 1 — KPI Core & Baseline Pivot | 2 minggu | KPI cards (count, value, accepted rate, aging 3+/7+), pivot `Owner x Month x Status`, role access baseline | KPI sesuai formula; tanpa defect P0 security |
| Sprint 2 — Role Pivot & Export Reliability | 2 minggu | Pivot final Direksi/BO/SO, filter enterprise, export parity | Parent-child total konsisten; export parity pass |
| Sprint 3 — Audit & Performance Hardening | 2 minggu | Activity audit board, reconciliation automation, perf tuning | p95 sesuai SLA; rekonsiliasi delta ≤tolerance |
| Sprint 4 — UAT Final & Go-Live Readiness | 1 minggu | Full UAT, closure P0/P1, Go/No-Go + sign-off | UAT KPI/security 100%; tanpa P0/P1; sign-off |

**Total 8 minggu.** Deliverable per sprint (KPI Baseline Doc, Endpoint-Query Mapping Matrix, UAT master test case v1; dashboard baseline; query pack rekonsiliasi; 3 dashboard role-based; export conformance report; audit dashboard; reconciliation job harian; performance benchmark report; UAT evidence; defect closure; go-live checklist).

**Backlog prioritas:** High — KPI formula lock (PO+BI), endpoint/query lineage (BI+DEV), role-based security validation (TL+QA), reconciliation automation (BI+DEV). Medium — advanced audit insights (SO+BI), predictive prioritization model (BI).

**Capacity:** PO 30%, TL 40%, Backend Dev 100%, Frontend Dev 80%, BI Analyst 80%, QA 80%, Sales Ops SME 30%.

**Quality gates per sprint:** KPI definition approved (S0); unit/integration + security role test (S1–S4); reconciliation pass (S1 partial → S2+ full); UAT pass (S2 partial → S3 partial → S4 full); sign-off ready (S3 partial → S4 full).

**Risk register sprint plan:** KPI ambiguity (High, mitigation KPI dictionary approval board, PO); mismatch UI vs DB (High, daily reconciliation + threshold alert, BI); performance drop filter kompleks (High, aggregate table + indexing + caching, TL); access control leak (High, security UAT matrix + regression, QA); scope creep (Medium, change control weekly, PO).

**Go-live checklist:** KPI & pivot doc final; RACI & escalation approved; monitoring dashboard active; rollback plan validated; hypercare roster published.

**Hypercare (2 minggu):** reconciliation report harian (BI); defect triage harian (QA+TL); business review mini-standup 3x/minggu (PO+BO+SO); KPI drift review mingguan (BI+EXE).

**Success metrics post go-live:** dashboard adoption by role ≥80%; draft aging 7+ turun ≥30% dalam 1 kuartal; accepted rate naik ≥10% dalam 1 kuartal; rekonsiliasi mismatch <0,5% stabil 4 minggu.

### 6.3 Weekly Execution Checklist (per PIC)

**Cadence:** Senin (KPI validation + priority queue refresh); Selasa (channel & owner deep-dive + action plan); Rabu (data quality & access control audit); Kamis (defect triage + reconciliation follow-up); Jumat (weekly review + risk register update).

**Checklist ringkas per peran (Sen–Jum):**
- **EXE:** review KPI ringkas (Sen+Jum → decision memo); validasi target kuartalan (Jum); approve eskalasi P0/P1 (as needed).
- **BO:** review owner leaderboard & backlog draft 7+ (Sen+Jum → action priority list); fokus account per owner (Sel → coaching plan); review conversion source/sub-source (Sel → channel decision).
- **PO:** cek consistency KPI definition vs dashboard (Sen → KPI consistency note); prioritas backlog defect (Kam → sprint board); weekly go/no-go readiness (Jum → readiness report).
- **TL:** review p95 dashboard (Sen+Kam → perf summary); review access matrix & security logs (Rab → security note); validasi fix P0/P1 & deployment safety (Kam+Jum).
- **BI:** jalankan reconciliation UI vs DB (Sen+Rab+Kam → reconciliation sheet); verifikasi quality metric (Rab → data quality report); review trend KPI 4 minggu (Sel+Jum → trend insight).
- **QA:** regression smoke endpoint kritis (Sen+Kam → test run evidence); validasi UAT matrix status (Rab+Kam → UAT status board); defect triage & retest (Kam+Jum → defect closure report).
- **SO:** validasi queue prioritas (incomplete, urgent 3+, urgent 7+) (setiap hari → priority queue log); cek kepatuhan follow-up owner (Sen+Rab+Jum); verifikasi data source/sub-source & domain (Sel+Rab → data correction list).
- **DEV:** monitor error endpoint report (setiap hari → error dashboard); hotfix P0/P1 (as needed → patch note); refactor/perf task sprint (Sel–Kam → dev progress note).

**Weekly meeting pack:** KPI Ops Sync 30mnt (BO, SO, BI); Defect and Quality Sync 30mnt (QA, TL, DEV, PO); Executive Review 30mnt (EXE, BO, PO, BI).

**Weekly completion criteria:** reconciliation report ditandatangani BI+QA; tanpa defect P0 >24 jam; backlog urgent 7+ punya owner action plan; security/access anomalies ditutup atau di-eskalate; weekly decision log tersedia. Evidence log template per PIC: `Week | PIC | Checklist Completion % | Open Risk | Open P0/P1 | Notes`.

### 6.4 UAT Evidence Template

Scope UAT (5 scope, semua included): S01 KPI Core (count, value, accepted rate, aging); S02 Pivot per role (Direksi, BO, SO); S03 Security & access scope; S04 Export consistency (Excel/Print); S05 Activity audit timeline/snapshot/compare.

**UAT Case Matrix (inti):**
- UAT-KPI-01 Estimate Count — UI aggregate vs DB aggregate, match 100%.
- UAT-KPI-02 Estimate Value — currency total UI vs DB, match (rounding policy).
- UAT-KPI-03 Accepted Rate — formula `accepted/(accepted+declined)`.
- UAT-KPI-07 KPI Core API — payload & consistency `kpi_core_data`.
- UAT-KPI-04 Draft Aging 3+ — boundary day 2/3 (day 3 included).
- UAT-KPI-05 Draft Aging 7+ — boundary day 6/7 (day 7 included).
- UAT-PVT-01 `Owner x Month x Status` — drill-down, parent-child totals konsisten.
- UAT-PVT-07 Owner×Month×Status API — `pivot_owner_month_status_data`, sum pivot = KPI total.
- UAT-PVT-02 Source/Sub-source; UAT-PVT-03 Aging Board; UAT-PVT-04 Activity Audit (event_type/activity_code/actor filters).
- UAT-SEC-01/02/03 — role Direksi (global), BO (team-only), SO (audit panel).
- UAT-SEC-04 Snapshot permission — tanpa permission buka snapshot → 403.
- UAT-NF-01 Performance — heavy pivot 12 bulan, meets SLA. UAT-NF-02 Export — Excel/Print vs UI identik.

**Evidence minimum:** EV-01 screenshot KPI overview; EV-02 screenshot pivot drill-down; EV-03 file export Excel; EV-04 query output rekonsiliasi DB; EV-05 screenshot access denied (403); EV-06 log error (opsional). Data set referensi: DS01 production snapshot anonymized, DS02 synthetic test data, DS03 manual edge-case.

**Reconciliation Sheet toleransi:** Estimate Count 0; Estimate Value ≤0,5%; Accepted Rate ≤0,5%; Draft 3+ 0; Draft 7+ 0; Ready SO 0.

**Entry criteria:** data set referensi tervalidasi; build release di UAT; semua endpoint aktif. **Exit criteria:** tanpa defect P0/P1; semua case KPI/security PASS; reconciliation delta dalam tolerance; BO sign-off. Sign-off: Business Owner, QA Lead, Product Owner, Tech Lead.

---

## 7. Leads (Prioritas Data Spec) & Timeline Hold

### 7.1 Dokumen Final V1 — Tanggal 2026-04-17, Status "Final Disetujui User"

Acuan integrasi fitur Estimate pada modul Leads. Fokus: tracking aktivitas lead lengkap dengan kontrol akses owner, atasan langsung, dan shared user saat shared aktif.

**Tujuan bisnis:** (1) aktivitas lead terkait estimate tercatat & dapat diaudit; (2) alur follow-up sales tertib dengan auto-kontrol status shared saat estimate dibuat; (3) aturan hak akses owner & shared user konsisten.

**In Scope:** estimate dapat dibuat dari tahap lead mana pun; auto update `lead_shared` saat create estimate; permission matrix lead+estimate pada konteks lead; audit trail event penting; **soft delete only**.
**Out of Scope:** otomasi perubahan lead→client; hard delete; perubahan workflow modul lain.

**Aturan proses inti:**
1. Estimate boleh dibuat pada tahap lead apa pun.
2. Saat `create estimate` pada lead, sistem **auto set `lead_shared = OFF`**.
3. `lead_shared` boleh diaktifkan kembali (`ON`) manual.
4. Perubahan status lead→client **hanya manual** oleh user berwenang.

**Aturan akses:**
- **Estimate pada konteks lead** (view/edit/cancel): `owner estimate`, `owner lead`, atau atasan langsung (1 level) dari owner estimate/owner lead.
- **Shared user pada lead** saat `lead_shared = ON`: boleh `edit/update` data lead dan `deactive` lead (soft delete). Batasan: hak shared **tidak otomatis** berlaku ke estimate; shared user **tidak boleh** mengubah lead→client.
- Owner lead & owner estimate tidak wajib sinkron; atasan yang diakui untuk eskalasi = **1 level langsung**.

**Aturan delete:** semua delete wajib soft delete; hard delete tidak diperbolehkan untuk lead maupun estimate.

**Audit trail:** event wajib `create`, `update`, `delete (soft)`, `status change`. Metadata minimal per log: `actor`, `timestamp`, `action/event_type`, `field_changed`, `old_value`, `new_value`, `source` (`manual`/`system`). Event kritis eksplisit: create estimate (termasuk auto shared OFF oleh sistem), perubahan manual `lead_shared`, aksi manual ubah lead→client, aksi edit/update/deactive oleh shared user saat shared aktif.

**Timeline Aktivitas Lead:** halaman `/leads/view/{id}`, panel kanan. Sumber data gabungan event lead + estimate. Baris memuat `timestamp`, `event_type`, `entity` (lead/estimate), `actor`, ringkasan perubahan (mis. `lead_shared: ON → OFF`), indikator `source`. Aksi: `Lihat` (detail field_changed/old/new), `Banding` (bandingkan sebelum-sesudah pada event update/status change; non-aktif bila event tak punya pasangan, mis. create). Filter: tipe event (Semua/create/update/delete/status change), entitas (Semua/lead/estimate), sumber (Semua/manual/system). Sorting default terbaru→terlama; default 20 event terbaru; pagination `Load more`. Integritas: append-only; event sistem wajib `source=system`; event user `source=manual`; soft delete tampil sebagai `delete (soft)`.

### 7.2 Acceptance Criteria & Checklist (13 item, seluruh [x] tercentang)

AC: create estimate dari stage lead mana pun; auto shared OFF; shared ON manual; shared user edit/update/deactive saat ON; shared user tak bisa set client; hak akses estimate owner/atasan 1 level; tanpa hard delete; semua event audit muncul; lead→client manual. Checklist implementasi (12 item [x]) & Checklist UAT (14 item [x]) **seluruhnya tercentang** pada dokumen final.

**Bukti UAT Teknis (verifikasi kode):**
1. Delete file lead hanya soft delete record (tanpa hapus fisik file) — `Leads.php` (`delete_file`).
2. Update foto contact lead tidak menghapus file lama permanen — `Leads.php` (`save_profile_image`).
3. Delete comment estimate hanya soft delete — `Estimates.php` (`delete_comment`).
4. Delete image estimate tidak menghapus file fisik di storage — `Estimates.php` (`delete_image`).
5. Validasi scan kode: tidak ada `delete_app_files(...)` / `delete_file_from_directory(...)` di `Leads.php`, `Estimates.php`, `Clients_model.php`.
6. Shared-only user diblokir convert lead→client — `Leads.php` (`make_client_modal_form`, `save_as_client`) dengan guard akses convert.

### 7.3 Prioritas Implementasi (P0 / P1) & Urutan Eksekusi

**Catatan fase:** bagian otomasi convert-to-client diabaikan fase ini (guard shared tetap); fokus = shared behavior, permission estimate, audit, timeline lead.

**P0 (wajib dulu):** auto shared OFF saat create estimate; penyesuaian permission estimate ke matrix final; shared user boleh edit/update/deactive saat ON; hardening endpoint share agar validasi akses per-lead wajib.

**Breakdown per file (P0):**
1. `app/Controllers/Estimates.php` — setelah create estimate sukses, set lead sharing OFF (`is_public=0`, `is_selected_members=0`) pada lead terkait; gunakan transaksi sama dengan save estimate; tambah event audit `system` untuk auto shared OFF.
2. `app/Controllers/Security_Controller.php` — refactor `can_access_this_estimate()` agar akses mengikuti owner estimate / owner lead / atasan langsung 1 level; pertahankan kompatibilitas scope `all/team/own/own_only`, tapi rule matrix final jadi guard utama.
3. `app/Models/Estimates_model.php` — selaraskan query list/filter dengan rule akses; shared lead tidak otomatis boleh akses estimate bila tidak memenuhi matrix.
4. `app/Controllers/Leads.php` — ubah gate edit/update/deactive untuk shared user; endpoint `update_share()` WAJIB panggil `validate_lead_access($lead_id)`; deactive tetap soft delete.
5. `app/Views/leads/lead_form_fields.php` + rendering row di `Leads.php` — lepas pola UI "shared by = view only" untuk shared ON; sesuaikan disable/lock icon mengikuti permission final.

**P1 (setelah P0 stabil):** panel Timeline Aktivitas di `app/Controllers/Leads.php` + `app/Views/leads/view.php`; service/model histori lead-estimate dengan endpoint data timeline filter `event_type`,`entity`,`source`,`limit`,`offset`; endpoint detail `Lihat` & `Banding`; audit trail terstruktur metadata minimal.

**Urutan eksekusi:** (1) `Estimates.php` auto shared OFF + audit system event; (2) refactor `Security_Controller.php` + sinkron `Estimates_model.php`; (3) rapikan `Leads.php` + `lead_form_fields.php`; (4) tambah timeline gabungan; (5) UAT checklist P0 dulu, lalu P1.

**Kriteria siap fase ini:** create estimate selalu mematikan shared otomatis; shared user (ON) bisa edit/update/deactive; akses estimate per matrix owner/atasan 1 level; event audit penting tercatat metadata minimal; timeline lead gabungan tampil & dapat difilter.

### 7.4 Gap-to-Compliance RBAC (ISO/IEC 27001:2022 Annex A)

**Status ringkas:** RBAC per role sudah ada (`roles.permissions`) & enforcement di controller; row-level access (`own/team/all/shared`) sudah tersedia. Gap terbesar ada pada **governance evidence**: audit perubahan hak akses belum konsisten, review akses periodik belum terdokumentasi, SoD belum diformalkan.

**Checklist kontrol (7 kontrol):**
1. Kebijakan access control terdokumentasi (least privilege) — **Partial**; gap: belum ada SOP formal. Aksi: buat SOP "Access Control Policy" + owner & siklus review (min per 6 bulan). Evidence: SOP bertanggal/nomor versi/approver + notulen review.
2. RBAC terpusat — **Implemented (teknis)**; gap: masih ada role ID hardcoded di controller. Aksi: refactor hardcoded role check → permission-based; mapping role→permission di layer role settings. Evidence: PR diff + test akses sebelum/sesudah.
3. JML (Joiner-Mover-Leaver) — **Partial**; gap: provisioning/deprovisioning belum dipaketkan sebagai alur audit formal. Aksi: definisikan workflow JML + checklist approval dua pihak untuk role sensitif. Evidence: ticket JML tersimpan + rekaman approval & timestamp.
4. **Segregation of Duties (SoD)** role sensitif — **Partial**; gap: maker-checker perubahan permission belum wajib. Aksi: **wajibkan approval kedua** untuk perubahan role/permission kritikal; **batasi siapa boleh memberi hak `can_manage_user_role_and_permissions`**. Evidence: matriks SoD + log approval berpasangan (requester + approver).
5. Logging & accountability perubahan akses — **Partial**; gap: perubahan permission role belum konsisten masuk audit trail. Aksi: pastikan endpoint perubahan permission/role selalu `init_activity_log` atau audit logger ekuivalen; simpan before/after JSON permission; simpan actor, waktu, alasan. Evidence: record log + query laporan audit.
6. Monitoring & review akses berkala — **Belum formal**; gap: belum ada job review owner/team/shared access periodik. Aksi: report bulanan user-role-permission + owner hierarchy + shared members; recertification akses per kuartal. Evidence: hasil export review + berita acara approval/cabut akses.
7. Validasi berkelanjutan (testing) — **Partial**; gap: belum ada suite automated authorization test memadai. Aksi: integration test matrix akses (`all/team/own/own_only/shared`) + negative test privilege escalation. Evidence: file test + CI result + coverage skenario.

**Rencana 3 tahap:** Tahap 1 Quick Wins (1–2 minggu) — audit log penuh perubahan permission/role; refactor hardcoded role check terkritikal; template SOP access control + SoD. Tahap 2 Hardening (2–4 minggu) — maker-checker role sensitif; report recertification; integration tests authorization. Tahap 3 Audit Readiness (1–2 minggu) — kumpulkan evidence 3 bulan; internal control review; tutup temuan minor dry-run audit.

**DoD siap audit internal (6 item, belum tercentang):** semua perubahan role/permission tercatat before/after+actor+waktu+alasan; tanpa hardcoded bypass role sensitif; recertification periodik terdokumentasi; maker-checker aktif; test authorization lulus (positif & negatif utama); SOP access control + SoD disetujui manajemen. **Artefak bukti minimum:** dokumen kebijakan access control & SoD (versi+approval); log perubahan role/permission (before/after); daftar user-role-permission bulanan; berita acara review berkala; hasil test authorization + CI.

### 7.5 Lead Activity Timeline — Status HOLD (2026-04-18)

**Ringkasan masalah:** nilai perubahan wilayah (province/city/subdistrict/subdivision) masih tampil **ID** (belum konsisten jadi label); perilaku auto-show last activity berubah-ubah antar revisi dan perlu finalisasi.

**Task lanjutan (belum selesai):** verifikasi root cause via payload `activity_logs.changes` per event; finalisasi resolver field alias wilayah (`province/propinsi/province_id/propinsi_id/st_province`; `city/kabupaten/city_id/kabupaten_id/st_city`; `subdistrict/kecamatan/subdistrict_id/kecamatan_id`; `subdivision/kelurahan/subdivision_id/kelurahan_id`); fallback resolver bila `postal` tidak ditemukan (mis. simpan snapshot label saat log dibuat); regression check field non-wilayah; **finalisasi behavior auto-show** (opsi A auto-open last activity vs opsi B manual click only — pilih 1 & lock); validasi cache layer (browser cache, OPcache/PHP cache server, pastikan deploy tak pakai JS lama); rapikan key `custom_lang` agar tidak fallback ke `default_lang.*`; UAT end-to-end 5 event utama (create, update, status change, share on/off, owner change).

**Kriteria done:** semua perubahan wilayah tampil label; tombol timeline stabil; tanpa string fallback salah (`default_lang.*`); UAT pass seluruh event utama.

**Lokasi teknis utama:** `app/Services/LeadActivityTimelineService.php`, `app/Views/leads/lead_activity_timeline_panel.php`, `app/Language/english/custom_lang.php`, `app/Language/Indonesian/custom_lang.php`.

---

## 8. Approval & Segregation of Duties (SOD)

Dokumen: `edit-approve-sales.md` (bersifat konsultatif, perlu disesuaikan kebijakan audit internal).

**Kasus:** dari Sales CRM (contoh: Pesanan Dinas Kehutanan Prov. Kalimantan Utara) ada kebutuhan penyesuaian data (edit) oleh pihak berwenang approval.

**Dilema:** secara operasional atasan berwenang mengoreksi data demi kelancaran bisnis, tapi prinsip **SOD** melarang satu orang memegang dua fungsi: **Eksekutor** (mengubah kuantitas/varian/harga) dan **Approver** (mengesahkan). Risiko: hilangnya kontrol "mata kedua" (*four-eyes principle*) → celah manipulasi atau kesalahan tak terdeteksi.

**Strategi efisiensi untuk tim ramping:**
- **A. Navigasi Risiko berbasis "Delta Control":** batasi ruang lingkup edit — approver hanya boleh edit **Kuantitas** (menyesuaikan stok) atau **Varian**; **kunci Harga** satuan agar tidak bisa diubah approver tanpa otorisasi tambahan dari Departemen Keuangan.
- **B. Gudang sebagai "Last Gatekeeper":** meski atasan edit, Gudang berhak verifikasi ulang sebelum barang keluar; jika tidak sesuai fisik/sistem, Gudang berwenang menginterupsi.
- **C. Digital Audit Trail (wajib):** catat **Who** (siapa mengubah), **What** (sebelum vs sesudah), **Why** (alasan — kolom catatan wajib diisi).

**Kesimpulan & langkah ideal:**
1. Perubahan **minor:** atasan edit → sistem catat log → atasan approve → Gudang verifikasi fisik.
2. Perubahan **mayor (Harga/Diskon):** gunakan tombol **Reject** → Salesman edit ulang → atasan approve (menjaga integritas data finansial).

**Hubungan dengan perubahan pada `rencana_penyelesaian.md`:** ada inisiatif teknis memisahkan pengajuan dari otorisasi lewat status baru `siap_diorder` (lihat §11 Temuan Lintas-Dokumen).

---

## 9. Integrasi CRM → Subsidiary → Holding (Flowchart Teknis)

### 9.1 Master Map Arsitektur

Sistem: **CRM (`san_ibb_master`) → Subsidiary (`san_sarana_8apr`) → Holding (`san_varian`)**, ditambah callback status, cancel orchestration, dan fault containment. Viewer interaktif: `/w:/san_sarana_8apr/flowcharts/index.html`.

### 9.2 Flow per Lapisan (L0)

**CRM Layer (`san_ibb_master`):** user ubah Estimate status=`accepted` → `Estimates::_writeOrders()` → persist backup ke `order_bridge_items` → percabangan `order_to_id`:
- (1) subsidiary → `WebhookService::sendOrderSubsidiary()` → `/eusvc/webhook/receive_order`
- (2) direct holding → `WebhookService::sendOrderDirectHolding()`
- Push status timeline (mgk).

**Subsidiary Layer (`san_sarana_8apr`):** `receive_order` → validate payload + transaction begin → customer resolve by `dc_id` / pre-customer fallback → upsert `penjualan_transaksi_data_crm_bridge` → `TransaksiCrm::viewOrderCrm` → `Create::previewCrm` (locker + validation) → percabangan `variant required?`:
- yes → `previewCrmVariantPicker/savePreviewCrmVariant` → kembali ke preview
- no → `FollowUp::doFollowup/save` → PostProcessor `TransaksiDataPenjualanBridging` → tulis `penjualan_transaksi_data_bridge + _master` → CLI `pembelian::autoPurchaseOrder` → publish `api_writeBridge` ke Holding.

**Holding Layer (`san_varian`):** `penjualan/API/ModulConnect::api_writeBridge_get` → insert `reseler_master_bridge` → `CliTransaksi::run_CliPenjualanReselerVersiDedicatedSubsidary` → create SO holding + bridge detail → callback update ke subsidiary `api_update_bridge/masterBridge`.

**Callback/Orchestration:** `BridgeCallbackService::sendOrderStatus` → `penjualan/API/Webhook::orderStatus` (subsidiary & holding).

**Data stores:** D1 CRM DB (`estimates + order_bridge_items`); D2 Subsidiary (`penjualan_transaksi_data_crm_bridge`); D3 Subsidiary (`penjualan_transaksi_data_bridge_master`); D4 Holding (`reseler_master_bridge`).

### 9.3 Critical Watchpoints & Fault Model

**4 Fault Containment:**
- **F1:** `Create::previewCrm` diblokir guard active session saat debug path aktif.
- **F2:** `referensi_pengiriman = 0` → bridge master penjualan tidak terbentuk → antrean CLI auto PO kosong.
- **F3:** scheduler memanggil CLI legacy → hard-stop di `run_CliPenjualanReseler()`.
- **F4:** `referensi_id` sudah ada tetapi item direvisi → revisi payload diabaikan di `receive_order`.

**5 Critical Watchpoints:** (1) `Create::previewCrm` masih punya jalur stop guard active session; (2) bridge master butuh `referensi_pengiriman > 0`; (3) Holding harus jalan dengan CLI dedicated subsidiary (bukan method legacy); (4) `receive_order` perlu kebijakan update bila `referensi_id` sama tapi item direvisi; (5) callback `orderStatus` perlu konsistensi event & side-effect (approved/rejected/cancelled/cancel_check) di kedua sisi.

**Trace token wajib konsisten:** `estimate_id` (CRM), `referensi_id` (bridge CRM & bridge SO/PO), `so_id`/`so_nomer` (sub sales), `po_id`/`po_nomer` (sub auto PO), `cli` status bridge (`0`→`1`), `domain` source/target callback, `variant_id`/`cart_key` (item varian).

### 9.4 Paket Flowchart Detail (4 paket)

- **FC01_CRM_OUTBOUND_TO_SUBSIDIARY** — CRM outbound & route keputusan (A01–A26: accepted di CRM, webhook route, injector/manual payload).
- **FC02_SUBSIDIARY_PREVIEW_FOLLOWUP_VARIAN** — intake, preview CRM, staging varian (B03–B23: validasi customer, pilih SAN/LOCAL + cabang, staging varian legacy, build cart).
- **FC03_BRIDGE_AND_CLI_SUBSIDIARY_TO_HOLDING** — bridge sales→CLI pembelian→holding (C04–C27: auto bridge sales→PO, CLI ke holding, SO & callback).
- **FC04_CALLBACK_AND_CANCEL_ORCHESTRATION** — callback status + cancel/reject lintas sistem (E01–E12).

### 9.5 UAT Multi-Kondisi CRM (2026-04-27)

Dataset dibuat di DB `san_sarana_18feb`, tabel `penjualan_transaksi_data_crm_bridge`. Kunci data: `jenisTr=5822` (sales penjualan), `client_id=2817`, `customer_id=149`, `estimate_id=9301–9304`.

URL UAT (base `https://demo.mayagrahakencana.com/san_sarana_8apr/penjualan/Create/`): list `index/5822?pihakMainExec=local`; preview S1 `previewCrm/5822/9301` (varian lengkap), S2 `/9302` (non-varian normal), S3 `/9303` (legacy varian tanpa `variant_id`), S4 `/9304` (campuran).

**Hasil verifikasi DB:**

| Skenario | estimate_id | item_rows | variant_rows | non_variant_rows | Status |
|---|---|---|---|---|---|
| S1 varian lengkap | 9301 | 3 | 3 | 0 | `VARIANT_OK` |
| S2 non-varian normal | 9302 | 2 | 0 | 2 | `NON_VARIANT_OK` |
| S3 legacy varian tanpa `variant_id` | 9303 | 2 | 0 | 2 | `LEGACY_NEEDS_STAGING` (produk master `has_variants=1`, payload `variant_id` kosong) |
| S4 campuran | 9304 | 2 | 1 | 1 | campuran valid |

**Catatan logik:** jalur `penjualan/_processSelectProduct/selectCrm` **belum memaksa hold/staging** untuk kasus legacy (`has_variants=1` tapi `variant_id` kosong) → S3 kemungkinan masih bisa masuk cart sebagai item non-varian, perlu patch khusus bila rule bisnis mewajibkan staging.

**Query verifikasi cepat:** agregasi `penjualan_transaksi_data_crm_bridge` dengan `SUM(CASE WHEN IFNULL(variant_id,0)>0 ...)` dikelompokkan `estimate_id` (filter `status=1 AND trash=0`). **Cleanup:** `DELETE ... WHERE estimate_id IN (9301,9302,9303,9304)`.

---

## 10. Progres 2 Minggu & Ringkasan Direksi

### 10.1 Kontrol Laporan (Actual Data Snapshot)

| Field | Value |
|---|---|
| Snapshot DB | 2026-04-18 00:09:03 |
| Database | `san_ibb_30mar` |
| Tabel | `rise_estimates`, `rise_estimate_items`, `rise_clients`, `rise_users`, `rise_taxes` |
| Scope utama | 2 minggu terakhir (2026-04-05 s.d. 2026-04-18) |
| Scope baseline | All active estimates (historis aktif) |
| Rumus Accepted Rate | `accepted / (accepted + declined)`, dengan `rejected` dinormalisasi ke `declined` |

### 10.2 Executive Summary 2 Minggu & Baseline All-Time

| KPI | 2 Minggu | Baseline All-Time |
|---|---|---|
| Total Estimate | 2 | 36 |
| Total Value | 161,754,728.00 | 8,048,856,221.96 |
| Accepted | 1 | 13 |
| Declined/Rejected | 0 | 1 |
| Accepted Rate | 100.00% | 92.86% |
| Draft | — | 22 |
| Draft Aging ≥3 hari | 0 | 21 |
| Draft Aging ≥7 hari | 0 | 21 |
| Lead Priority Incomplete | — | 18 |
| Lead Priority Ready SO | — | 1 |

Status distribution (baseline): Draft 22, Accepted 13, Declined 1. Owner aktif utama (2 minggu): **Rahmiati Aspi**. Catatan: aktivitas 2 minggu rendah (2 dokumen), kualitas close bagus (accepted rate 100% pada volume kecil); risiko utama bukan di 2 minggu, tapi backlog draft historis.

### 10.3 Analisa Direksi (EXE)

- Total pipeline value aktif: **8,05 miliar**. Backlog draft dominan: **22/36 (61,1%)**. Draft kritis (≥7 hari): **21 dokumen**. Owner tidak terpetakan (`owner kosong`) memegang **4,71 miliar** pada 6 bulan.
- **Tren bulanan 6 bulan:** 2026-04 = 2 / 161,754,728.00; 2026-03 = 18 / 5,359,180,130.04; 2026-02 = 15 / 2,500,021,363.92; 2026-01 = 1 / 27,900,000.00.
- **Keputusan cepat:** (1) validasi mapping owner pada portofolio 4,71B; (2) lock target penurunan draft ≥7 hari min 30% per 2 minggu; (3) prioritaskan 10 lead teratas aging tertinggi sebagai war room operasi.

### 10.4 Analisa Business Owner / Head of Sales (BO)

Kontribusi 6 bulan per owner: (1) `(owner kosong)` 2 / 4,707,583,495.00; (2) Satria Poncoyudo 8 / 1,880,653,690.00; (3) Janson Simbolon 3 / 519,984,000.00; (4) Oscar Susantio 1 / 445,760,000.00; (5) Rahmiati Aspi 2 / 161,754,728.00.

Prioritas coaching: redistribusi akun draft tua tanpa owner jelas; owner backlog draft tertinggi → SLA follow-up harian; review harian `draft → sent/accepted` untuk backlog umur >30 hari.

### 10.5 Analisa Sales Ops (SO) & Top 10 Antrian Follow-Up

`Lead Priority Incomplete=18`, `Ready SO=1`. Missing field dominan: **NIK dan NPWP**.

| No | Lead | Estimate | Draft Age (hari) | Missing | Owner |
|---|---|---|---|---|---|
| 1 | Bp Munthe | EST#0010 | 87 | NIK, NPWP | Suyanto Tosono |
| 2 | Irsan | EST#0012 | 75 | NIK, NPWP | Satria Poncoyudo |
| 3 | Agus | EST#0013 | 75 | NIK, NPWP, Address | Janson Simbolon |
| 4 | Eko Bagus | EST#0015 | 67 | NIK, NPWP, Address | Iwan Cahyono |
| 5 | DLH MAKASSAR | EST#0019 | 67 | NIK, NPWP, Address | Satria Poncoyudo |
| 6 | Harry Setiadi | EST#0027 | 54 | NIK, NPWP | H Markoni |
| 7 | PT ABC | EST#0031 | 54 | NIK, NPWP, Address | Usman Junaedi |
| 8 | Bp Ardiansyah | EST#0025 | 53 | NIK, NPWP | Herman Suseno |
| 9 | BPBD makassar | EST#0030 | 53 | NIK, NPWP | Satria Poncoyudo |
| 10 | Pak Akbar | EST#0032 | 52 | NIK, NPWP | Satria Poncoyudo |

Checklist SO 2 minggu: (1) lengkapi NIK/NPWP top 10 dalam 3 hari kerja; (2) tutup gap address; (3) verifikasi owner assignment untuk queue kritis.

### 10.6 Ringkasan Direksi 1 Halaman (18 April 2026)

Sumber data `san_ibb_30mar` (tabel `rise_*`); periode utama 5–18 April 2026; pembanding baseline all-time. KPI 2 minggu identik dengan §9.2 kolom 2 minggu. Risiko utama (all-time): total estimate aktif 36; draft 22; draft aging ≥7 hari 21; lead incomplete 18; ready SO 1. Konsentrasi nilai 6 bulan: `(owner kosong)` 4,707,583,495.00; Satria Poncoyudo 1,880,653,690.00; Janson Simbolon 519,984,000.00.

**Keputusan Direksi minggu ini:** (1) owner mapping wajib untuk seluruh portofolio owner kosong (target ≤3 hari kerja); (2) war-room backlog draft ≥7 hari (top 10 lead prioritas) dengan review harian BO+SO; (3) target penurunan draft ≥7 hari min 30% dalam 2 minggu. **KPI monitoring harian Direksi:** `Draft ≥7 hari` (turun konsisten); `Lead incomplete` vs `Ready SO`; `Accepted rate` (jangan turun saat volume naik); `Owner kosong` (menuju nol).

**Catatan validitas data:** laporan murni dari data existing, tanpa fitur baru; angka dapat berbeda UI per-user karena query bersifat global lintas role scope; cocok sebagai baseline enterprise cepat.

### 10.7 Rencana Penyusunan Laporan Pivot Final (timeline konkret)

- **18 April 2026:** freeze scope, freeze KPI dictionary, freeze filter standard.
- **19 April 2026:** tarik data awal + draft narasi per role.
- **20 April 2026:** validasi angka (rekonsiliasi endpoint vs UI).
- **21 April 2026:** review bisnis (Direksi/Sales Manager/Sales Ops).
- **22 April 2026:** finalisasi dokumen + sign-off versi 1.

**Struktur laporan per role:** Direksi (Executive KPI card: total value, accepted rate, draft aging ≥7, ready to convert SO; tren bulanan 3–6 bulan; risk radar; keputusan minggu ini; pivot profile `direksi` + Owner×Week×Status summary). Sales Manager (team performance summary; Owner×Month×Status + accepted rate; backlog aging by owner; lead vs client mix; item load; pivot profile `sales_manager` + Owner×Week×Status full). Sales Ops (queue prioritas follow-up urgent ≥7/≥3; daftar owner perlu tindakan; estimate rework tinggi dari activity; monitoring kualitas data; pivot profile `sales_ops` + priority data summary/listing).

**Endpoint aktif (versi rencana):** `estimates/kpi_core_data`, `estimates/pivot_role_matrix_data`, `estimates/pivot_owner_week_status_data`, `estimates/prioritas_data_summary_data` — semuanya di `app/Controllers/Estimates.php`.

**QC wajib:** total estimate count match KPI vs pivot (±<1%); accepted/declined konsisten; `lead_count + client_count` sejalan `estimate_count` di agregat; item_count/item_qty tidak null di total row; filter owner/month/status konsisten antar endpoint; angka laporan = angka layar pada timestamp sama. **Standar tampilan:** currency konsisten; persen 2 desimal; timezone tunggal Asia/Jakarta; soft-deleted record tidak dihitung. **Out of scope v1:** model scoring ML; materialized summary table baru; integrasi lintas sistem eksternal; detail item per SKU (versi 2).

---

## 11. UAT & Endpoint-Query Mapping

### 11.1 Endpoint Inventory Modul Estimates (di `app/Controllers/Estimates.php`)

| Endpoint | Method |
|---|---|
| `estimates/list_data` | `list_data()` |
| `estimates/kpi_core_data` | `kpi_core_data()` |
| `estimates/pivot_owner_month_status_data` | `pivot_owner_month_status_data()` |
| `estimates/estimate_list_data_of_client/{id}` | `estimate_list_data_of_client()` |
| `estimates/save` | `save()` |
| `estimates/update_estimate_status/{estimate_id}/{status}` | `update_estimate_status()` |
| `estimates/update_activity_status` | `update_activity_status()` |
| `estimates/activity_timeline/{estimate_id}` | `activity_timeline()` |
| `estimates/activity_snapshot/{estimate_id}/{version_no}` | `activity_snapshot()` |
| `estimates/activity_compare/{estimate_id}/{from}/{to}` | `activity_compare()` |
| `estimates/delete` | `delete()` |
| `estimates/prioritas_data_summary_data` | `prioritas_data_summary_data()` |
| `estimates/prioritas_data_list_data` | `prioritas_data_list_data()` |

### 11.2 Matriks UAT Case → Endpoint → Service/Model → SQL

| UAT Case | UI Trigger | Endpoint | Controller Method | Service/Model | SQL / Data Source | Validation Rule |
|---|---|---|---|---|---|---|
| UAT-KPI-01 Estimate Count | Load tabel Estimates | `estimates/list_data` | `list_data()` | `Estimates_model->get_details($options)` | `SELECT ... FROM estimates WHERE estimates.deleted=0` | UI count = DB count by same filter |
| UAT-KPI-02 Estimate Value | Load tabel | `estimates/list_data` | `list_data()` | `Estimates_model->get_details()` | `estimate_value_calculation` join `estimate_items` + tax/discount | UI sum currency = DB sum formula |
| UAT-KPI-03 Accepted Rate | Filter status/dashboard | `estimates/list_data` | `list_data()` | `Estimates_model->get_details()` | `estimates.status` (`accepted`,`declined/rejected`) | Formula denominator fixed |
| UAT-KPI-07 KPI Core API | KPI card backend | `estimates/kpi_core_data` | `kpi_core_data()` | `Estimates_model->get_details()` + `_get_estimate_priority_summary()` | aggregate count/value/status + lead priority SQL | API konsisten dengan list/summary |
| UAT-KPI-04 Draft Aging 3+ | Quick summary card | `estimates/kpi_core_data` | `kpi_core_data()` | `_get_estimate_priority_summary()` via `data.lead_priority` | `SUM(CASE WHEN draft_age_days >=3 THEN 1 END)` | Boundary day-2/day-3 valid |
| UAT-KPI-05 Draft Aging 7+ | Quick summary card | `estimates/kpi_core_data` | `kpi_core_data()` | `_get_estimate_priority_summary()` | `SUM(CASE WHEN draft_age_days >=7 THEN 1 END)` | Boundary day-6/day-7 valid |
| UAT-KPI-06 Ready SO | Quick summary card | `estimates/kpi_core_data` | `kpi_core_data()` | `_get_estimate_priority_summary()` | `NOT(missing_any_sql)` | Ready count sesuai rule missing data |
| UAT-PVT-01 Owner×Month×Status | AppTable + filters | `estimates/list_data` | `list_data()` | `prepare_estimate_filter_options()` + `get_details()` | owner matrix filter + `estimate_date` range | Parent-child total konsisten |
| UAT-PVT-07 Owner×Month×Status API | Pivot backend aggregate | `estimates/pivot_owner_month_status_data` | `pivot_owner_month_status_data()` | `get_details()` + grouped aggregation | grouped by owner/month/status + totals | Sum pivot = total KPI by same filter |
| UAT-PVT-02 Source/Sub-source | Priority table/filter | `estimates/prioritas_data_list_data` | `prioritas_data_list_data()` | `_build_estimate_priority_query_context()` | source/sub-source join di query context | Child subtotal = parent total |
| UAT-PVT-03 Aging Board | Priority tab | `estimates/prioritas_data_list_data` | `prioritas_data_list_data()` | `_build_estimate_priority_query_context()` | draft age bucket + missing fields SQL | Queue sesuai filter owner/domain |
| UAT-PVT-04 Activity Audit | Timeline panel | `estimates/activity_timeline/{id}` | `activity_timeline()` | `EstimateActivityHistoryService->get_timeline()` | `Estimate_activity_history_model->get_timeline_rows()` | Event count = history rows |
| UAT-PVT-05 Snapshot Audit | Snapshot action | `estimates/activity_snapshot/{id}/{v}` | `activity_snapshot()` | `EstimateActivityHistoryService->get_snapshot()` | `estimate_activity_history.snapshot_json` by version | Hash/snapshot konsisten |
| UAT-PVT-06 Compare Versions | Compare action | `estimates/activity_compare/{id}/{from}/{to}` | `activity_compare()` | `EstimateActivityHistoryService->compare_versions()` | compare `snapshot_json` antar versi | Diff paths valid |
| UAT-SEC-01 Staff access matrix | Table/view/detail | `estimates/list_data` dll | `validate_estimate_access()` | `can_access_this_estimate()` + `prepare_estimate_filter_options()` | `Security_Controller` scope matrix | Staff hanya data sesuai scope |
| UAT-SEC-02 Client access | Client portal list | `estimate_list_data_of_client/{id}` | `estimate_list_data_of_client()` | `exclude_draft=true` for client | `status!='draft'` enforced | Client tidak melihat draft |
| UAT-SEC-03 Snapshot permission | Snapshot API call | `estimates/activity_snapshot/...` | `activity_snapshot()` | `_current_user_can_view_estimate_activity_snapshot()` | role key `can_view_estimate_activity_snapshot` | Unauthorized → 403 |
| UAT-NF-01 Export consistency | Excel/Print export | AppTable export layer | View `estimates/index.php` | AppTable `printColumns/xlsColumns` | same source `estimates/list_data` | Export angka = UI |
| UAT-NF-02 Soft delete exclusion | Delete + reload | `estimates/delete` + `list_data` | `delete()` + `list_data()` | `Estimates_model->delete()` + `get_details()` | `WHERE estimates.deleted=0` | Deleted rows excluded |

### 11.3 Access & Scope Traceability

- **Estimate scope by role:** `prepare_estimate_filter_options()` di `Security_Controller` — inject `owner_id`, `owner_id_list`, `permission_estimate`, matrix flags.
- **Matrix enforcement:** opsi `enforce_estimate_access_matrix` membatasi ke creator/lead owner/team manager scope.
- **Client scope:** `estimate_list_data_of_client()` memaksa `exclude_draft` + client contact access check.
- **Snapshot access:** `_current_user_can_view_estimate_activity_snapshot()` — permission gate sebelum snapshot/compare.

### 11.4 Query Rekonsiliasi Referensi

- Baseline count/value: `SELECT COUNT(*) AS total_rows, SUM(estimate_value) AS total_value FROM ( ... mirror logika Estimates_model->get_details() dengan filter sama ... ) t;`
- Status distribution: `SELECT status, COUNT(*) AS total FROM estimates WHERE deleted=0 GROUP BY status;`
- Activity timeline count: `SELECT COUNT(*) AS total_activity FROM estimate_activity_history WHERE estimate_id = :estimate_id;`

### 11.5 UAT KPI/Pivot Technical Checklist (POST-based, generation baru)

**Scope endpoint:** `estimates/kpi_core_data` (POST), `estimates/pivot_owner_month_status_data` (POST), `estimates/prioritas_data_summary_data` (POST, API compatibility), `estimates/prioritas_data_list_data` (POST).

**Payload standar UAT:** `start_date`, `end_date`, `status`, `owner_id`, `month`, `priority_state` (mis. `incomplete`), `priority_owner_id`, `priority_draft_age`, `priority_missing_field`, `priority_province_id`.

**Test case inti:** TC-KPI-01 (`total_count` = `COUNT(*)` scope filter sama); TC-KPI-02 (sum `status_breakdown.count` = `total_count`); TC-KPI-03 (`accepted_rate` = accepted/(accepted+declined)*100); TC-KPI-04 (4 metrik lead priority); TC-PVT-01 (pivot sum = KPI count filter sama); TC-PVT-02 (filter `month=YYYY-MM`); TC-PVT-03 (filter owner); TC-PVT-04 (`server_side=1`, `recordsTotal`/`recordsFiltered` benar, page ≤ limit); TC-PRIO-01 (boundary aging day-2/day-3/day-7); TC-PRIO-02 (filter `priority_missing_field`).

**Evidence minimum:** request/response JSON capture per endpoint; screenshot UI card/pivot; output query DB pembanding; sheet rekonsiliasi `API vs UI vs DB`; defect ticket jika mismatch.

### 11.6 Rekapitulasi Skenario UAT Activity History (Fungsional F-01..F-21 & Non-Fungsional N-01..N-08)

**Fungsional (21 skenario):** F-01 create (Ver1/Rev1/activity=NEW); F-02 edit header (Ver+1/Rev+1); F-03/F-04/F-05 tambah/edit/hapus item; F-06 ubah aktivitas (Rev reset 1); F-07 edit di aktivitas baru (Rev→2); F-08 NO_RESPONSE tanpa note ditolak; F-09 WON saat status draft ditolak; F-10 WON saat accepted berhasil; F-11 RENEWAL sebelum terminal ditolak; F-12 RENEWAL setelah WON (cycle_no+1); F-13 kembali ke aktivitas lama (activity_entry_no naik); F-14 integrity versi (no duplikat `(estimate_id, version_no)`); F-15 lihat timeline; F-16 lihat snapshot; F-17 compare versi (diff highlight); F-18 filter timeline; F-19 no-op save (no version baru); F-20 append-only enforcement (403/405); F-21 hash verify.

**Non-fungsional (8 target):** N-01 load detail 5.000 history first paint <2s (20 data pertama); N-02 load more <1s per 20 data; N-03 commit event 200 item <2s; N-04 concurrency 2 user tanpa corrupt version; N-05 snapshot JSON 100% valid; N-06 monitoring ukuran tabel per bulan; N-07 verifikasi hash periodik 100% sampel valid; N-08 query arsip data >24 bulan ≤3s.

**Checklist UX (6 grup):** keterbacaan timeline; navigasi & aksi (Lihat/Banding benar, filter tidak hilangkan konteks); performa UX (no freeze, load more konsisten, modal cepat); konsistensi data (timeline = DB, Rev/Ver sesuai aturan, snapshot mencakup header+item+total+lampiran+metadata, `tax_rules` sesuai momen transaksi); error handling UX (pesan WON/LOST/NO_RESPONSE actionable, notifikasi jelas, no silent failure); diff & akses (diff highlighter benar, user tanpa izin tidak bisa buka snapshot full).

---

## 12. Temuan Lintas-Dokumen & Kontradiksi

### 12.1 Kontradiksi Activity Code Estimate (paling material)

- `ESTIMATE_ACTIVITY_HISTORY_FINAL_SPEC.md` **§5.1/8.2/8.3** masih mendefinisikan **9 process activity** (`NEW, QUALIFIED, NEGOTIATION, FOLLOWUP_1, FOLLOWUP_2, NO_RESPONSE, WON, LOST, RENEWAL`) beserta transisinya.
- Namun **koreksi 2026-04-16** di dokumen yang sama menegaskan activity code Estimate = status dokumen `DRAFT/SENT/ACCEPTED/DECLINED`; `TASK_CHECKLIST` A1 dan `SQL_MANUAL_EXEC_README` (verifikasi: master punya **4 kode aktif**) mengunci versi ini.
- **Versi mutakhir:** 4 kode `DRAFT/SENT/ACCEPTED/DECLINED`. Section 9-kode bersifat **retained sebagai referensi flow Lead** atau perlu dianotasi stale. Bila data lama `NEW/WON/LOST` sudah terlanjur masuk, wajib jalankan `ALIGN_TO_DOC_STATUS.sql` satu kali.

### 12.2 Kontradiksi Prefix Tabel & Nama Tabel

- Spec & task checklist konsisten pakai prefix **`rise_`** (`rise_estimates`, `rise_users`, `rise_estimate_activity_history`).
- Namun query rekonsiliasi di `ESTIMATES_UAT_CASE_ENDPOINT_QUERY_MAPPING.md` dan `ESTIMATES_ENTERPRISE_KPI_PIVOT_UAT_CHECKLIST.md` memakai nama **tanpa prefix** (`estimates`, `estimate_activity_history`, `clients`).
- **Versi mutakhir:** prefix aplikasi `rise_`; query rekonsiliasi perlu menambahkan prefix agar tidak ambigu (atau dieksekusi pada konteks DB yang menyertakan prefix).

### 12.3 Kontradiksi Retensi: 24 Bulan vs 730 Hari vs Tanpa Purge

- Spec & scale strategy menyebut retensi aktif **24 bulan** dengan pemindahan ke archive.
- `RETENTION_STEP3_README` memakai ambang **> 730 hari** (≈24 bulan) dan secara eksplisit **tidak melakukan purge** karena ada trigger immutability (`no update/delete`) — hanya menyalin ke tabel arsip.
- **Versi mutakhir / resolusi:** 24 bulan ≈ 730 hari konsisten; **tetap tanpa purge** pada step3. Purge hanya via maintenance window + backup + drop trigger sementara + purge batch + re-enable trigger. Archive batch 5.000–20.000 rows, archive table read-only, verifikasi hash sebelum & sesudah.

### 12.4 Kontradiksi Endpoint Pivot: Tiga Generasi Nama

- **Blueprint §6 (P1):** `pivot_summary_data`, `pivot_owner_week_status_data`, `pivot_channel_data`, `pivot_client_data`, `pivot_lead_data`, `pivot_aging_data`.
- **Blueprint Progress 2026-04-19 (P1+P2 selesai):** `pivot_summary_data`, `pivot_owner_performance_data`, `pivot_channel_performance_data`, `pivot_client_data`, `pivot_lead_data`, `pivot_aging_data`, `pivot_exception_data`.
- **Rencana Penyusunan Laporan:** `pivot_role_matrix_data`, `pivot_owner_week_status_data`.
- **UAT Mapping & KPI UAT:** `pivot_owner_month_status_data`.
- **Versi mutakhir:** gunakan set **Progress 2026-04-19** (owner_performance/channel_performance/client/lead/aging/exception + summary) sebagai kanonik P1+P2, dan `pivot_owner_month_status_data` sebagai endpoint pivot terstruktur yang diuji UAT. Nama `pivot_owner_week_status_data`/`pivot_role_matrix_data` disebut sebagai dataset/role-matrix internal. perlu rekonsiliasi penamaan agar tidak ambigu.

### 12.5 Kontradiksi HTTP Method & Kontrak Filter

- **P1 endpoints** didokumentasikan `GET` dengan query params `owner_id`, `role_profile`, `time_frame` (`this_week|this_month|this_quarter|ytd|rolling_30|rolling_90|custom`), `date_from`, `date_to`, `date_basis`, `source_id`, `sub_source_id`, `entity_type`.
- **KPI/Pivot UAT checklist** mendokumentasikan `POST` dengan payload `start_date`, `end_date`, `status`, `owner_id`, `month`, `priority_*`.
- **Versi mutakhir:** ada **dua generasi kontrak** yang hidup berdampingan (page/filter P1 GET vs data-pivot POST). Perlu dinormalkan;Uo T mapping (section 10) memakai nama generik yang konsisten.

### 12.6 Kontradiksi Snapshot JSON vs PII Masking

- `FINAL_SPEC` §6 menampilkan contoh snapshot berisi `client.phone`, `client.address`, `client.name` **mentah**.
- `PII_POLICY` mewajibkan masking deterministik **sebelum** hashing, dan menambah blok `_privacy.*`.
- **Versi mutakhir:** contoh snapshot harus dibaca sebagai bentuk pre-mask; yang tersimpan sudah termask. Memastikan hash tetap konsisten karena masking terjadi sebelum `to_canonical_json()`.

### 12.7 Kontradiksi/Perlu Rekonsiliasi: Approval SO — Dua Inisiatif

- `edit-approve-sales.md` (konsultatif) mengusulkan model: atasan boleh edit kuantitas/varian, harga dikunci, Gudang jadi gatekeeper, audit trail who/what/why wajib; perubahan mayor (harga/diskon) via Reject → edit ulang → approve.
- `rencana_penyelesaian.md` (rencana teknis) mengusulkan status baru **`siap_diorder`**, fungsi privat `_process_order_webhook_sync()`, endpoint baru `authorize_order($estimate_id)`; pemisahan pengajuan (Sales, tombol "Mark as Won" → modal `modal_admdomain_form` target `siap_diorder`, webhook TIDAK dikirim) vs otorisasi (Atasan/Admin, tombol "Otorisasi Order" → status `accepted` → jalankan webhook sync).
- **Catatan:** inisiatif `siap_diorder` **memperluas** enum status dokumen di luar 4 activity code yang dibekukan (`DRAFT/SENT/ACCEPTED/DECLINED`) → perlu update master activity & aturan transisi agar konsisten.

### 12.8 Kontradiksi Nama Fungsi/Method Path Order

- Flowchart teknis menyebut `Estimates::_writeOrders()` (CRM) dan `save_order()`.
- `rencana_penyelesaian` merujuk `save_order()` yang dipecah ke `_process_order_webhook_sync()`; bridge table disebut `rise_order_bridge_items`.
- Flowchart menyebut `order_bridge_items` (tanpa prefix) dan `Estimates::_writeOrders()`.
- **Versi mutakhir:** perlu standardisasi nama method (`_writeOrders` vs `save_order`) dan nama tabel bridge (`order_bridge_items` vs `rise_order_bridge_items`).

### 12.9 Multi-Environment / Path Drift

Beberapa dokumen merujuk basis kode & DB berbeda:
- `san_ibb_master` (CRM prod), `san_sarana_8apr` (Subsidiary), `san_varian` (Holding), `san_ibb_30mar` (snapshot DB laporan), `san_sarana_18feb` (dataset UAT), `san_ibb_2jul` (kode pada rencana/context), `san_28jun` (Data Center API), `san_tsa_17jul` (kode TSA), `new_san_variant` (kode BI pivot), `z:\san_ibb_master\files` (skrip SQL).
- **Catatan:** perbedaan nama environment/path antar dokumen perlu dipetakan sebelum go-live agar tidak salah eksekusi skrip.

### 12.10 Framework Version (CI3 vs CI4)

- Mayoritas dokumen (analisis v14, spec estimate, dsb) merujuk **CodeIgniter 4 / RISE CRM** dengan struktur `app/Controllers/`, `app/Models/`, `app/Views/`.
- `implementation_plan_pivot.md` (personnel activity pivot) memakai **CodeIgniter 3** (`application/controllers/eusvc/LaporanApi.php`, `application/models/Activity_model.php`) pada repo `new_san_variant`.
- **Versi mutakhir:** pivot personnel activity adalah inoteknosial **terpisah** (stack CI3) dari CRM Estimate pivot (stack CI4); tidak boleh disamakan.

### 12.11 Definisi Accepted Rate & Normalisasi Status

- Accepted rate = `accepted / (accepted + declined) * 100`, denominator 0 → `0.00%` (dipakai seragam di blueprint, KPI contract, UAT).
- `Project_laporan_CRM_2minggu` menegaskan normalisasi **`rejected` → `declined`** sebelum dihitung.
- UAT mapping menyebut sumber status `accepted`, `declined/rejected`. → **Aturan normalisasi wajib codified** (treat `rejected` sebagai `declined`) agar angka konsisten antar role & endpoint.

### 12.12 Angka Baseline (Fingerprint) yang Perlu Dikunci

Angka baseline (18 April 2026) yang menjadi acuan rekonsiliasi: total estimate all-time **36**, total value **8,048,856,221.96**, accepted **13**, declined **1**, draft **22**, draft aging ≥3 **21**, ≥7 **21**, lead priority incomplete **18**, ready SO **1**; owner kosong **4,707,583,495.00**. Angka ini harus dikunci sebagai regression baseline agar perubahan kode tidak menggeser angka dashboard.

### 12.13 Deviasi UAT Case ID antara Dua Dokumen

- **Evidence Template** punya UAT-KPI-01..05, **UAT-KPI-07** (=KPI Core API) dan UAT-PVT-01..07 dengan **PVT-07** (=owner month status API); UAT-NF-01 = Performance, UAT-NF-02 = Export.
- **UAT Mapping** punya UAT-KPI-06 = Ready SO (tidak ada di template) dan **UAT-NF-01 = Export consistency, UAT-NF-02 = Soft delete exclusion** (berbeda posisi dari template).
- **Versi mutakhir:** mapping endpoint (UAT Mapping) adalah acakan nomor yang lebih lengkap; nomor NF perlu diselaraskan agar tidak ambigu.

### 12.14 Item Minor: Analisa Sub-Modul Biaya & Putusan Stok (Konteks)

- `analisa-sub-modul.md`: 22 sub-modul (`jenisTr`) biaya terdaftar di `coTransaksiUi.php`; usage teratas 677 (biaya usaha, 7.195), 2677 (otorisasi, 6.952), 1675 (biaya umum pusat, 1.356); 9985 & 119 belum pernah dipakai. Selector fisik: `MdlLockerStockSupplies` & `MdlNotaItem` (tanpa `MdlProduk`). Relevan sebagai referensi pola, bukan bagian dari scope Estimate/Lead.
- `analisa_putusan.md`: selisih FIFO vs UI = **ghost stock** pada `stock_locker_variant` (state `active` tetapi `oleh_id != 0`) untuk Produk 34/Pusus; FIFO total 407 unit valid, tidak ada data loss. Fix: `UPDATE stock_locker_variant SET oleh_id = 0 WHERE state='active' AND oleh_id != 0;` + perbaikan UI `variant_picker.php`; pencegahan lewat `ComLockerStockDualWrite` (Agent Protocol). Relevan sebagai prinsip integritas stok yang interfacing dengan item varian pada integrasi.

---

## 13. Lampiran: Daftar File Sumber (31 file)

| # | Nama File | Ukuran (bytes) | Topik H1 | Peran dalam Sintesis |
|---|---|---|---|---|
| 1 | ESTIMATE_ACTIVITY_HISTORY_FINAL_SPEC.md | 18,087 | Dokumentasi Final Fitur Estimate Activity History (Full Snapshot) | Kanonik spec Activity History: data model, DDL, snapshot JSON, flow, validasi, UAT F/N, DoD, rollout |
| 2 | ESTIMATE_ACTIVITY_HISTORY_ENTERPRISE_HARDENING_CHECKLIST.md | 5,539 | Estimate Activity History - Enterprise Hardening Checklist | Fase 0–6 hardening + daily tracking + bukti eksekusi Fase 1–4 |
| 3 | ESTIMATE_ACTIVITY_HISTORY_TASK_CHECKLIST.md | 6,788 | Checklist Implementasi Estimate Activity History | Checklist task 2 sprint (A–I) fondasi s.d. go-live, DoD, risiko |
| 4 | ESTIMATE_ACTIVITY_HISTORY_PII_POLICY.md | 1,925 | Estimate Activity History - PII Policy (Phase 3) | Kebijakan masking deterministik 28 kunci PII + metadata `_privacy` |
| 5 | ESTIMATE_ACTIVITY_HISTORY_SCALE_STRATEGY_STEP4.md | 2,474 | Estimate Activity History - Scale Strategy (Step 4) | Index strategy, monitoring, growth threshold, archive, partisi |
| 6 | ESTIMATES_PIVOT_ENTERPRISE_BLUEPRINT_FINAL.md | 10,275 | Estimates Pivot Enterprise Blueprint (Final) | Blueprint pivot: tab per role, KPI, endpoint, NFR, governance, progress P1/P2 |
| 7 | ESTIMATES_PIVOT_P1_TECH_IMPLEMENTATION_CHECKLIST.md | 6,057 | Estimates Pivot P1 - Technical Implementation Checklist | Checklist implementasi P1 file-by-file (Estimates.php, Reports.php, view, lang) |
| 8 | ESTIMATES_ENTERPRISE_KPI_PIVOT_UAT_CHECKLIST.md | 3,960 | Estimates Enterprise KPI/Pivot UAT Checklist (Technical) | Endpoint POST, payload, TC-KPI/PVT/PRIO, query rekonsiliasi |
| 9 | ESTIMATES_ENTERPRISE_RACI_MATRIX.md | 3,213 | Estimates Enterprise RACI Matrix (FINAL) | Kanonik RACI 8 peran, matriks governance/build/UAT, eskalasi, approval board |
| 10 | ESTIMATES_ENTERPRISE_RACI_FINAL_PIC.md | 334 | Estimates Enterprise RACI Final PIC | Alias pointer ke dokumen kanonik RACI |
| 11 | ESTIMATES_ENTERPRISE_SPRINT_PLAN.md | 4,770 | Estimates Enterprise Sprint Plan | Sprint 0–4, backlog, risk, capacity, quality gates, hypercare, success metrics |
| 12 | ESTIMATES_ENTERPRISE_UAT_EVIDENCE_TEMPLATE.md | 4,131 | Estimates Enterprise UAT Evidence Template | Scope UAT, case matrix, evidence, reconciliation sheet, entry/exit, sign-off |
| 13 | ESTIMATES_ENTERPRISE_WEEKLY_EXECUTION_CHECKLIST.md | 4,546 | Estimates Weekly Execution Checklist per PIC | Cadence harian, checklist 8 peran, meeting pack, completion criteria |
| 14 | ESTIMATES_UAT_CASE_ENDPOINT_QUERY_MAPPING.md | 8,110 | Estimates UAT Case to Endpoint and Query Mapping | Inventaris endpoint, matriks UAT→controller→service→SQL, access trace |
| 15 | LEADS_PRIORITAS_DATA_SPEC.md | 16,743 | Dokumentasi Fitur Leads - Adopsi Estimate (Final V1) | Aturan shared/permission/audit lead, timeline, P0/P1 breakdown, gap RBAC ISO 27001 |
| 16 | LEAD_TIMELINE_HOLD_TASKLIST.md | 2,057 | Lead Timeline - HOLD Task List | Status HOLD; task wilayah label, auto-show, cache, i18n, UAT e2e |
| 17 | analysis_results_CRM_UPDATE_v14.md | 7,493 | Analisis Feedback Klien (CRM Update v14.pdf) | 8 permintaan klien: item Buat Baru, hapus keterangan, email dinamis, PDF 2 halaman, dll |
| 18 | analisis_nama_konsumen_crm.md | 4,950 | Analisis Teknis: Nama Konsumen Tidak Tampil di Order Baru CRM | Root cause kolom `nama` NULL di `per_customers_register` + multi-field fallback |
| 19 | Project_laporan_CRM_2minggu.md | 4,482 | Project Laporan CRM 2 Minggu (Actual Data Snapshot) | Baseline angka 2 minggu & all-time, analisa per role, top 10 antrian |
| 20 | Project_laporan_CRM_2minggu_RINGKAS_DIREKSI.md | 1,977 | Ringkasan 1 Halaman Direksi - CRM Estimates (2 Minggu) | Ringkasan eksekutif, risiko, konsentrasi nilai, keputusan direksi, KPI harian |
| 21 | FLOWCHART_TEKNIS_CRM_SUBSIDIARY_HOLDING.md | 5,976 | Flowchart Teknis Advanced - Master Map | Master map L0 CRM→Sub→Holding, fault F1–F4, trace token, 4 paket FC |
| 22 | UAT_MULTI_KONDISI_CRM_2026-04-27.md | 2,430 | UAT Multi-Kondisi CRM - 2026-04-27 | Dataset 4 skenario (9301–9304), URL preview, status varian, query & cleanup |
| 23 | edit-approve-sales.md | 2,732 | Analisis Prosedur Approval & Segregation of Duties (SOD) | Dilema executor/approver, delta control, gudang gatekeeper, audit trail |
| 24 | analisa-sub-modul.md | 3,790 | Analisa Sub-Modul Biaya | 22 `jenisTr` biaya + usage, selector `MdlLockerStockSupplies`/`MdlNotaItem` |
| 25 | analisa_putusan.md | 3,767 | (Putusan) Selisih Stok FIFO vs UI Locker | Ghost stock `oleh_id`, fix `UPDATE ... oleh_id=0`, `ComLockerStockDualWrite` |
| 26 | RENCANA_PENYUSUNAN_LAPORAN_PIVOT_FINAL.md | 4,507 | Rencana Penyusunan Laporan Pivot Final (Estimates) | Scope v1 data existing, struktur laporan per role, timeline 18–22 Apr, QC |
| 27 | implementation_plan_pivot.md | 8,039 | Implementation Plan - Personnel Transaction Activity Pivot Report | ETL pivot personnel (CI3): `dim_person`, `trx_activity_raw`, SP, views, `Activity_model` |
| 28 | SQL_ESTIMATE_ACTIVITY_HISTORY_MANUAL_EXEC_README.md | 2,706 | Manual Execute Guide - Estimate Activity History | 8 file SQL, cara eksekusi manual, verifikasi, align doc status, hardening |
| 29 | SQL_ESTIMATE_ACTIVITY_HISTORY_RETENTION_STEP3_README.md | 1,184 | SQL Retention Step 3 - Estimate Activity History | Arsip >730 hari idempoten tanpa purge, output, rekomendasi bulanan |
| 30 | rencana_penyelesaian.md | 3,972 | Rencana Penyelesaian: Alur Otorisasi Estimate Sebelum Order | Status `siap_diorder`, `authorize_order`, `_process_order_webhook_sync`, workflow |
| 31 | session_context_estimate.md | 5,483 | Ringkasan Konteks Pengembangan Fitur Katalog Drawer - Estimates | Katalog drawer, `get_cart_restriction_ajax`, Data Center API, JS anti-race |

---

*Dokumen sintesis ini menghimpun dan mengurutkan seluruh 31 file sumber menjadi satu referensi CRM yang utuh, menandai kontradiksi dan menetapkan versi mutakhir pada setiap topik yang saling bertentangan.*
