KB Coverage & Gaps — build punch-list

KB Coverage & Gaps

Audit of the Arkanza Marketing KB as the Main Hub: what each domain holds, what’s still (to fill), the structural gaps, and where new knowledge belongs. Claude Code builds against this as a punch-list; tick items and update the status column as nodes are filled.

Governance rules still apply: single home per fact (link, don’t restate), App vs KB boundary (live/operational data → Marketing HQ app or a worksheet; understanding → here), every note has an owner + tags + real content or #status/draft.

Status legend: ✅ filled · 🟡 partial/thin · ⬜ placeholder (to fill) · ➕ new (no home today)

---

1. Domain coverage (existing 01–08)

#	Domain	Node	Status	Note
01	Company & Strategy	Brand_Architecture	✅	6 primary + 3 startup brands
01		Positioning_and_Segments	⬜	target customer per brand — also the audience home
01		OKRs	⬜	quarterly objectives
01		Competitive_Landscape	➕	GAP — competitor pricing/positioning/share; propose here
02	Brand Guidelines	per-brand guides (template exists)	⬜	one guide per brand, Bahasa
02		Batik_Motif_and_Story_Library	⬜	motif meanings, heritage, usage rights
03	Products & Catalogue	Batik_Techniques_and_Materials	⬜	tulis/cap/print, fabrics, care
03		SKU_and_Naming_Logic	⬜	code structure, variant rules
03		Pricing_Architecture	🟡	skeleton built (Phase 6); tiers/floors/ceilings pending → Phase 7
03		Unit_Economics	➕	GAP — contribution margin + breakeven ROAS; unblocks ads thresholds/ROAS KPI
04	Channels & Marketplaces	one profile per marketplace (template exists)	⬜	Shopee, TikTok Shop, Tokopedia, Lazada, Zalora, Webstore
11	Partnerships (Affiliate & KOL)	_MOC + Approach + Criteria_Matrix + Roster	➕	GAP — cross-cutting (varies by brand AND channel); own home, see §3
05	Playbooks & SOPs	Product_Launch_Playbook	⬜	cross-role
05		Campaign_Execution_Playbook	⬜	cross-role
05		KOL_Affiliate_Onboarding_Playbook	⬜	cross-role
05		Daily_Marketplace_Ops_SOP	⬜	see SOP-home decision §3
06	Campaigns	Campaign_Calendar	🟡	skeleton built (Phase 6): windows + planning cols; dates to fill
06		brief + post-mortem templates	✅	templates exist
07	Performance & Data	KPI_Definitions	✅	metric dictionary (daily 100% / weekly 50%)
07		Reporting_Templates	🟡	monthly done; weekly to fill
07		Benchmarks	⬜	target ranges per channel; links to Unit_Economics for breakeven ROAS
07		Budget_and_Allocation	🟡	built (Phase 6): allocation model + RACI authority; nominal pending → Phase 7
08	Team & People	Org_Structure_and_RACI	✅	settled
08		RACI_Marketing_Team.xlsx	✅	4 cells pending PIC map
09	Roles & Operations	_Roles_System_Charter	✅	this sub-project
09		DA (Diky) JD + breakdown	✅	revised; rest of roles pending
10	Tools	_Tools_MOC + tool nodes	🟡	seeded Foundation 1A: index + 8 stubs; deepen per-SOP

---

2. Pricing — where each facet belongs (single-source map)

Pricing isn’t missing; it’s multi-facet and each facet has one home:

• Price architecture (tiers, margin floors, discount ceilings) → 03/Pricing_Architecture (the home).
• Unit economics / contribution margin / breakeven ROAS → 03/Unit_Economics, linked from 07/Benchmarks as the ROAS target. This gives the pending breakeven-ROAS blocker a home — resolving it unblocks the ads-pause threshold and the ROAS KPI.
• Promo timing (payday, 9.9, 11.11, Ramadan) → 06/Campaign_Calendar.
• Live price/promo monitoring (Monitoring Harga) → App/worksheet (operational), links to 03 for the discount-ceiling rules — never restates them.

