# KBX v30 Standard Traceability

| v30 구현 | KBX 표준 근거 |
|---|---|
| T01~T09 `coreComponents` / `completionChecks` | Business UX/AX §7, §45~§50, §61~§73; Implementation Contract §7~§9, §94~§118 |
| 9개 Screen Type canonical Scaffolder | Business UX/AX §65~§66; Design System §94~§100, §120~§123 |
| `KbxFormGrid` 기본 2-column / `KbxFormSpan` | Business UX/AX §8; Design System §55~§57 |
| Field label canonical width 유지 | Business UX/AX §4, §8; Design System §57 |
| Home `바로 시작` Workbench | Business UX/AX §58~§60; Reference Screens §3~§7 |
| Global Header Module Selector | Reference Screens §4 Global Header `[OMS ▼]` |
| Header/SideNav module context 동기화 | Predictable Layout, Global Application Shell / Side Navigation |
| Route capability 재검증 | Implementation Contract §6 ScreenId, §85~§86 Permission, §113~§114 Preference |
| Unknown route 표준 Recovery | Design System §101~§104 Error Recovery / Permission UX |
| AccessDenied 기본 Screen metadata 비노출 | Permission UX / 민감정보 최소 노출 / Backend 최종 Enforcement 원칙 |
| Home·메뉴검색 Recovery | Reference Side Navigation/Menu Search, Business UX Mouse/Keyboard complete |
| 사용자 Header action propagation | Hidden/dead action 금지, Global Header 계약 |
| Design debt 286 ratchet | Design Token 계층, 공통 Component 우선, 기술부채 관리 |

v30은 첨부 KBX 표준에 없는 새로운 업무 문법을 발명하지 않는다. 기존 Form, Screen Template, Global Shell, Workspace, Permission, Error Recovery 원칙을 **생성기·공통 Component·Navigation Policy·자동 Gate**로 강제하는 작업이다.
