> **기록 · 설계서** 본문은 쓴 때의 원문이다. 지금 동작은 「현재 정본」을 읽는다. - 상태: 확인 안 함 - 작성일: 2026-09-19 - 요약: 운영 코드가 Spring active profile을 직접 읽지 않게 하는 경계 설계다. - 현재 정본: `src/bootstrap/app/README.md` # Runtime Profile Access Boundary ## Goal Finish the remaining BOOT-002 requirement: production bootstrap code must not read Spring active profiles ad hoc after the runtime vocabulary has already been centralized in shared-contract RuntimeEnvironment. ## Boundary shared-contract RuntimeEnvironment remains framework-free and owns only vocabulary/semantics: - local - dev - prod - profile -> RuntimeEnvironment resolution - production/test interpretation app-bootstrap owns one Spring-aware bridge: - RuntimeProfileSnapshot.from(Environment) - immutable copy of active profile names - delegation to RuntimeEnvironment for environment resolution and production/test interpretation No other app-bootstrap production class calls Environment#getActiveProfiles directly. ## Why a bootstrap bridge instead of changing RuntimeEnvironment shared-contract is deliberately Java-stdlib-only and is also consumed by non-Spring adapter leaves. Making RuntimeEnvironment accept Spring Environment would reverse that boundary. The bridge keeps Spring extraction in the composition root while preserving one vocabulary/decision implementation. ## Compatibility - active profile order is preserved; - supplementary profiles remain visible; - profileless contexts remain empty; - production still means exactly the RuntimeEnvironment.PROD vocabulary; - test remains a test-only profile, not a deployable RuntimeEnvironment; - logging and management surfaces that expose active profiles retain their current string behavior. ## Enforcement Add an ArchUnit rule over app-bootstrap production classes: - RuntimeProfileSnapshot is the only class allowed to call Environment#getActiveProfiles; - new direct callers fail architectureTest. ## Verified result - app-bootstrap production calls Environment#getActiveProfiles exactly once, inside RuntimeProfileSnapshot; - RuntimeProfileSnapshot focused unit tests: PASS; - RuntimeProfileAccessArchitectureTest: PASS; - ArchRuleDiscoveryContractTest includes and discovers the new rule: PASS; - shared-contract check, including RuntimeEnvironment tests: PASS; - app-bootstrap Spotless, full test and full architectureTest: PASS; - git diff --check: PASS.