arch-lock

0. 문서 구조 (본 SKILL의 세 층)

1. 도메인 본문 (§1 ~ §N): 이 SKILL의 프로토콜. 잠금 어휘 사용 0건이 verify-policy --check body-neutrality로 자동 검증됩니다.
2. 방법론 본문 — 도메인 중립: Cycle 3에서 <!-- BEGIN: cycle3-body-neutral --> ~ <!-- END: cycle3-body-neutral --> 마커로 감싸진 영역.
3. 도메인 예시 부록 (§A): MCU/MPU/WPF 도메인별 사례. SoT(policies/locked-vocab.json)에서 scripts/gen-locked-vocab.mjs가 자동 생성합니다.

직접 부록을 편집하지 마세요 — node scripts/gen-locked-vocab.mjs로 재생성됩니다.

---

Arch-Lock Skill

Lock architecture decisions from Design documents. Prevents scope creep during Do phase.

Arguments

Argument	Description	Example
(none)	Show arch-lock status	/arch-lock
lock {feature}	Lock architecture from Design doc	/arch-lock lock uart-dma
unlock {id}	Unlock specific decision	/arch-lock unlock AD-001
unlock all	Unlock all decisions	/arch-lock unlock all
status	Show locked decisions	/arch-lock status
diagram {feature}	Generate architecture diagram	/arch-lock diagram uart-dma

How It Works

1. Reads the Design document (docs/02-design/features/{feature}.design.md)
2. Extracts architecture decisions (layers, interfaces, memory, patterns, dependencies)
3. Locks decisions in .rkit/state/arch-lock.json
4. Generates Mermaid diagrams based on domain
5. Pre-write hook checks modifications against locked boundaries

Actions

lock {feature}

1. Read Design document for the feature
2. Auto-detect domain (MCU/MPU/WPF) from project context
3. Extract architecture decisions from Design document sections:
   • Software layer structure
   • Interface definitions
   • Memory/resource allocation
   • Design patterns chosen
   • Dependency directions
4. Present extracted decisions for confirmation via AskUserQuestion
5. Lock decisions in state file
6. Generate domain-specific Mermaid diagram
7. Write lock document to docs/02-design/features/{feature}.arch-lock.md

unlock

• unlock {id}: Remove specific decision by ID (e.g., AD-001)
• unlock all: Remove all locked decisions, disable arch-lock

status

Display all locked decisions with categories and affected paths.

--- Architecture Lock Status ----------------------
Active    : Yes
Feature   : uart-dma
Domain    : mcu
Decisions : 4 locked

| ID     | Category  | Title                      |
|--------|-----------|----------------------------|
| AD-001 | layer     | Software Layer Structure   |
| AD-002 | memory    | Memory Map                 |
| AD-003 | interface | Interrupt Priority Map     |
| AD-004 | interface | Peripheral Allocation      |
---------------------------------------------------

diagram {feature}

Generate domain-specific Mermaid architecture diagram.

MCU Diagrams:

• Memory Map (Flash/RAM sections)
• Peripheral allocation table
• Interrupt priority map
• Software layer diagram (Application → Driver → HAL)

MPU Diagrams:

• Software stack (Kernel → Driver → Library → App)
• DT node tree structure
• IPC/interface structure (ioctl/sysfs/socket)

WPF Diagrams:

• MVVM structure (View ↔ ViewModel ↔ Model)
• DI container graph
• Navigation map

Domain Templates

MCU

Decision	Description
Software Layer Structure	Application → Driver → HAL. No direct register access from app.
Memory Map	Flash/RAM allocation per linker script
Interrupt Priority Map	ISR priorities locked
Peripheral Allocation	Peripheral-to-function mapping

MPU (Kernel/Driver/App)

Decision	Description
Software Stack	Kernel → Driver → Library → App. Clear user/kernel boundary.
Driver Interface	ioctl/sysfs/netlink per driver
DT Node Structure	Device Tree hierarchy and bindings
IPC Architecture	Inter-process communication method

WPF

Decision	Description
MVVM Structure	View → ViewModel → Model. ViewModel must not reference View.
DI Container	Service registration and lifetimes
Navigation Pattern	Page/Window navigation strategy
Communication Architecture	Serial/network layer isolation

Integration

pre-write.js Hook

When arch-lock is active, Write/Edit operations to affected paths show a warning:

Architecture decision AD-001 (Software Layer Structure) applies to this file.
Ensure changes comply with locked architecture. Use /arch-lock unlock AD-001 to modify.

/guard mode

Guard mode activates arch-lock boundary enforcement alongside freeze and L2 cap.

PDCA Design Phase

Auto-suggested after Design document creation: "Consider locking architecture decisions with /arch-lock lock {feature}."

State

File	Purpose
.rkit/state/arch-lock.json	Locked decisions state
docs/02-design/features/{feature}.arch-lock.md	Lock document with diagrams

Usage Examples

# Lock architecture after design
/arch-lock lock uart-dma

# Check what's locked
/arch-lock status

# Generate diagram
/arch-lock diagram uart-dma

# Unlock specific decision
/arch-lock unlock AD-002

# Unlock everything
/arch-lock unlock all