IA Governance · Planning

Hard Rules กฎแข็ง · ห้ามฝ่าฝืน

Main console เป็น A-owned · top-level ต้องน้อย · ห้ามกระจายด้วย sub-domain entries
/kb/* เป็น B-owned · A link เท่านั้น · ไม่แก้ content หรือ structure
/planning/* และ /runtime/* เป็น A-owned · B reference ได้เท่านั้น
ทุก surface ต้องประกาศ Live / Shell / Soon อย่างซื่อตรง · ห้าม claim production ถ้ายังไม่มี runtime + data + approval
คำว่า Dashboard สงวนไว้สำหรับ real dashboard experience (charts · drilldown · interactive) · ไม่ใช่คำใช้เรียกกลุ่ม
กลุ่ม umbrella ใช้ชื่อ Portal · ไม่ใช่ Dashboard
เมื่อ B rename /kb/* route · A update link only · ห้าม reinterpret B logic

Naming Rules คำสงวน · ใช้กับอะไร · ห้ามใช้กับอะไร

Term	Reserved For	Do NOT Use For	Valid Example	Invalid Example
Dashboard	Real dashboard experience with charts, filters, drilldown, interactive analytics	Container/umbrella groups · folder labels · abstract landing pages	`/kb/dashboard.html` (17 real dashboards spec)	Calling the Operations Portal a Dashboard
Operations	Umbrella name for the operational/runtime-adjacent group on main console	Individual dashboards · single tools · single contracts	Main button `Operations` → `/operations-portal.html`	`/kb/operations.html` (B does not own this naming)
Portal	Group landing pages that fan out to multiple related sub-entries	A single page of content · a single contract viewer	Operations Portal · Feature Portal · Stakeholder Portal	Calling a single contract page a 'Portal'
Planning	RFC / design / field mapping / implementation scope (A-owned)	Live runtime · production data · admin plane	`/planning/feature-flags.html`	`/planning/live-dashboard.html` (no live data)
Runtime	Preview · debug · scaffolding · implementation-facing (A-owned, not prod)	B-owned spec viewers · canonical contracts · marketing pages	`/runtime/feature-flags/` (registry + simulator)	Claiming `/runtime/*` is production
KB	B-owned knowledge · contract · shell · spec viewer	A runtime · A admin plane · A planning RFC	`/kb/dashboard.html` · `/kb/cases.html` · `/kb/lexicon.html`	`/kb/admin-control-plane.html`
App	Future user-facing A-owned application runtime (production)	Planning docs · spec viewers	Future: `/app/wizard/`	`/app/` for planning RFCs
Admin	Future admin plane A-owned runtime (approvals · audit · sign-off)	Public-facing content	Future: `/admin/approvals/`	`/admin/` used for demos
Ops	Future operational tooling (flag flips · deploys · incident)	B-owned KB · planning docs	Future: `/ops/flags/`	`/ops/` for marketing

Path Rules path ไหนใช้กับอะไร · owner คือใคร

Path	Owner	Purpose	May Contain	Must NOT Contain	Current State
/	A	Main console (executive entry)	6 top-level buttons (soft cap 8)	Per-module crowding · runtime admin UI	Live · 6 btns
/operations-portal.html	A	Sub-portal · dashboards/cases/generate/tenant/planning	5 sub-entries · Live/Shell labels	Live runtime · write operations	Shell · 5 Shell
/links · /hub · /portal · /ai-content-dashboard	A	Legacy A-owned surfaces	Live content or legacy demos	New content unless reviewed	Live
/kb/*	B	Knowledge · contracts · spec viewers · shells	KB HTML · data JSON · kb.js / kb.css	A runtime · A admin · A-defined flags	Phase 12 closed · 87 docs
/planning/*	A	RFC · design · field mapping	Design HTML · ER · API sketch · sequence flows	Live data · production runtime · admin ops	v0.2 · 10 pages
/runtime/*	A	Runtime preview · debug · scaffolding	Registry JSON · schemas · simulator HTML	Production traffic · admin flip UI	Phase 1 · feature-flags
/app/* (future)	A	User-facing production runtime	Real product · real data · real auth	Planning docs · spec viewers	Not yet
/admin/* (future)	A	Admin plane runtime	Approval queue · sign-off · audit viewer · tenant mgmt	Public-facing content	Not yet · planned
/ops/* (future)	A	Operational tooling · flag flips · incidents	Flag admin UI · deploy kanban · rollback	Planning docs · spec viewers	Not yet

Owner Matrix surface · owner · purpose · can link to · must not contain

Surface	Owner	Purpose	Can Link To	Must NOT Contain	Note
Main Console (`docs/index.html`)	A	Executive entry · 6 top-level gateways	/kb/* · /planning/* · /runtime/* · /operations-portal.html · legacy A pages	Per-runtime sub-buttons · live admin controls · B-owned structure	Keep small · collapse into Portal
Operations Portal	A	Sub-portal landing · 5 sub-entries	/kb/dashboard · /kb/cases · /kb/generated · /kb/enterprise-upload · /planning/	Write ops · live admin flip	Link-only layer
KB (`/kb/*`)	B	Canonical knowledge · contracts	other /kb/*	A runtime · A admin · A naming reused as labels	A links only
Planning (`/planning/*`)	A	RFC · design · mapping · scope	/kb/* (ref) · /runtime/* (impl pointer) · /operations-portal.html	Live data fetch · production runtime · write ops	B refs via anchor only
Runtime (`/runtime/*`)	A	Debug · scaffolding · registry · simulator	/planning/* (spec) · /kb/* (contract ref)	Production traffic · admin flip UI	5-status binding vocab
Future /app/*	A	User-facing production runtime	/api/*	Planning docs · spec viewers	FF gate + Admin CP req
Future /admin/*	A	Admin plane · approvals · audit · tenant mgmt	/ops/* · /api/admin/*	Public content · /kb/* editing UI	All writes gated
Future /ops/*	A	Operational tooling · flag flips · deploys	/admin/* · /api/admin/* · /runtime/* (read-only)	B-owned content · public marketing	Admin-tier · audit-logged

Portal Hierarchy ตัวอย่างโครงสร้างปัจจุบัน

/ (Main Console · A-owned) ├── Links → /links.html [Live] A ├── Hub → /hub.html [Live] A ├── Portal → /portal.html [Live] A ├── Merchant → /ai-content-dashboard [Live] A ├── Knowledge → /kb/ [Live] B └── Operations → /operations-portal.html [Shell] A │ ├── Dashboard → /kb/dashboard.html [Shell] B ├── Cases → /kb/cases.html [Shell] B ├── Generate → /kb/generated.html [Shell] B ├── Tenant → /kb/enterprise-upload.html [Shell] B └── Planning → /planning/ [Shell] A │ ├── 5 runtime planning pages (dashboard · cases · generate · tenant · wizard) ├── 4 cross-cutting pages (admin · flags · hints · signal) └── IA governance (this page) /runtime/ (A-owned implementation preview) └── feature-flags/ ← Phase 1 · registry live · evaluator not bound

Live vs Shell vs Soon Policy เมื่อไรใช้ป้ายไหน

Live · criteria

Backed by real runtime + real data
Tested in staging at minimum
Feature flag exists and is ≥internal for the linked surface
No production claim beyond actual rollout stage

Current examples: Links · Hub · Portal · Merchant · Knowledge

Shell · criteria

Contract viewer · RFC · planning · spec page
No runtime bound OR flag still draft/internal
No production traffic uses it
Honest note on page

Current examples: Operations (main) · Dashboard · Cases · Generate · Tenant · Planning

Soon · criteria

Route placeholder · target page does not exist yet
Clear ETA or blocked-by citation
Do not link if target 404s · keep as disabled card

Current examples: (none)

Rules

Every button on main console OR sub-portal MUST carry exactly one of: Live / Shell / Soon
Never promote Shell → Live without feature-flag evidence + approval ref
If Shell has partial runtime (e.g. registry live · evaluator not bound) · stay Shell at button · honest note inside explains detail
Page-internal binding uses 5-status vocab: live / mock / mapped-not-bound / placeholder / derived (see /planning/ binding legend)

Change Control เมื่อมีการเปลี่ยนแปลง

Scenario 1 · B renames a /kb/* route

Example: B renames /kb/cases.html → /kb/case-board.html

✅ Update the href in operations-portal.html + any planning/runtime anchor
✅ Do NOT rename A-owned labels to match (A label naming is A-governed)
✅ Add SYNC.md entry noting the sync
❌ Never edit the B page itself
❌ Never duplicate B content into A
❌ Never reinterpret what the renamed page does

Scenario 2 · New business need wants a new top-level button

✅ FIRST · check if fits an existing Portal (collapse inside sub-portal)
✅ If genuinely new umbrella · propose Portal name per naming_rules
✅ Add governance entry here · update owner_matrix · path_rules · hierarchy examples
✅ Only then edit docs/index.html
❌ Never add top-level without governance review
❌ Never use reserved terms (Dashboard · KB · Admin · Ops) as a label for unrelated content

Scenario 3 · Deprecation

Mark with Soon badge + deprecation notice for 1 release cycle
Remove only after stakeholder review
Keep redirect or 410 Gone
Append SYNC entry

Soft Caps ขอบเขตจำนวน · เกินต้องทบทวน

8

Main console top-level

6

Sub-portal entries

10

Planning pages per pack

3

Runtime phase deliverables per batch

Soft · exceed with justification + governance review · not a hard block

JSON Source machine-readable version

Full structured source at ia-governance.json · use this for CI linting or automation that needs to check IA rules.

IA Governance กฎมาตรฐาน naming · path · owner · portal hierarchy · live vs shell policy · change control