---

3. Structural gaps & proposed homes

Keep the tree shallow — fill within existing domains rather than adding top-level folders.

• Competitive landscape — no home today → 01/Competitive_Landscape.
• Partnerships (Affiliate & KOL) — cross-cutting: criteria & approach vary by both brand and channel (confirmed by Anton), and 05 only has a playbook stub. This is a go-to-market motion across the brand × channel matrix, not a marketplace sub-page. Recommended: dedicated 11_Partnerships/ domain — _MOC, Partnerships_Approach (shared framework), one Affiliate_KOL_Criteria_Matrix note (single home for per-brand/per-channel differences, sliced by #brand/+#channel/ tags — NOT folders, per the KB’s anti-matrix-explosion rule), plus KOL_Roster / Affiliate_Programs (tagged reference lists). Single-source: brand guides (02) link for fit, channel profiles (04) for mechanics, onboarding playbook (05) + MS+KOL role hub (09) for how-to/ownership — none restate the criteria. Tradeoff: adds an 11th domain (past the “8 stable domains” story). Only reason to instead broaden 04 to “Channels & Partnerships” is to preserve that count — but 04 = one profile per marketplace, and affiliate/KOL isn’t a marketplace, so the separate home is cleaner.
• Budget / spend allocation — RACI owns it, spend-pacing SOPs reference it, no home → 07/Budget_and_Allocation (or 03 unit-economics cluster).
• Audience — partially covered by 01/Positioning_and_Segments; deepen there, don’t add a domain.
• Content-production knowledge (Surya’s prompt library, AI content workflow) — lives in the role KB (09/AI_Content_Creator) and links to 02. No separate domain needed.

---

4. Decision to lock in Foundation — SOP home

Two SOP homes now exist (05_Playbooks_SOPs and 09/<role>/SOPs). Single-source rule = one home per SOP. Recommended:

• Role-specific operational SOPs live in 09/<role>/SOPs/ (co-located with the role hub).
• Cross-role playbooks (Product Launch, Campaign Execution, KOL Onboarding) stay in 05.
• Both tagged #type/sop → an “all SOPs” index (MOC/dataview) shows them together. The tag gives the unified view; nothing is duplicated.

Lock this before any SOPs are written, or they’ll need re-homing.

🔒 LOCKED (Foundation 1A, 2026-07-10). SOP home decided as above: role-specific ops SOPs in 09/<role>/SOPs/, cross-role playbooks in 05, unified by #type/sop.

---

4b. Locked decisions (Foundation 1A)

Recorded here as the single audit home; full list + rationale in Plan → Locked decisions.

• 🔒 Position-based, not person-based. Every JD/breakdown/SOP/worksheet/scorecard/hub describes the position. PIC mapping stays operational (App / Laporan_Marketing_Sheet) — the marketplace→person map is never baked into the KB.
• 🔒 SOP home — §4 above.
• 🔒 Partnerships → dedicated 11_Partnerships/, but built during phase 4 (Marketplace & Affiliate + KOL), not now. Until then the 11 row in §1 is a planned home, not a live folder.
• 🔒 Build tracker home — _Roles_MOC (moved out of the charter).
• 🔒 KPI scoring baked in — direct weighting, achievement capped 120%, rating bands; DA v1 weights 35/25/20/20. See KPI_Definitions.
• 🔒 One vault / overlay; knowledge atomic (five buckets = tag/MOC views, not folders).

---

5. Two workstreams, one vault

The Main Hub build now has two interleaved tracks that link into each other:

• A — Domain knowledge fill (01–08): turn the (to fill) placeholders above into real nodes.
• B — Roles & Operations system (09 + 10): per-position JD → breakdown → SOPs → worksheets → templates, wired into the domain knowledge from track A.

Sequencing: fill a domain node just-in-time when a role SOP needs to link to it (e.g. build Unit_Economics when writing the DA spend-pacing SOP), so knowledge and operations grow together rather than as two disconnected passes.